Note |
---|
This is an archive of an old page. Perhaps you want one of: |
Overview
Goal: Drive adoption of Tutor as the unified, extensible, easy-to-use development environment for Open edX.
Epic Breakdown | ➡ Project Board⬅
People
Kyle McCormick: Project Lead, Developer @ tCRIL
Régis B.: Tutor Principal Maintainer
Kyle McCormick: tCRIL
Edward Zarecor: tCRIL
Diana Huang: edX
Rebecca Graber (Deactivated): Developer @ edX/2U
Carlos Muniz : Developer @ tCRIL
Maria Fernanda Magallanes Z : Developer @ eduNEXT
Jenna Makowski : Open edX Product Manager @ tCRIL
Processes
Task tracking
We will plan and track this initiative in GitHub.
Epics
Epics (aka Milestones) 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" .
Each epic will contain a task list of groomed stories, such as on this CourseGraph plugin epic.
...
(linked in Overview section).
Epics are also copied into the project board as a filter-able attribute. Stories can be moved between epics by drag-and-drop or by editing the value of the “Epic” column (see drop-down in the bottom right):
...
Issues
We will propose, groomrefine, prioritize, and track issues on the Tutor DevEnv Adoption project boardGitHub Project board (linked in Overview section).
Groomed By default, stories will be written as issues created in the most relevant repository (tutor, devstack, etc.). When no relevant repository exists and/or issue tracking isn’t enabled for the repository, the generic public-engineering repository is a fine place for issues.Un-groomed stories will be “draft issues” on the project board2u-tutor-adoption repository. Additionally, some stories will be included on the board from other repositories. For example, stories relating to the Tutor CourseGraph plugin exist in the tutor-contrib-coursegraph repository.
Meetings
We will meet in this Google Meet room.
Meeting cadence: As-needed.
Comms
Help requests go on the Tutor forums.Open edX Slack room for logistics (public): #tutor-adoption
Technical discussion can go on the project boardGH issues, PRs, or the forums.
Open edX Slack room for logistics (public): #tutor-adoption-initiative
Requests for Tutor support are best done via the standard process: the Open edX forums. If necessary, though, folks helping with this project can escalate to Régis and/or Kyle via the #tutor-adoption
Slack channel.
Pages
Meeting notes, retros, and other documents will be put here:
Child pages (Children Display) | ||
---|---|---|
|
Other docs:
https://docs.google.com/spreadsheets/d/12MxCu6Z3lzbF8Z6t2B39y73r65PjiwPnvwb3gHkkKD8/edit#gid=0 : Will be moving these items to the project board.
Tutor Analysis : Some evaluation Feanil did last year with some insightful Q&A.
https://docs.google.com/document/d/1DfoCRz3xRa2kufCwP511s61f7WpX6BjZfr1OOFWzyCA/edit