Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Date: March 1, 2023

DRAFT. THIS IS A DRAFT.

Introduction

The Deprecation Working Group focuses primarily on managing deprecation processes. Our primary goal is to get duplicate/unsupported/useless code removed from the platform.

Consider this report as a compilation of what we’ve done over the past year, what we’re looking at doing in the next 6 months, and a wider vision of the group’s future beyond that.

Accomplishments

Over the past year, our major accomplishments were:

  • EdxRestApiClient replacement happened, so we are no longer dependent on the Slumber library, which has not been supported for a few years now.

  • Removed old UI pages that have been replaced by MFEs from edx-platform. These UIs were not very well supported and were difficult to continue to maintain.

  • …

Further, we’ve made significant progress on the following initiatives:

  • Removal of Old (Draft) Mongo Modulestore. We have too many modulestores for course content on our system. We are closer to getting rid of one of them.

  • Ripping out pavelib from edx-platform. This is a fairly slow, fairly clunky system we used to run various important commands in edx-platform (like installing requirements, updating assets, running tests). Many of these have been replicated in Makefiles/shell scripts/something else, and we are going to try to rip out this dependency entirely.

  • …

We continue to engage in a set of ongoing tasks; these tasks are work we need to be sure we’re doing on a regular basis, but we don’t want to lose sight of their importance. Those tasks are:

  • We review the Deprecation Board and work to move things all the way to ‘fully removed’.

  • We review the deprecation processes and OEP to ensure that the process is as smooth and as easy as it possibly can be.

  • …

Concrete Plans - Next 6 Months

Over the next six months, the deprecation working group has some really exciting work queued up. We hope to drive {key metrics, description of impact, etc}. Our primary goals are to {work on / complete / another word} the following tasks and projects:

  • Task/project 1; 1-2 sentences of importance/impact

  • Task/project 2; 1-2 sentences of importance/impact

  • …

If applicable: Links to roadmaps/GitHub projects/important wiki pages/etc

Optional: We’ll provide a deeper dive into (name project(s) you’ll deep dive into) later in this report.

Deep Dive: Accomplishment/In-progress Initiative/Ongoing Task/Concrete Plan (Optional)

Use this section to write or link to deep dives into any of your accomplishments or initiatives that would benefit the community to know more about. You can assume readers at this point will have the background knowledge to understand this being written in industry jargon. You may have as few or many “Deep Dive” links as you’d like. If you don’t have a place to post deep-dive content at the moment, consider posting them as blog posts on the Open edX site.

Old Mongo Deprecation

  • All student and instructor access to Old Mongo courses has been removed.

  • Old Mongo will now be a read-only Modulestore that only supports returning the root CourseBlock (so we don’t break CourseOverviews).

  • Removing static asset support is blocked on certificates (which stores signatures there). We’re working on migrating this out.

  • No labels