Overview
Goal: Drive adoption of Tutor as the unified, extensible, easy-to-use development environment for Open edX.
Epic Breakdown | Project Board
People
Régis B.: Tutor Maintainer
Kyle McCormick: tCRIL
Edward Zarecor: tCRIL
Diana Huang: edX
Processes
Task tracking
We will plan and track this initiative in GitHub.
Epics
Epics are represented as issues on the Open edX community roadmap. To see all epics for this project, filter the Effort
attribute for "Tutor as DevStack" (linked in Overview section).
Each epic will contain a task list of groomed stories, such as on this CourseGraph plugin epic.
Stories
We will propose, groom, prioritize, and track issues on the project board (linked in Overview section).
Un-groomed stories will start on the project board as issues in the 2u-tutor-adoption repository.
Once groomed, the issue may be moved to a more specific repository, for example:
overhangio/tutor
for fixes/improvements needed in the core Tutor repo,<org>/tutor-<plugin>
for tasks relating to specific Tutor plugins,openedx/devstack
for devstack cleanup steps,openedx/tcril-engineering
for tCRIL-specific tasks,etc.
If no appropriate repository exists, or the most appropriate issue repository has its issue tracking disabled, it is fine for the ticket to stay in 2u-tutor-adoption.
Meetings
We will meet in this Google Meet room.
Meeting cadence: As-needed.
Comms
Help requests go on the Tutor forums.
Technical discussion can go on the project board, PRs, or the forums.
Open edX Slack room for logistics (public): #tutor-adoption
Pages
Meeting notes, retros, and other documents will be put here:
Some old Google docs:
https://docs.google.com/spreadsheets/d/12MxCu6Z3lzbF8Z6t2B39y73r65PjiwPnvwb3gHkkKD8/edit#gid=0 - will be moving these items to the project board
https://docs.google.com/document/d/1DfoCRz3xRa2kufCwP511s61f7WpX6BjZfr1OOFWzyCA/edit