2025-07-24 Meeting Notes

2025-07-24 Meeting Notes

All public Working Group meetings follow the Recording Policy for Open edX Meetings

 Date

Jul 10, 2025

 Participants

  • @Kyle McCormick

  • @Chintan Joshi

  • @Adolfo Brandes

  • @Usama Sadiq

  • @Maksim Sokolskiy

  • @Sarina Canelake

Previous TODOs

 Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

Make Upgrade for forks

Usama Sadiq

Created one PR Add Custom make-upgrade workflow for forks by UsamaSadiq · Pull Request #37064 · openedx/openedx-platform to setup the make upgrade workflow to run on the forks too.

 

 

 

Access for the AppHelix team?

Robert Raposa

Should they get same permissions as arbi-bom team and add them to maintainers-at-large.

  • Use the Core Contributor plan for the team’s progress

  • Repos: GitHub

    • How should they be maintained in the next few months?

  • Full-time contributors, depending on various variables, could be ready to be CCs in 3-6 months.

    • Robert: JR is not pushing for this team to be CCs

      • This needs confirmation

    • Kyle: If anyone from AppHelix is interested in working towards being a core contributor (the same way any community member would), we are happy to support that – 2U, let us know how we can

 

 Action items

@Adolfo Brandes Topic for next time: Starting the React 19 upgrade
@Adolfo Brandes Node 22 and 24 upgrades
Next time: [Robert] [Does Jeremy want this if I am absent?] Discussion about linting for __init__.py files, and meta conversation about these types of cross-repo proposals. See comment in Missing __init__.py files causes pylint to fail to lint some modules · Issue #57 · edx/edx-arch-experiments

 Decisions

  1. We should only do edx-platform frontend upgrades if they are easy or if they are very important. This includes React and Paragon. Revisit this decision once the only thing left is XBlock view support.