Page Comparison

• Deprecation of Old edx-platform Frontends

• in the future we want teams to do this as part of the replacement

• but for now, we have some ones that us edx-platform maintainers will need to take care of

  • Existing MFEs with corresponding Legacy Code

• where to track tasks for removing old studio frontends?

  • Jeremy’s teams use jira

  • the more that we have in github, the more we could have other maintainers help

• Plan

  • Studio frontends

    • public DEPR ticket owned by Jeremy Ristau

    • internal 2U Jira tasks to drive removal by sumac

    • generate some “how to remove” notes for community to use in LMS removals

  • LMS frontends

    • public DEPR ticket(s) – we need to find CCs as owners

• Testing Environment - https://docs.tutor.edly.io/tutorials/nightly.html

• PR Review/Security Review
  

• Maybe start with making the items visible in Slack as a way to start seeing what needs to be done and making the work visible to all CCs.

  • #cc-edx-platform should work

• 
  

• Divvying up maintainer-ship of edx-platform folders

• Paver Task Replacement

• Same question around timing/coordination

SWITCH to full Maintenance WG

• Node 20 Upgrade

• What should the timing of this be?

• Front-end engineers that I’ve spoken to are skeptical that we can run both at the same time.

• https://github.com/openedx/public-engineering/issues/229

• We will try to do both and Adolfo Brandes will coordinate the Node 20 Upgrade tasks with the relevant repo maintainers.

• Maintainership for frontend-app-learning

Tim

• This repo is getting PRs on a regular basis but reviews are not happening in a timely manner.

  • If there are people interested in becoming CCs of frontend-app-learning, please nominate them.

• Codecoovvvvv

Kyle

• It’s complicated.

  • They made a big breaking change to their API, rather than having a token for the org, it requires a repo specific token.

  • This means sometimes they use an old api when the token doesn’t exist and the old API can get rate limited.