Hold on, folks! Just because some MFEs got Olive branches does not mean we have to include them in Tutor!
tutor-mfe maintainer and tCRIL’s frontend guy, I took the liberty of assigning myself Olive: list of new MFEs · Issue #200 · openedx/build-test-release-wg · GitHub. I’ve been having conversations with people about this, this week, and here’s where we stand:
Do we need to include every MFE in that list in Tutor/Olive?
MFE developers (as of now mostly employed at or by 2U) are aware they can’t remove a feature in edx-platform before the MFE that replaces it is officially accepted as being production-ready by the community. This should apply to each MFE in that list, and it means we don’t have to enable any of them for Olive if we don’t want to.
How do we decide which ones to include?
TLDR: Don’t know. We need to decide how to decide.
While the ultimate decision on whether an MFE is ready is in fact up to the community, and in particular, the BTR group, there is no official method to arrive at this decision. This is a problem we should fix pronto, precisely so we can answer the question of which ones to include.
This comment in the ticket where we’re tracking this question is a collation of the information I could find. Please refer to it and add your comments, including which MFEs you would like to have included, and why. Once we have a reasonable idea of where the community’s opinion lies, we can start to narrow down the list in a technical fashion: by checking each MFE against the criteria.
(And yes, right off the bat it looks like a sine qua non criterion is whether the MFE supports runtime configuration.)
TLDR: Let’s consult the Product Working Group as well.
There are product considerations to take into account. Ultimately, I think the list will be narrowed down a lot by them. I’m not saying they have ultimate say, but it doesn’t make sense to start maintaining Tutor support for an MFE if it doesn’t make sense to make it part of the Open edX product at a given point in time.
I’ve started discussing this with @jmakowski, yesterday. The short of it is that my job will be to try and put all stakeholders together (mostly asynchronously, such as via this post) so we can decide ASAP which MFEs to work on for Olive.
(Committing additional BTR “taggery” for awareness: @pdpinch, @ghassan, @sambapete, @BbrSofiane, @Dean, @kmccormick)