Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

⏮️ Previous TODOs

DescriptionAssigneeTask appears on
  • Jeremy Ristau Talk to Diana about helping coordinate the django upgrade.
Jeremy Ristau2024-09-19 Meeting notes
  • Feanil Patel Drop in #ask-2u about the potential index changes with the next Django update so Ristau can connect us with SRE
Feanil Patel2024-09-19 Meeting notes
  • Next time: Discuss access for teams that maintain many repos across the org.
 2024-09-19 Meeting notes
  • Next Time: Continued discussion on whether we should change the Depr 6-month window approach. Should we have one big ticket for something like Python 3.8 or Node 18 and just start the 6-month clock once all the maintained repos have been updated?
 2024-09-12 Meeting notes
  • Feanil Patel ticket enabling cron CI of master every week so we know when external changes might have broken some repos that are usually not getting updates.
Feanil Patel2024-09-12 Meeting notes
  • Brian Smith will update the DEPR pilot issue with the exception for unmaintained repos. Something like “Once all maintained repos have dropped support for something (post 6-month window), it is fair game to drop support in any unmaintained repo.” but with examples of when this notification happens.
Brian Smith2024-09-12 Meeting notes
  • Next time: 6-month support window for simultaneous python versions doesn’t seem prudent
2024-09-05 Meeting notes
2024-09-05 Meeting notes
  • Kyle McCormick Next time: Py 3.13 or Py 3.12 for next upgrade? Take a look at the changelog.
Kyle McCormick2024-09-05 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 Ristau2024-05-30 Meeting notes
  • Chintan Joshi Update maintenance docs with guidance for when to merge regular dependency update PRs
Chintan Joshi2024-05-23 Meeting notes

\uD83D\uDDE3 Discussion topics

Presenter

Notes

Maintenance Update

  • Enzyme

  • Jest

  • Node

  • enzyme

    • just released repo using enzyme

      • cookie-policy-banner

      • igor and glib will take a look

    • some enterprise repos that weren’t switched over from enzyme to react-testing-library

      • no plan to fix this now, flagging for 2u teams that maintain these

    • is enterprise 2u specific? based on discovery findings

      • 2 instances of it being used, not to the degree where they want to maintain

      • maintenance limbo

      • pearson also has interest in using it

      • further investigation needed, regardless, we still need maintainer(s)

  • jest

    • mostly done

    • some non-enterprise repos still need jest landed

    • ecomm - feanil will follow up with new maintainers to see if they can take this on

      • NOTE: Maintainers will be merging to master branch of ecommerce repos without pinging 2U on sox compliance

  • node

    • brian smith is on vacation now,

  • PyPI Workflow Update PRs:

Jeremy Ristau

random inform (and win for FE plugins!)... an ai-translations repo was retired because it was replaced with the new plugin approach.

It was simple, seamless, and is a much better implementation than the original one!

Maintainership Update/Check-in


  • Farhaan’s Rights Expansion

  • First time we’ve made transfer of maintainership

  • Feanil will begin bugging maintainers that they are doing the small basic maintanance tasks - catalog-info, ci passing, etc

Cypress e2e tests DEPR

Maksim Sokolski

https://github.com/openedx/cypress-e2e-tests/issues/123
What was an intention to create the repo initially
Do we want to provide automation testing capabilities for Open edX?

Python 3.11/3.12 tracking

Robert Raposa

https://github.com/openedx/public-engineering/issues/234

Edx-platform Meeting Agenda Below Here

Resiliency in edx-platform roadmap ticket

Frontend Strategy for edx-platform

categories of remaining frontends

  • things that have an mfe <--- focus here

    • at parity

      • e.g. studio outline?

    • without feature-parity

      • e.g. authn?

      • e.g. learning

      • we need to push this using the DEPR process – either get the parity met, or decide to DEPR the lack of parity to move things forward

  • things that don’t have an mfe

    • but should

      • e.g. instructor dashboard

      • e.g. learner-facing support

    • but should stay static?

      • e.g. LMS catalog discovery and about pages

    • but should be removed?

      • e.g. django-wiki

  • pages that will be rendered by django but don’t involve having frontend tooling in edx-platform

    • django admin pages

    • xblock views, eventually

are we racing against frontend-app-shell?

  • kinda

  • we need to coordinate - ideally we build shell components instead of standalone mfes

✅ Action items

⤴ Decisions

  • No labels