2024-06-27 Meeting notes

\uD83D\uDDD3 Date

27 Jun 2024

\uD83D\uDC65 Participants

Feanil Patel

⏪ Previous TODOs

Description	Assignee	Task appears on
Robert Raposa Follow up with in-progress repo items in the spreadsheet and ensure teams add a catalog file or give up maintainership by end of July.	Robert Raposa	2024-06-27 Meeting notes
Jeremy Ristau to follow up with 2U>Aurora and 2U>Purchase squads to document the maintainership transfer.	Jeremy Ristau	2024-06-27 Meeting notes
Jeremy Ristau will figure out if 2u-aurora still wants to own frontend-app-learning or if we should find a different maintainer	Jeremy Ristau	2024-06-13 Meeting notes
Robert Raposa Feanil Patel Review what legacy code exists for any frontend MFE that are part of the current release. Check to see if there are DEPRs for them or create the shell of the DEPR.	Robert Raposa	2024-05-30 Meeting notes
Jeremy Ristau ensure DEPR tickets are created for any frontend that can be deleted as a result of the new course-authoring MFE.	Jeremy Ristau	2024-05-30 Meeting notes
Chintan Joshi Update maintenance docs with guidance for when to merge regular dependency update PRs	Chintan Joshi	2024-05-23 Meeting notes
Kyle McCormick turn the Big Ideas google doc into issues and figure out how to organize them	Kyle McCormick	2024-05-23 Meeting notes
Feanil Patel Adolfo Brandes Write up a maintenance/depr ticket for dropping the way we do footers	Feanil Patel	2024-05-16 Meeting notes
Feanil Patel A quick how-to for updating an open-edx Python libraries to Python 3.11/12	Feanil Patel	2024-03-28 Meeting notes
Jeremy Ristau to make sure that the internal audit of ownership at 2U will end with an update to CODEOWNERS file to make that mapping public.	Jeremy Ristau	2024-02-08 Meeting notes

\uD83D\uDDE3 Discussion topics

Item	Presenter	Notes
edx-platform Maintenance Models	Feanil Patel	I’ve started a document, please add more ideas to it.
Swapping Maintenance Meetings	Feanil Patel	Agreed to swapping. edx-platform meeting will be after the full maintenance WG meeting.

Teams in Github as a communication form		There is not an escalation path for when a team is not being responsive. One solution: Escalate to the maintenance WG Previous Solution: Escalate to specific 2U contact points for PRs stuck on specific companies. Should teams that are maintainers be public to easily find specific people. For now, use the #wg-maintenance channel to escalate any PRs that are blocked on repos that have maintainers. Teams are not always properly updated in Backstage, Backstage is out-of-date compared to github.
Next 2 Meetings	Feanil Patel	Feanil and Kyle are both going to be at the Open edX conference and then on PTO. We can cancel the meetings or someone else can run them? We’ll re-convene on July 18th No meetings the next two weeks.
frontend-app-learning Hand-off	Feanil Patel	Can the 2U Aurora team post to hand off maintainership per https://docs.openedx.org/projects/openedx-proposals/en/latest/processes/oep-0055/decisions/0002-maintainership-transfer-process.html [JR] Will do this for fea-ecommerce as well.
frontend-app-ecommerce maintenance?	Adolfo Brandes	Is it being actively maintained? Is it still subject to the SOX thing? Can Axim (or CCs) start committing to it when necessary? (Such as.) Has it been DEPRd? Should it? Found a proposal: https://github.com/openedx/public-engineering/issues/22 And a roadmap issue: https://github.com/openedx/platform-roadmap/issues/83
Repo ownership clarification	Robert Raposa	Spreadsheet for finding maintainers Can we resolve repos with interest and no catalog? Note: Cookiecutters may incorrectly have 2U interest marked in the spreadsheet. There may be others, if there is no catalog file.
Adding Catalogs for things that don’t have owners		From Chintan Joshi I am creating catalog files for such repos which have no interest and no info etc I've finished PR for priority 1 on going work for priority 2 and should be done by Monday... and priority 3-4 I'll pickup next week

✅ Action items@

Jeremy Ristau to follow up with 2U>Aurora and 2U>Purchase squads to document the maintainership transfer.
Robert Raposa Follow up with in-progress repo items in the spreadsheet and ensure teams add a catalog file or give up maintainership by end of July.

⤴ Decisions

All teams that are maintainers should be public.