Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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:

    • Create a tasks board on Trello for the group - the current points will move there (Stefania/Abstract Technology, Gabriel/OpenCraft)

    • 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)

    • Ideas Factsheet to organize the next step

  • Organize the contributors meetup (Xavier)

Development & architecture

  • Help guide initiatives advancing the points listed in Needed Architecture Investments (Nimisha/edX)

    • Tests: Answer the poll about recap of pain points with tests (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)

    • Sysadmin dashboard: Follow-up with Peter Pinch (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

  • No labels