🏗️ This page is under construction. Feel free to help build it!
RelatedThere also an effort to create an OEP to formalize the working group system: https://github.com/openedx/open-edx-proposals/pull/424. It’s currently on the back burner, but you can take a look and leave feedback if you’d like.
Table of Contents
| Table of Contents |
|---|
Prerequisites
(These were carried in from Working Group Guidelines and Definition)
The topic must be related the Open edX platform, its community, or one of its use cases.
There must be adequate control and feedback into the Open edX community. A working group functions with bidirectional communication with the larger community
Generally all communication as to the work of the working group should be public, understanding that sometimes a matter may need to be private. In such cases, please consult with Open edX leadership.
All code produced within the working group must be compatible with a license presently used by Open edX platform.
All documentation produced within the working group must be licensed under a Creative Commons share alike license (CC-BY-SA).
Any code generated by the working must be published in a repository in the openedx GitHub organization.
All code contributors must either sign an individual Open edX CLA be specifically included under their organization's Open edX CLA.
...
As the chairperson, set up each of the following. For anything you lack access to do, you can open up an Axim Request (feel free to batch a bunch of them together into one request).
Wiki | 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. |
|---|
Calendar
Meetings | You don’t have to have meetings, but if you do, make sure everyone can benefit from them!
|
|---|---|
Slack | Create a new public channel in the Open edX Slack workspace, prefixed with Add yourself (the WG chair) to the |
Forums | Create a subcategory on discuss.openedx.org underneath Example: https://discuss.openedx.org/c/working-groups/build-test-release |
GitHub | Create a new public GitHub repository in the openedx organiztion to hold issues for your working group. Grant access to the repository:
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 |
Anything else?
These are new instructions. If anything seems missing, add it here!
...