Review TODOs from Last time

@Feanil Patel

• Mongo upgrade needs 2U help to test for edx-platform.

  • Prioritize being able to run edx-platform tests on both mongo 4 and mongo 6.

  • Tests can be run on other infra than 2U but may need more research.

    • https://github.com/openedx/edx-platform/blob/master/.github/workflows/unit-tests-gh-hosted.yml

    • vs

    • https://github.com/openedx/edx-platform/blob/master/.github/workflows/unit-tests.yml

• Ecommerce

  • edunext is more interested in enterprise than in ecommerce. But currently we need ecommerce for enterprise.

  • They can currently devote 2hrs a week to keep the lights on but not

• Ownership

  • Already posted: Maintainers Requirements Update

  • Feanil will post a list of repos today or tomorrow.

Ubuntu Upgrade

@Tobias Macey

MIT already running using Debian Buster instead of Ubuntu and using standard python Docker Images

• Reduces usage of other infra like the deadsnakes PPA.

• Using the external codejail service and building that against the Ubuntu container.

  • Using a sudoers profile inside the code jail service image.

Node 18 → 20 Upgrade

@Feanil Patel

Looks like we’ll have to accelerate this upgrade to keep things functional. @Adolfo Brandes can you provide some context here?

Context:

• The upgrade from Node 16 to 18 took a long time, and a lot of coordination. We still have time until Node 18 is EOL (April 2025), but some packages have started to drop support for it already, leading to complications when upgrading related dependencies.

• Renovate has already started to open 18 → 20 upgrade PRs.

• To get in front of it, we should elect somebody to start the discovery and coordination work, and set a tentative target: Sumac.

• Tutor only supports one version of Node in production for MFEs

  • Can we change something in the tutor plugin to bring up a second container for some of the MFEs?

    • @Régis B. people are concerned that a PR to run 2 images would be to clunky to be accepted by the tutor team. Do you have thoughts on how we could incrementally upgrade MFEs without having to do a big bang upgrade of all of MFEs.

    • We’re going to have more MFEs in the future and doing a big bang upgrade can be more costly.

    • Note: In the future we will have the same problem with Piral so we may be stuck with this.

      • https://github.com/openedx/open-edx-proposals/pull/410

      • Piral Slack room: https://openedx.slack.com/archives/C06HRLTP3E0
        
        

Moving NPM workspaces

@Adolfo Brandes

Turns out it’s a pretty manual process. @Brian Smith and now @Yagnesh Nayi have been contributing PRs, but as usual, the more contributors, the merrier!

Main ticket (see referenced issues towards the bottom of the feed): https://github.com/openedx/axim-engineering/issues/23

• This wiki page may be helpful: NPM Scope Change

Maintenance burden of org-specific code

@Adolfo Brandes

In going through the above (in particular, when upgrading frontend-app-course-authoring dependencies), we found that the Video Upload feature is not realistically usable by the community. Not only that, it’s not feasible to run it locally for the purpose of, for example, fixing unit tests. We proposed that in such situations, the unit tests be disabled / made non-blocking as a workaround, and long-term, the feature should be pluggified, deprecated, or put in the docs and other work to make it usable by the community.

• We’re aware that we don’t have a single plugin API that we’re going with yet.

• Can the tests be run elsewhere?

  • How do we run the tests sometimes?

    • This is in Jest, there is some capability for optionally running tests.

• How can 2U know that 2U specific tests were disabled?

  •  

Ruby Upgrade in Comment Service

@Maksim Sokolskiy

What’s the plan with the ruby upgrade?

• Feanil will prioritize finding a maintainer for this so we can get the Ruby upgrade going.

•  

Central vs Distributed Tasks for Upgrades

Who will be in charge of the centralized tasks for upgrades?

• This group

• We’ll need help with both the creation of tasks and driving them forward with maintainers

• Feanil will make board

  • Will reuse or replace https://github.com/orgs/openedx/projects/51

• Product roadmap will also have line items for main upgrade epics.

• Difference between transparency and visibility

  • A board is useful, but comms is still important.

  • Ristau would be happy to help bolster some of the communications and visibilty steps moving forward.

Historic edx-platform maintenance state

@Kyle McCormick

We had a central team that would route to experts within 2U. We think that was a good system but we would want to build that with CCs instead of a 2U internal ownership delegation.

• Michelle was historically doing the routing within edx-platform to 2U.

• More recently the BOM team tried to take over and that was badly timed.

• Be mindful about the difference between the alerting setup within 2U which will remain internal and the routing for PR reviews which will become public.

• Should we be switching to CODEOWNERS instead?

  • CODEOWNERS is not super visible and does not get info to the owners quickly.

  • CODEOWNERS currently auto assigns PRs

Impending Redwood Upgrades

• More important than getting the full ownership mapping.

• For now focus on the upgrades we need for Redwood.

  • Python 3.8->3.10/11/12

  • Mongo 4->6

• Feanil will work on making tickets for all edx-platform python packages