...
AKA 'slash n burn' AKA 'kill it with fire'
Slack
#depr#wg-depr-slash-n-burn on edx-internal#depr in the Open edX workspace
#openedx-wg-depr-slash-n-burn on openedx in the internal 2U workspace
Members
Process
Open edX Proposal (OEP)
...
Keep an eye on whether or not this process is working
If not, suggest improvements/revisions
...
Board
We track items for deprecation and removal on the DEPR Jira Board.Here's a view of DEPR tickets report DEPR Board on Github.
Scratch Confluence Page
Deprecation/Removal Evaluation is an internal page where the Architecture team started this process and that we can use for exploring possible items to remove.
Meetings
We meet once every two weeks. You can view the meeting on the Open edX Working Group calendar.
Meeting Notes
...
How do we get this work onto our team backlogs?
What work should be added to this list?
Are there ways to make deprecation more 'frictionless'? What pain points do people run into during deprecation work?
How can we hold the engineering org accountable for technical debt deliberately introduced?
Resources
Maintenance Cost Estimates - How much it costs to keep around code we don’t use anymore.
DEPR Release Notes Process - Process for ensuring deprecations have proper release notes. If we are contacted by BTR about a release being cut, follow this process.
edX Internal Use Only