DEPR request for enterprise backend repo's

[sc-sonata-svg]

Firm Name

2U

Urgency

Medium (< 2 weeks)

Problem/Request

Hi Team,

We have to depricating the below enterprise backend repo's . Could you please help me out on this. Additionally must disable the Actions in the old repo's (Open edx repo's).

https://github.com/openedx/license-manager ---- old one to deprecate
https://github.com/edx/license-manager ----- new one

https://github.com/openedx/enterprise-access ---- old one to deprecate
https://github.com/edx/enterprise-access --- new one

https://github.com/openedx/enterprise-subsidy --- old one to deprecate
https://github.com/edx/enterprise-subsidy --- new one

https://github.com/openedx/enterprise-catalog ----- old one to deprecate
https://github.com/edx/enterprise-catalog --- new one

Note:Do not disable the actions untill we give confirmation to proceed, and also license-manager now avalaible to do that.

Reasoning

we are onboarfing the many new contrator engineers who cannot sign the contributor agrement. So we must fork many enterprise-only code repo's.

These enterpise repo's are not widely used outside 2U (except may be opencraft who might respond to call for maintainer).

[github-actions]

Thank you for your report! @openedx/axim-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer.

[bmtcril]

Hello, there are a few things we need to understand better before we can work on this ticket.

1. We'll need someone who we know from 2U to approve this request (@jristau1984 perhaps?)
2. The deprecation process is outlined here: https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0021-proc-deprecation.html and that is the process you'll need to follow in order to deprecate the repositories
3. Since 2U took on the responsibility of maintaining those repositories, someone from there should be the "coordinator" for the deprecation and handle the steps outlined above, but I'm happy to help if there are questions
4. This is usually a 6+ month process to give people who are relying on the code time to either take over maintenance or find an alternative, but it will depend somewhat on the responses to the forum posting to see which, if any, of these repositories are in wider use
5. As long as the deprecation process is in progress this is considered live code so we cannot disable many of the actions (ex: the CLA check is legally required, tests are required, etc). If someone else takes over maintaining those repositories the actions will need to remain in place. Are there specific actions that are causing you problems?

[jristau1984]

The approval for this will need to come from Brian Beggs.

[bmtcril]

@pwnage101 can you roll back the deprecation messages on those repositories? They have to go through the process outlined above before they can be deprecated. If the intention is to immediately step away from maintaining them that would be good to know as well, and something to put into the deprecation forum post so that people who may be using them can have a chance to step in.

[pwnage101]

1. We have sent this ticket for approval from Brian Beggs. This approval should come quickly.
2. Thanks for the process link, we will review today.
3. @sc-sonata-svg , Vijay, and myself will be the DEPR coordinators.
4. We understand now that this is normally a much longer process. (Still, I think the intention was to expedite it during our 2-week stay in India).
5. We are happy to keep the Actions running in openedx/* repos. The motivation was based on deprecation purposes and completeness, not any critical need.

can you roll back the deprecation messages

Yes, we can roll them back, we'll make an effort today. Just to clarify, the new edx forks are already deployed on 2U infrastructure and used to build images used by edx/devstack.

[macdiesel]

Approved.

[bmtcril]

@pwnage101 Can you please remove the links to the edx forks and roll back the changes to the PR templates as well? These repos aren't deprecated yet. Adding the forks into the README confuses the issue and there are some potential legal/licensing issues that we should make sure are understood on both sides before we have any links pointing to code outside the org.

[pwnage101]

Apologies, I was on a weeks long vacation followed by a fever but now I'm back. Having just merged removal of deprecation notices on a couple of the repos, I noticed your message here about even links to the 2U forks being non-compliant. I just wanted to be extra sure that even those links must be removed, as I don't want to remove them unless absolutely necessary. See:

• https://github.com/openedx/enterprise-subsidy/blob/main/README.rst?plain=1#L14
• https://github.com/openedx/license-manager/blob/master/README.rst?plain=1#L11

[bmtcril]

Sadly that's correct. I've been told that we can't direct people out to repositories that we don't control.

[pwnage101]

I'm extra back from vacation and have filed tickets internally to make it so.