Versions Compared

Old Version 20

changes.mady.by.user Farhanah Sheets

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.

Engagement Theme

...

Automation Rules

...

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

...

Programs Theme

...

Platform AreaProduct Component(s)
Description
Automation
Triage StepsWhere to start with any additional questions (for learning & clarification)StatusPlanned Sustaining Date
Squad 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 Engagement team who has the most context.
If a ticket comes in relating to any new Course About Pages:

Website Squad

edX Internal Slack: #engagement

Catalog & Publishing

Course Publishing Workflow

Publisher

Engagement 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:
  • Triage & create the Prod ticket, tag Jason Myatt (Deactivated) (Eng 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.

Publisher Squad

edX Internal Slack: #publisher-squad

Catalog & Publishing

Other Marketing Pages (Institution / Subject / Profile)

Topic Pages

Engagement 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:

Website Squad

edX Internal Slack: #engagement

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:

  • 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.
edX Internal Slack: #revenue-engineeringLaunchedMultipleSite-wide experimentsThe 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.
Active page of current flags: Revenue waffle flags and switches

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.
edX Internal Slack: #revenue-engineeringOngoingCommerce & PaymentFirst-time payer discount

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.
edX Internal Slack: #revenue-engineeringOngoing

...

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

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

Masters team will do extensive grades infrastructure, API and UI work in FY2020. Masters team have the knowledge and context around issues that arise.

Gradebook is a new micro-frontend that will be used for Master's partners when viewing and editing learner grades. 

For incoming Grades issues:

  •  Tag Simon Chen (Neem Engineering Manager) and Alexander Dusenbery 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.

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.
Platform AreaProduct ComponentDescriptionAutomationTriage StepsWhere to start with any additional questions (for learning & clarification)StatusPlanned 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

DeliveredContent & 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 #masterdevsIn ProgressLearner ExperienceMaster TrackWe 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

...

xblock-lti-consumer

aka LTI Tool Consumer

...

Platform 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

...

Video Service (VEDA, Val)

edx-val

edx-video-pipeline

chunkey

...

edX Internal Slack: #escalations or #sustaining-vulcans

...

Forums

cs_comments_service

...

Forums

...

https://github.com/edx/cs_comments_service

...

Farhanah Sheets

...

Xqueue

...

https://github.com/edx/xqueue

...

Farhanah Sheets

...

edx-val/edx-veda

...

https://github.com/edx/edx-val

...

Farhanah Sheets

...

edx-video-pipeline

...

https://github.com/edx/edx-video-pipeline

...

Farhanah Sheets

...

edx-milestones

...

https://github.com/edx/edx-milestones

...

Farhanah Sheets

...

edx-search

...

https://github.com/edx/edx-search

...

Farhanah Sheets

edX for Business Theme

...

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