Versions Compared

Old Version 11

changes.mady.by.user Zachary Rockwell (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Feanil Patel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



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 (smile)

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

Platform AreaProduct Component(s)
DescriptionTriage StepsWhere to start with any additional questions (for learning & clarification)StatusPlanned Sustaining Date
AutomationSquad Details
Catalog & Publishing

Course About

Pages

Page,
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

Page,
Discovery Cards,
Drupal Infrastructure,
edX Marketing Homepage,
Other Misc Marketing Pages

CR

Eng Ticket

  • Project: Website (WS)
  • Status: Backlog

Website Squad

Eng Lead: Albemarle (Deactivated)

Product Lead: Gerrit Orem (Deactivated)


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:
  • Tag Albert (AJ) St. Aubin (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

V1 Delivered, V2 PendingPlatform & Infrastructure

Registrar service

Master track

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. 

At the same time, 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 #masterdevsIn Progress

Ownership Repos

...

Master's Theme

Active Product Development Areas

...

CR

Eng Ticket

  • Project: Discovery (DISCO)
  • Status: Needs Triage
  • Labels: publisher

Publisher Squad

Eng Lead: Jason Myatt (Deactivated)





Programs Theme

Automation Rules

/wiki/spaces/PROD/pages/933200139

...

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.

...

Ownership Repos

...

edX Internal Slack: #ecommerce-guild or #revenue-engineering

...

Architecture Theme

Active Product Development Areas

...

Ownership Repos

Info

Note: if your questions will include specific user information, do not use the Open edX Slack

Platform AreaRepoDescriptionTriage StepsWhere to start with questions (for learning & clarification)Multipleedx-platform

edX Internal Slack: #dev or @arch-team within any channel
Open edX Slack: #architecture

Platform & Infrastructureauthn/authzOpen edX Slack: #architecture
edX Internal Slack: @arch-team within any channelPlatform & Infrastructuredjango-openid-authOpen edX Slack: #architecture
edX Internal Slack: @arch-team within any channelPlatform & InfrastructureBlockStoreOpen edX Slack: #architecture
edX Internal Slack: @arch-team within any channelPlatform & InfrastructureUnified HeaderOpen edX Slack: #architecture
edX Internal Slack: @arch-team within any channel
Platform AreaProduct ComponentDescriptionAutomationTriage StepsWhere to start with any additional questions (for learning & clarification)Planned Sustaining DateContent & 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:
  • Tag David St. Germain (Deactivated) (Dahlia Team Tech Lead) and message in #masters-proctoring on the Internal Slack with the ticket link to determine if issue is related to any ongoing work or changes. This will keep the dev team updated to any fixes that we see coming in, and help give insight whether it is related to active development. If it is related to active development, the Dahlia team will take on the issue.

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:

  • If there is anything related to the new Gradebook, tag Deen Abdul-Hathi (Deactivated) (Product Manager) for context and he can work with the engineering team in Cambridge to triage and prioritize.

For incoming Grades issues:

  •  Tag Simon Chen (Neem Engineering Manager) to provide context of work that our team is working on to resolve. This provide insight to the team of what changes our teams are making and they may be able to provide knowledge sharing.

Master's Neem Team

edX Internal Slack: #masterdevs

Ownership Repos

...

xblock-lti-consumer

aka LTI Tool Consumer

...

Revenue Theme

Active Product Development Areas

...

Squad Details
Content & Authoring

Content and Authoring:
Content:ProctorTrack (Verificient)

CR

  • Assignee: Empty
  • Status: Needs Triage

Eng Ticket

  • Project: Educator (EDUCATOR)
  • Status: Backlog
  • Labels: masters; masters-support

Master's & MicroMasters Squad

Eng Lead: Mat Carter (Deactivated)

Product Lead: Deen Abdul-Hathi (Deactivated)

Learner ExperienceMaster Track

CR

  • Assignee: Empty
  • Status: Needs Triage

Eng Ticket

  • Project: Educator (EDUCATOR)
  • Status: Backlog
  • Labels: masters; masters-support

Master's & MicroMasters Squad

Eng Lead: Simon Chen

Product Lead: Deen Abdul-Hathi (Deactivated)





Platform Theme

Automation Rules

Platform AreaProduct ComponentAutomationSquad Details




edX for Business Theme

Automation Rules

Platform AreaProduct ComponentAutomationSquad Details
Business & Enterprise*any

CR

  • Assignee: Empty
  • Status: Needs Triage

Eng Ticket

  • Project: Enterprise (ENT)
  • Status: Backlog
* S&E team looks at these tickets in the queue to check if they are Ent specific or more broad in scope