Page Comparison

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:

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

  • maintainer - please merge

  • unmaintained repos - feanil will merge

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

• https://github.com/openedx/edx-platform/issues/35144

• Also, Tim made a fix which we might want to back-port.

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

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