Create a wiki page underneath Active Working Groups. Include your name, purpose, chairperson & any other named roles, communication methods, meeting times, and any other info that would help new collaborators jump in and get involved with your working group. Consider adding a sub-page to hold agendas, notes, and recording links for your meetings.

Example: Data Working Group .

Add a listing to the table on Active Working Groups , following the pattern set by the other working groups.

If your working group will have regular meetings, add them to https://calendar.google.com/calendar/embed?src=c_v86shrnegshsqgp4fj2k94u7bc%40group.calendar.google.com&ctz=America%2FNew_York . In the event’s description, include links to wherever you will hold your meeting agendas/notes.

Create a new public channel in the Open edX Slack workspace, prefixed with #wg-.

Example: #wg

-build-test-release

Add yourself (the WG chair) to the @wg-chairs user group Slack.

Create a subcategory on discuss.openedx.org underneath Working Groups.

Example: https://discuss.openedx.org/c/working-groups/build-test-release

Create a new public GitHub repository in the openedx organiztion to hold issues for your working group. Grant access to the repository:

• core-contributor-program-

• committers should have write access

• .

• community-pr-triage-managers should have triage access.

Example repository: https://github.com/

openedx/wg-developer-experience

Also create a new publicly-readable GitHub project in the openedx organization. This will let you organize your issues into boards. You, as the WG chair, should be granted admin access to the project.

Example project: https://github.com/orgs/openedx/projects/37

Ask the Marketing WG in #wg-marketing to add your new working group to https://openedx.

org/open-edx-community-working-groups/.