DEPR Project board

Mar 5, 2026

Feb 19, 2026

• Should we have a separate Abandoned status from Rejected?

  • This would make it easier to move tickets that have been sitting in Draft for a long time into Abandoned.

  • Distinction:

    • Abandonded: we don’t want to put more resources or attention into doing something, but we don’t want to stop anyone from picking it back up

    • Rejected: this was an active decision to not decide to move forward on something

    • Draft(with help wanted tag): this seems small enough for someone to pick up, but no one is actively working on

  • Next steps:

    • update the OEP with information above

      • ensure that comments in the tickets clearly indicate the reasoning behind ending up in those states

    • publicizing the different statuses

  • Action items:

    Deborah will speak to 2U enterprise teams about making DEPR tickets (for example: https://github.com/openedx/edx-enterprise/issues/2467 )

    Robert will make a PR for Abandoned/Rejected split

Feb 5, 2026

• Review draft column

  • Do we to put dates on things?

    • By default, we will set things to 6 months for periodic review. Other tickets might have different dates depending on what we decide during review.

    • Dates may be useful in specific cases, and then we’ll use them.

  • What is our criteria for closing tickets or putting things in Reject/Abandoned?

    • Plans have changed since the tickets were created.

  • What about tickets that are semi-abandoned but we still want to do?

    • Can we use our time to help craft better/clearer tickets out of these?

    • Add a label/tag for “help-wanted” to help us track these.

      • Things that are well-written and ready.

• Quick Question(s) about https://github.com/openedx/public-engineering/issues/316

  • Product team seems to think this is still an open question (i.e. Verawood “Decision: Keep or lose horizontal nav” – but given this DEPR, I think that decision has been made, to lose the horizontal nav?

  • There is a post-closure question on the DEPR issue: https://github.com/openedx/public-engineering/issues/316#issuecomment-3114152505 “does the scope of this task also include removal of those legacy waffle flags from edx-platform? A quick search indicates that they are still present.”

  • Answer: This is already unsupported in the Learning MFE, but the waffle flags are still lingering in openedx-platform. Asking AXIM to help finish cleaning that up.

Jan 22, 2026

• How to handle the repos that are being transferred in ownership

  • 2U can’t maintain some repos anymore (mostly enterprise related) and we need to make tickets for those repos.

  • 2U is trying internally to get a list of repos from former owners, but this process has been slow going.

• Legacy Libraries ticket being rewritten

  • Verawood will be the last release to support legacy libraries

    • Might have impacts on any instance still running off master (like MITx)

  • New ticket should have better migration information and a full migration plan

    • Mostly tying together a bunch of existing documentation

  • Ulmo has user-facing docs on this process already

• Do we consider Django Admin changes breaking changes?

  • Yes, even then

Jan 8, 2026

• Working on old Studio UI removal work.

• LMS UI removal tickets have been accepted.

  • Lots of unused pages that are not removed yet.

• Removing a temporary toggle that crosses a named release boundary.

  • Just needs a release note, but doesn’t need a full depr ticket.

• How are we tracking a decrease in the number of toggles?

  • We can count the number of annotated toggles.

  • New toggles might be pylint checked to ensure all new toggles are annotated.

  • 271 as of Teak

    • +2 between Sumac and Teak

  • Probably should check with Ulmo to see the delta.

• Draft column?

  • Dedicate a specific meeting to the draft column in the past