Versions Compared

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)

...

Platform AreaProduct Component(s)DescriptionTriage StepsWhere to start with any additional questions (for learning & clarification)StatusPlanned 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:
  • 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



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



...

Active Product Development Areas

Master's product delivery overview (Q3/Q4/Q1)/wiki/spaces/PROD/pages/933200139

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

Delivered
Content & Authoring

Course Grading Policy & Tools

aka Grades

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.


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 Progress
Learner 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







...

Platform AreaRepoDescriptionTriage StepsWhere to start with questions (for learning & clarification)
Learner Experiencecredentials

edX Internal Slack: #masterdevs
Learner Experienceedx-certificates

edX Internal Slack: #masterdevs
Content & Authoring

xblock-lti-consumer

aka LTI Tool Consumer



edX Internal Slack: #masterdevs
Content & Authoringproctoring

edX Internal Slack: #masters-proctoring
Content & Authoringgradebook

edX Internal Slack: #masterdevs

...

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/authz

Open edX Slack: #architecture
edX Internal Slack: @arch-team within any channel
Platform & Infrastructuredjango-openid-auth

Open edX Slack: #architecture
edX Internal Slack: @arch-team within any channel
Platform & InfrastructureBlockStore

Open edX Slack: #architecture
edX Internal Slack: @arch-team within any channel
Platform & InfrastructureUnified Header

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

...