More documentation around deprecation
How do we create a DEPR pipeline?
Review the Toggle Removal report
toggles are a good first step
anything we should add to the report that we’re not capturing today?
How do we engage other squads to help out?
How do we make it visible to squads what their DEPR status?
What are the organization code smells that might indicate DEPR needs?
How do we prioritize what to work on?
Metrics for analyzing the impact of DEPR work
Agenda (1/5/21)
Agenda (1/19/21) -
Agenda (2/2/21)
Agenda (2/16/21)
Agenda (3/2/21)
Agenda (3/16/21)
Agenda (3/30/21) -
Agenda (5/14/21) -
Agenda (6/8/21) -
Agenda (6/22/21) -
Agenda (7/6/21) -
Agenda (7/20/3221) -
Agenda (8/3/21) -
Agenda (8/17/21)
Agenda (8/31/21)
Agenda (9/28/21) -
Agenda (10/26/21) -
|
Agenda (11/9/21) -
Discovery around removing ES from our services
Insights/Analytics already did this analysis:Do We Need Elasticsearch in Analytics Data API and Insights?
Ecommerce update, maybe?
DEPR in the time of non-profits
Making DEPR meetings public
Learning how to be public first vs. private first is going to be different
We (2U) probably won’t own this in the future, but would still have to be driven by the folks as part of this working group and at 2U.
Would like to see more involvement from the community in DEPR process, proposing, etc.
Hopes and dreams: Can we get more visibility into DEPR and attention from the internal folks? Should we communicate these internally as well as externally?
Agenda (next) -
https://github.com/jazkarta/edx-jsme - Nobody really maintains this anymore and we’d like to deprecate it, Peter Pinch has offered to help
lms/djangoapps/dashboard has only contained 2 ADRs for about a year after its removal, can those be removed now?