| Info |
|---|
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 helpdocument the automation rules for incoming bugs being reported and how to minimize feedback loops where possible. 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
...
Engagement Theme
Automation Rules
...
Master's Theme
...
| Platform Area | Product Component(s) |
|---|
| Automation |
|---|
| Squad Details | |
|---|---|
| Catalog & Publishing | Course About |
Page, |
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?)
- Triage & create the Prod ticket, then tag Mike Dikan (Deactivated) (Discovery Eng Lead) & Gerrit Orem (Deactivated) (Product Manager) to provide triaging support for Discovery team development.
Discovery Squad (multiple teams/pods here)
edX Internal Slack: #discoveryPage, | CR
Eng Ticket
| Website Squad Eng Lead: Albemarle (Deactivated) Product Lead: Gerrit Orem (Deactivated) |
| Catalog & Publishing | Course Publishing Workflow |
Publisher
- Triage & create the Prod ticket, tag Jason Myatt (Deactivated) (Publisher Pod Team Lead) for context & to ask if the experience is related to active work - not all Publisher issues coming in relate to ongoing Publisher work, but the team should be made aware of what changes our teams are making and may be able to provide knowledge sharing.
Discovery Publisher Pod
edX Internal Slack: #disco-publisher
Other Marketing Pages (Institution / Subject / Profile)
Topic Pages
- Triage & create the Prod ticket, then tag Mike Dikan (Deactivated) (Eng Lead) & Gerrit Orem (Deactivated) (Product Manager) to provide triaging support for Discovery team development.
Discovery Squad (multiple teams/pods here)
edX Internal Slack: #discovery
Ownership Repos
...
CR
Eng Ticket
| Publisher Squad Eng Lead: Jason Myatt (Deactivated) | ||
Programs Theme
Automation Rules
/wiki/spaces/PROD/pages/933200139
...
Learners are offered a discount for their first verified certificate upgrade. It applies to most learners, but not all. The discount is advertised to them in the courseware. The discount is automatically applied during checkout.
The Revenue squad is planning on continuing to experiment in this area.
...
For any issues related to the discount banner or the applicability of the discount:
- Tag Emma Green (Deactivated) and Shelby Quinn (Deactivated). They will work within their team to resolve issues as they are still actively working on and improving this product feature. It's OK to tag them if you are unsure, they will quickly be able to tell you if it is an ongoing experiment or not.
...
Ownership Repos
...
edX Internal Slack: #ecommerce-guild or #revenue-engineering
...
Architecture Theme
Active Product Development Areas
...
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
| Info |
|---|
Note: if your questions will include specific user information, do not use the Open edX Slack |
edX Internal Slack: #dev or @arch-team within any channel
Open edX Slack: #architecture
edX Internal Slack: @arch-team within any channel
edX Internal Slack: @arch-team within any channel
edX Internal Slack: @arch-team within any channel
edX Internal Slack: @arch-team within any channel
| Platform Area | Product Component | DescriptionAutomation | 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 | Delivered | Content & Authoring | Course Grading Policy & Tools aka Grades | Master's Neem Team edX Internal Slack: #masterdevs | V1 Delivered, V2 Planning | 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
...
aka LTI Tool Consumer
...
Revenue Theme
Active Product Development Areas
...
Feature Based Enrollments (FBE)
New Revenue Model for edX
...
For any FBE specific issues:
- Tag Gabe Mulley (Deactivated) (Revenue Eng Manager) and Shelby Quinn (Deactivated) (Product Manager) for any FBE specific issues for the Revenue squad to triage and prioritize. They will work within their team to resolve issues as they are still actively working on and improving this product feature.
...
For anything that looks like an experiment causing issues on the production site:
- Tag Gabe Mulley (Deactivated) (Revenue Eng Manager) and Shelby Quinn (Deactivated) (Product Manager). They will work within their team to resolve issues as they are still actively working on and improving this product feature. It's OK to tag them if you are unsure, they will quickly be able to tell you if it is an ongoing experiment or not.
...
| Squad Details | |||
|---|---|---|---|
| Content & Authoring | Content and Authoring: | CR
Eng Ticket
| Master's & MicroMasters Squad Eng Lead: Mat Carter (Deactivated) Product Lead: Deen Abdul-Hathi (Deactivated) |
| Learner Experience | Master Track | CR
Eng Ticket
| Master's & MicroMasters Squad Eng Lead: Simon Chen Product Lead: Deen Abdul-Hathi (Deactivated) |
Platform Theme
Automation Rules
| Platform Area | Product Component | Automation | Squad Details |
|---|---|---|---|
edX for Business Theme
Automation Rules
| Platform Area | Product Component | Automation | Squad Details |
|---|---|---|---|
| Business & Enterprise | *any | CR
Eng Ticket
| * S&E team looks at these tickets in the queue to check if they are Ent specific or more broad in scope |