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 14 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

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

    • Authorization - Course/Catalog Access/Visibility Groups (Nate/Appsembler)

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

    • Hold a meeting on March 18th to guide the toggles documentation effort (organized by Nimisha, attended by Regis, Felipe/eduNext, Appsembler)

    • Toggle/Settings Documentation/Tooling (Regis, Arch-BOM/edX, Nate/Appsembler)

    • Build a reference manual for edx-platform: PR (Regis creates the PR, Felipe documents some of the settings in Regis' PR)

    • Help to document features - not necessarily operation settings (Felipe)

Tasks done

  • No labels