Actually, from working on the list I have a new proposal:
- Components that need a maintainer and are directly important for: any our clients, our hosting/infra, or our development process.
- e.g. Aspects (important for our clients, important for the community)
- e.g. Harmony (important for our infra / our hosting, important for the community)
- e.g. extendable interfaces like XBlock API, REST APIs, or theming
- Components that we developed or majorly contributed to, but aren’t necessarily currently used by our clients. Also, dependencies of anything in Priority 1 (i.e. things we don’t really care about directly but they’re currently required for something we do need) (e.g. we don’t use proctoring but we consider
edx-proctoringa priority 2 because it’s required for the “timed exams” feature, which we do need.)- Specifically: blockstore, openedx-tagging, content libraries, Drag & Drop XBlock, Pluggable Discussions API , XBlock runtime [BD-13]
- Anything that we think our clients might use, or that is currently used but we don’t really want to support in the future would be the third priority for us. We could still offer to maintain it if a maintainer is needed and we have capacity, but it’s low priority.
Here is a draft list. @Agrendalath , @farhaan , @kshitij and anyone else - could you please help me my filling out column H about which clients use things, add notes in Column G, and add any comments you have in general?
Note that Column D is the Axim priority from @feanil and Column E is the proposed OpenCraft priority.