Discovery: Where should extensions & repos live?

[sarina]

We need to develop a standpoint on whether extensions/community-developed repos need to be in the openedx GitHub org or can be in the providers' orgs. What does it mean for an extension to be hosted in the Github org?

Some thoughts/color to this issue:

• The TOC is likely going to be the one to ultimately answer this question; this discovery task is simply to discuss the possibilities and their pros/cons. tCRIL may put forth an opinion to the TOC, but again, they will likely have the final call.
• One question to consider: Should django hooks & signals be in the openedx org?

@ormsbee has written some thoughts on this issue previously:

My starting position is that something most go into the openedx org if its sudden removal would essentially break the system as a whole. Case in point, the events/filters work should be in the Open edX org, because edx-platform already references those things directly and emit them in a bunch of places. New XBlocks are things that can be put in providers' orgs (as they already are).

Providers can and should keep commit+merge rights to those projects, but Open edX / TCRIL should have the keys to the infrastructure/PyPI/doc site generation, so that if and when a given provider needs to suddenly step back from that work, we're not left scrambling.

I'm also thinking that we should set up a tiered system of repo support status, and be really up front about what's under active development vs. what's parked in maintenance-only mode vs. what's actively looking for maintainers.

[jmakowski1123]

H2 - revisit after ownership and clean-up tasks complete

[sarina]

@jmakowski1123 I think this falls out of Core Product Offering - at least, it should be considered as part of that work.

fwiw we did pull in hooks & signals into the org. But we're not pulling in, say, Tutor.