2024-03-28 Meeting notes

Begin Recording

edx-platform Meeting

• Which Repos need Python 3.11 Tests

  • All relevant Repos are Tracked under here: https://github.com/openedx/edx-platform/issues/34229

    • For these if possible you should add 3.12 testing now unless there is an issue preventing it (like it uses numpy/scipy).

• All others repos will target 3.12.

• Redwood cut is 1.5 months from now and we’re not seeing a lot of activity on

• Chintan/Feanil will do an example upgrade and write up a wiki page for upgraders (of libraries, in particular).

  • Kyle will add help-wanted labels to small repos and send out a call for help.

  • Will 2u teams be able to help pile on these package upgrades?

    • → Jeremy will ping them

    • Feanil: Python upgrade is higher priority than React upgrade due to support windows

  • reminder: assign yourself (or use assign me command) as a way to say that you’re working on it

  • One item to add to that page: Pay attention whether it’s 3.12 optional, or 3.12 required, or 3.12 not possible (scipy/numpy dependencies)

• Kyle McCormick will look at edx-sandbox / codejail-includes

  • lock current py38 requirements file and make a new one

  • to do: look into that and write up the plan

• libsass update - on track to completion

  • https://github.com/openedx/edx-platform/pull/34318

  • https://github.com/openedx/edx-platform/pull/34439

• OSPRs in edx-platform

  • What is the new escalation path?

    • Escalate to CCs instead of Arch-BOM

Python 3.11 Risk

Feanil Patel

• Release is going to be cut Apr 28, wihch means we don’t have a lot of time to get changes landed. We need the work prioritized.

2U CCs Conversation Update

Feanil Patel

• Gonna discuss with the TOC will have more updates soon.

Next steps for PR management

Tim Krones

• 2 Questions about Automation

  • Are we ready to automate steps Michelle and Tim are doing?

    • Letting the PR authors know who they can reach-out to when items are ready for review.

    • We’re ready to update messaging for the openedx-webhooks bot

      • https://github.com/openedx/openedx-webhooks/tree/master/openedx_webhooks/templates

      • Mention @maintainer-name instead of @maintainer-name so that PR authors know who to ping without immediately pinging them

      • openedx-webhooks code is gnarly, feel free to ping #openedx-webhooks for help

  • Who would handle that work? Does it need to be Axim.

    • No, we would appreciate contributors, but we could support

Maintenance tickets on open edx roadmap

Jeremy Ristau

Should top-level maintenance initiatives be on the Open edX Roadmap board?

• Feanil: yes, I think so