Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Trying not to dupe too much of MFE Rewrite Status , https://docs.google.com/document/d/1R7usm33eqj8-U3g_Kb7EHyMdP1jWe3q_0CZlg1uRuxY/edit , or https://github.com/openedx/wg-frontend/issues/156

...

  • This was used for testing out language/i18n switching functionality. Should we replace this?

Process/Next Steps Suggestions

  • Working agreements - who’s responsible for what

  • Synchronous & asynchronous ceremonies

  • Existing venues - DEPR working group, Product WG, Frontend WG, FedX

  • Bottleneck is on the PR reviews - how do we fix this?

  • New MFEs should be in the maintainership pilot - Feanil Patel

  • Venue for discussions?

  • When is next conversation on this topic?

  • Nominate DEPR WG meetings - next session Thursday, 4/6

  • Do we wait for modular MFE work?

    • Maybe only for writing new MFEs

  • Things that are almost removed – eg: 5% of features haven’t been ported, or they old version is only running in one environment – can be pushed over the line. <Insert link here>

  • Code analysis for dead/unused code. Things that have already moved to MFEs but have tendrils in edx-platform, like we did in the past with shoppingcart.

    • Sonarqube?

  • Identify “quick wins” that don’t require new MFEs, assign implementers

  • After the maintenance board is finalized and moved to openedx org, let’s move https://github.com/openedx/wg-frontend/issues/156 sub-tasks onto it for prioritization, assignment, and tracking

  • Who should write docs?

  • Who else should be involved?

  • How do we go through the list of endpoints above and map them to removal status/project?