Community organization
In order to measure how we are doing in helping each other in the community, provide what statistics exists of usage from discourse, and description of how we could use badges (Ned)
Community support - Helping with answering & moderating tools like the forum (OpenCraft has weekly rotations, Felipe/Edunext to increase time commitment)
Organize the community hangout (Ned/edX)
Workgroups
Marketing:
Scheduling of first meeting for the workgroup (Stefania/Abstract-Technology)
Comparison of Open edX and Canvas (Peter/RaccoonGang)
Feature matrix that could get cleaned up and contributed as marketing collateral for the Open edX website (Nate/Appsembler)
Organize the contributors meetup (Xavier)
Development & architecture
Help guide initiatives advancing the points listed in Needed Architecture Investments (Nimisha/edX)
Tests: Recap of pain points with tests, posted in a thread on the forum (Nimisha: start thread, comment: Xavier/OpenCraft, Nate/Appsembler, Raccoon Gang, Felipe/EduNext)
Documentation - see the item in “Releases”, below
Plugins/API work:
Frontend plugin framework specifications review (to be posted by edX/Nimisha, and then reviewed by OpenCraft)
Post recap of discussion to MIT in the thread, ask if MIT could work on this now (Xavier/OpenCraft)
Automated notifications of publishes of ADRs. (OpenCraft + edX)
Releases
Organize the releases working group (Regis)
Produce the named releases (Ned/edX)
Reviewing & solving some of the issues reports from the Juniper tag on the discussion forum (OpenCraft/Geoffrey)
Documentation effort:
Toggle/Settings Documentation/Tooling (Regis, Nimisha+Arch Squad/edX)
Build a reference manual for edx-platform: PR (Regis)
Help to document features - not necessarily operation settings (Felipe)
Tasks done
Marketing - Creating a discourse thread and starting to schedule a meeting for the workgroup (Stefania/Abstract-Technology)
Creating a discourse thread for the contributors meetup (Xavier)