[BD-14] Engineering sync 2020-02-04
M2.5 scoping pulse
@Marco Morales (Deactivated) is leaning towards keeping M2.5 scope as low as possible, aiming to pilot it to our biggest v1 Content Libraries power-using partners.
Decision: No randomization for M2.5
Question: Sourcing from multiple libraries?
Question: Course-level overiddes to settings - how should they look?
UI level
Database level
Component editor shimming vs. modernization
@Former user (Deleted) - any updates on your feelings about the effort of shimming vs. modernizing the old editors?
Just to confirm - this includes Video, Capa, and HTML, correct?
If we modernized Capa, we’d probably just reach for the interactive problem editor.
For Video/HTML, our UX team could do some greenfield design, but we’ll want to begin that soon.
Recommendation: Shimming will be significant time investment
50%+ of time that it would take to modernize editors, probably
v2 library import/export/inclusion specifics
Dave and I began talking through this
Adolfo, the comments in https://openedx.atlassian.net/browse/TNL-7454 give a good overview of how this works in v1 libraries and some of the pitfalls.