This is a living document and will change as active team/theme development moves through the system. If you notice that things are out of date, please update as needed. If you're unsure, leave a comment with a question! Thanks 
Summary
This page is meant to capture the parts of the system that are actively being worked on by teams at edX and how to triage and how/where to ask for help. Additional context on components can be viewed with the full listing of Platform Areas and Product Components.
The "Planned Sustaining Date" represents the goal date that the theme work will move into a sustaining phase. This date occurs after the current active work has been complete and is in a healthy state, depending on ownership this may also include that the proper knowledge transfers and trainings have been complete to ensure a proper hand-off.
Ownership responsibilities have been defined at a high level within this document. The notes captured here are currently to help provide guidance on where to go to for questions and knowledge support.
Discovery Theme
Active Product Development Areas
| Platform Area | Product Component(s) | Description | Triage Steps | Where to start with any additional questions (for learning & clarification) | Status | Planned Sustaining Date |
|---|---|---|---|---|---|---|
| Catalog & Publishing | Course About Pages Program About Pages In relation to Prospectus aka "new pages" Topic Pages | Discovery is creating a new frontend system for our marketing site and pages. This is called Prospectus and is written in GatsbyJS. They have rolled it out for a subset of Course About pages and have been spoken of as the "New Course About Pages." They have a new user experience and will be best handled by the Discovery team who has the most context. (Jasper Ho can you provide context of which types of pages fall into this category?) | If a ticket comes in relating to any new Course About Pages:
| Discovery Squad (multiple teams/pods here) edX Internal Slack: #discovery | ||
| Catalog & Publishing | Course Publishing Workflow Publisher | Discovery has taken on the task of creating a new Publisher frontend as well as having done some data clean up work to help prevent/reduce data reversions that we had been used to seeing. They are not doing a lot of active changes within the existing Publisher as the team is currently working on building out the new frontend, but they should be kept up to date with work our team does in case it is related to their changes / so they are aware as they plan their roadmap. | For incoming Publisher issues:
| Discovery Publisher Pod edX Internal Slack: #disco-publisher | ||
| Catalog & Publishing | Other Marketing Pages (Institution / Subject / Profile) Topic Pages | Discovery has launched 15 new Topic pages for Computer Science and Data Science courses. To see the list of Topic Pages that were launched check here. | If a ticket comes in relating to any new Topic Pages:
| Discovery Squad (multiple teams/pods here) edX Internal Slack: #discovery |
Ownership Repos
| Repo | Description | Triage Steps | Where to start with questions (for learning & clarification) |
|---|---|---|---|
| course-discovery | edX Internal Slack: #discovery | ||
| edx-mktg | edX Internal Slack: #discovery | ||
| prospectus | edX Internal Slack: #discovery | ||
| publisher | edX Internal Slack: #disco-publisher |
Master's Theme
Active Product Development Areas
Master's product delivery overview (Q3/Q4)
| Platform Area | Product Component | Description | Triage Steps | Where to start with any additional questions (for learning & clarification) | Status | Planned Sustaining Date |
|---|---|---|---|---|---|---|
| Content & Authoring | Content: Special Exams (Proctored, Timed) aka Proctoring | The team is working on adding a new integration/provider option into edx-proctoring. They are working to make changes to the existing system to support this new integration and likely will have the expertise and context around the edx-proctoring system. They are still in active development phase and the new integration has not yet been rolled out fully. | For incoming Proctored Exam issues:
| Master's Dahlia Team edX Internal Slack: #masters-proctoring | ||
| Content & Authoring | Course Grading Policy & Tools aka Gradebook & potentially Grades | Gradebook is a new micro-frontend that will be used for Master's partners when viewing and editing learner grades. We should not yet be seeing any Gradebook issues as it has not been released to all users and currently is in a pilot phase with a small subset of partners. There have been some underlying changes with Grades in the process of the team's work, They are not actively working on making changes to how grades are calculated, but may have the knowledge and context around issues that arise. | For incoming Gradebook issues:
For incoming Grades issues:
| Master's Neem Team edX Internal Slack: #masterdevs | V1 Delivered, V2 Pending | |
| Platform & Infrastructure | Registrar service | As part of running and administrating Master programs, edX needs integration with Masters degree conferring schools. Registrar service is our integration layer with Schools systems. It manages information like Program Enrollment and Program course enrollments. | No data should be live for these efforts. There shouldn't be any escalation issues for these yet. | edX Internal Slack #masterdevs | In Progress | |
| Learner Experience | Master Track | We need a way to provide Master level features for Masters students in a course. Those are driven off Master Track of the course enrollment. | No data should be live for these efforts. There shouldn't be any escalation issues for these yet. | edX Internal Slack #masterdevs | In Progress | |
Ownership Repos
| Platform Area | Repo | Description | Triage Steps | Where to start with questions (for learning & clarification) |
|---|---|---|---|---|
| Learner Experience | credentials | edX Internal Slack: #masterdevs | ||
| Learner Experience | edx-certificates | edX Internal Slack: #masterdevs | ||
| Content & Authoring | aka LTI Tool Consumer | edX Internal Slack: #masterdevs | ||
| Content & Authoring | proctoring | edX Internal Slack: #masters-proctoring | ||
| Content & Authoring | gradebook | edX Internal Slack: #masterdevs |
Revenue Theme
Active Product Development Areas
| Platform Area | Product Component | Description | Triage Steps | Where to start with additional questions (for learning & clarification) | Status | Planned Sustaining Date |
|---|---|---|---|---|---|---|
| Commerce & Payment | Feature Based Enrollments (FBE) New Revenue Model for edX | Feature Based Enrollments (FBE) is the name of the project for the new revenue model that has been rolled out on the platform. FBE changes the definition of the free and paid tracks at edX. The Revenue team is still actively working on this system. They are actively experimenting in this area. | For any FBE specific issues:
| edX Internal Slack: #revenue-engineering | Launched | |
| Multiple | Site-wide experiments | The Revenue squad is actively running a wide variety of experiments across the system related to payment and payment pathways. You may encounter these experiments when manually testing and/or triaging issues. An example experiment is a banner that is visible inside courses that offers a 15% off discount to users who have never paid before. | For anything that looks like an experiment causing issues on the production site:
| edX Internal Slack: #revenue-engineering | Ongoing | |
Ownership Repos
| Platform Area | Repo | Description | Triage Steps | Where to start with questions (for learning & clarification) |
|---|---|---|---|---|
| Commerce & Payment | ecommerce | edX Internal Slack: #ecommerce-guild or #revenue-engineering | ||
| Platform & Infrastructure | edx-ace | edX Internal Slack: #revenue-engineering | ||
Architecture Theme
Active Product Development Areas
| Platform Area | Product Component | Description | Triage Steps | Where to start with additional questions (for learning & clarification) | Status | Planned Sustaining Date |
|---|---|---|---|---|---|---|
Platform & Infrastructure | Micro-frontend Runways (deploys, authn, i18n) | edX Internal Slack: #dev or @arch-team within any channel
| ||||
Learner Experience | Learner Profile and Account Settings | edX Internal Slack: #dev or @arch-team within any channel
| ||||
Content & Authoring | Blockstore | edX Internal Slack: #dev or @arch-team within any channel
|
Ownership Repos
Note: if your questions will include specific user information, do not use the Open edX Slack
| Platform Area | Repo | Description | Triage Steps | Where to start with questions (for learning & clarification) |
|---|---|---|---|---|
| Multiple | edx-platform | edX Internal Slack: #dev or @arch-team within any channel | ||
| Platform & Infrastructure | authn/authz | Open edX Slack: #architecture edX Internal Slack: @arch-team within any channel | ||
| Platform & Infrastructure | django-openid-auth | Open edX Slack: #architecture edX Internal Slack: @arch-team within any channel | ||
| Platform & Infrastructure | BlockStore | Open edX Slack: #architecture edX Internal Slack: @arch-team within any channel | ||
| Platform & Infrastructure | Unified Header | Open edX Slack: #architecture edX Internal Slack: @arch-team within any channel |