Tutor Adoption Requirements by Squad - 2U/OCM

List of repositories and current support status: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3349840611

 

Tutor service/plugin requirements

List of services and MFEs and Tutor plugins each team must have support for in order to adopt Tutor for daily development work.

Squad

Must Have

Nice to Have

Squad

Must Have

Nice to Have

arbi-bom

LMS

  • course-discovery

  • ecommerce

  • insights

arch-bom

LMS

 

content-tnl

  • LMS

  • CMS

  • frontend-app-learning

coursegraph, blockstore, codejail, frontend-app-library-authoring, frontend-app-course authoring,

content-aperture

 

 

content-aurora

 

 

content-cosmonauts

  • LMS

  • CMS

  • frontend-app-learning

  • edx-proctoring (LMS plugin)

  • edx-analytics-api

  • edx-analytics-dashboard

content-infinity

 

 

content-phoenix

 

 

engagement-engage

 

 

engagement-revenue

 

 

engagement-vanguards

 

 

engagement-discover

 

 

engagement-mobile

 

 

enterprise-titans

 

 

enterprise-yonkers

 

 

enterprise-quokkas

 

 

enterprise-markhors

 

 

Tutor feature requirements

List of features believed to not yet be present in Tutor which are blocking each squad from adopting Tutor for daily development work. (Some of these features may actually be present, but hard to either discover or use in their current state.)

Squad

Must Have

Nice to Have

Squad

Must Have

Nice to Have

arbi-bom

 

 

arch-bom

  • Installation of edx-platform plugins into a folder on host OS, for local development (e.g. like the /src directory in devstack).

 

platform-tnl

 

 

aperture

 

 

aurora

 

 

content-cosmonauts

  • edx-platform plugin development

 

engagement-revenue

 

 

engagement-vanguards

 

 

enterprise-titans

 

 

infinity

 

 

quokkas