Overview
…
People
…
Processes
…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".
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 Tutor Adoption project board.
Groomed stories will be written as issues 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 board
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-initiative
Pages
Meeting notes, retros, and other documents will be put here:
| Child pages (Children Display) | ||
|---|---|---|
|