Build a roadmap/board that allows easy identification of upcoming monolith deprecations and their MFE replacements

[jmakowski1123]

Problem

There is too much of a lack of adherence to deprecation standards and it negatively impacts MFE workflows. In at least one case, a new MFE has replaced a pre-existing IDA without porting commonly used features. This has to be avoided in the future. There is often a lack of awareness among any Open edX user who did not initiate the deprecation process and thus may not be aware that it is happening.

Product/Platform Value

A transparent deprecation process will allow users of the platform to not only plan ahead accordingly, but to have a say in the deprecation itself.

Acceptance Criteria

A comprehensive and regularly updated Kanban Board that includes: 1) all monolith deprecations and 2) their MFE replacements.

Related or in-progress work

Open approach questions:

A current DEPR board does exist. Investigate where the MFE-specific gaps are. Do we need to build a separate board that focuses on the DEPR initiatives only that contain MFE replacements? Or can this layer be built into the current DEPR board, perhaps with an intentional approach to labeling?

Contingencies

No other tasks on the MFE Roadmap are contingent on this task being completed. The deprecation tasks are the openedx/axim-engineering#1 priority, but they can happen simultaneously with other initiatives.

[arbrandes]

I think we can use the current Frontend WG board for this. There's an epic in progress for this very issue already. We can capture progress in that epic via sub-issues, which should be pretty transparent and visible.