2025-08-21 Meeting notes

__init__.py files and Pylint, and cross-repo issues.

@Robert Raposa

https://github.com/edx/edx-arch-experiments/issues/57

• Pylint issue can be fixed with either a new .github workflow (Robert will create an issue), or possibly through rust replacement for pylint, if it does not have the same issue.

  • There is a rule available in ruff to check for __init__.py, just FYI https://docs.astral.sh/ruff/rules/implicit-namespace-package/#implicit-namespace-package-inp001

• Meta conversation about the best place to add cross-repo enahncements:

  • Kyle: [proposal] put an issue here (.github) for things that concern every repo

    • Issue would require an action item to add a repo check to ensure the new workflow exists in every repo.

    • Possibly could get implemented by the maintainer, and possibly we find a volunteer.

    • repo-checkshttps://github.com/openedx/repo-tools/tree/master/edx_repo_tools/repo_checks#usage

  • public-engineering is a good place for an issue if you don’t know where it needs to go.

https://github.com/openedx/.github

@Adolfo Brandes

Node 22 and 24 upgrades

Adolfo has been busy with frontend-base

RG has several PRs for Node 22 and 24 upgrades. Will update the status of these for ready to review / not ready to review, and will post in the CC channel

We are still targeting Ulmo, so aim to get in before October. Adolfo needs to review.

There exists a big issue with a link to all the sub-issues: https://github.com/openedx/public-engineering/issues/407

React 19 upgrade

@Adolfo Brandes

Adolfo has been busy with frontend-base

Ulmo is unlikely

Not necessary for security (react 18 is still getting security patches), but good to have for DevX

• Could possibly come down through frontend-base, but not sure yet.

• Could point engineers asking for react 19 to tasks required to do so:

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

2u-orbi-bom permissions

@Robert Raposa

• @Robert Raposa TODO: Find public-engineering ticket for orbi-bom permissions.

• We are clear that orbi-bom won’t have CC for some time. We’ll need to complete the public-engineering ticket, which may entail finding new maintainers for certain repos.

2u-phoenix team

@Kyle McCormick

They maintain 3 repos, but have been disbanded/changed into 2u-catalog from Sonata

• Sonata is a company that 2U is contracting from

  • AppHelix is a Sonata sub-contractor

https://github.com/search?q=org%3Aopenedx%20%222u-phoenix%22&type=code

Will they continue maintaining or do we need to deprecate these / ask for new maintainers

FEATURES flattening

@Robert Raposa

Why the short breaking change window? Is it blocking work

• Yes, the PR is blocking settings followup work, and it ripe for rebase conflicts as long as it’s open

2U will try to meet the deadline but it will be an injection for robert and/or orbi-bom. But they can probably merge a quick version of this that meets the deadline and then do clean-up later.

Request from Robert: Ping him when it’s ready to merge and he’ll merge it so he can test on stage.edx.org

• We will do this if it’s convenient

• All agreed that this is not a long-term strategy for testing changes on master