OEP-55 - Phase 1: Pilots

[hurtstotouchfire]

We'd like to do some gap analysis in preparation for OEP-55 and ideally pilot the new maintainer structure with a few repos.

Use cases

All of these cases assume that we're currently maintaining the repo. Are there any that we don't maintain but might have to take on?

1. Repos we currently maintain & will keep
   a. Maintenance is already close to goal
   b. Close large maintenance gap
2. Transition to new maintainer
   a. Still in use by 2U / edx.org
   b. Formerly used by 2U / edx.org, now deprecated or unused
   c. Not used or used historically by functions now moved to tCRIL (e.g. CC program, Open edX conference, etc)
3. Only used by us / not part of Open edX
   a. keep public on 2U-owned org
   b. transition to private

Possible pilot repos

1. Keep & maintain

These would be the primary cases where we need to sort out what OEP-55 compliance looks like for us.

• TNL: edx/frontend-lib-content-components - This might be a good straightforward case.
• Paragon (see Issue 30) - This is a more complex case

2. Transition to new maintainer

• openedx/xblock-drag-and-drop-v2
• openedx/xblock-adventure
• openedx/xblock-image-explorer
• openedx/xblock-google-drive
• openedx/blockstore - developed by OpenCraft with Dave Ormsbee (now at tCRIL). Not used by 2U / edx.org?

3. Only used by us

As far as we know, anything that needs to be private for business reasons is already private, so what might we want to make private for other reasons? Is there a model for 2U-owned open source that (in theory) does not need to comply with OEP-55?

[davidjoy]

One option - frontend repositories formerly owned by community-engineering which now more naturally fit with the frontend working group or tCRIL.

Such as:

• frontend-app-profile (fwg)
• frontend-build (fwg)
• frontend-platform (fwg)
• frontend-component-header (fwg)
• frontend-component-footer (fwg)
• eslint-config (fwg)
• frontend-template-application (fwg)
• edx-bootstrap (fwg, unsupported)
• edx-ui-toolkit (fwg, unsupported)
• stylelint-config-edx (fwg, unsupported)
• frontend-wg (tCRIL)
• openedx-tech-radar (tCRIL)

All of these fall into the bucket of "things which are already de facto owned by FWG or tCRIL".

Note, I don't include frontend-app-account in this list because I think it may have a better home with a team at 2U - we continue to invest in it.

[ashultz0]

https://github.com/openedx/edx-analytics-pipeline is a weird case but might be interesting.

2U will stop running any of this code this month. We know some partners (opencraft certainly, maybe others) still use it. The sad wrinkle is no one actually loves it or probably even likes it.

[hurtstotouchfire]

I'm closing this ticket to preserve the historical context but current work on OEP-55 pilots will be tracked on #31