DEPR Meetings Notes (2025)
Future
[Robert] [proposal] I plan to add a comment like the following to all DEPRs in the Accepted state: https://github.com/openedx/brand-openedx/issues/23#issuecomment-2919418180. If you have comments on the wording, let me know and I can adjust before commenting. I learned in the Maint WG meeting that this particular DEPR ticket has plans for moving forward, so I got a jump start before it was too late. (Copied from Slack message.)
29 May 2025
[Robert] [inform] Abandoned/Rejected won’t auto-close, so it doesn’t move to Plan Completed (as a closed ticket). These will need to be updated manually.
[Robert] [question] When closing, we have “Last Release with Feature” to fill in on ticket. Is there anything else?
Answer: That’s it.
[Robert] [proposal] I plan to add a comment like the following to all DEPRs in the Accepted state: https://github.com/openedx/brand-openedx/issues/23#issuecomment-2919418180. If you have comments on the wording, let me know and I can adjust before commenting. I learned in the Maint WG meeting that this particular DEPR ticket has plans for moving forward, so I got a jump start before it was too late. (Copied from Slack message.)
15 May 2025
Retros were completed in Maintenance WG meeting on 15-May.
Retro for the Studio waffle flip
Retro for pre-Teak late-stage breaking changes to MFEs (
FooterSlot)[inform] Decision: Let’s use our updated process and board to inform.
[Robert] DEPR board review and process improvements.
[inform] I renamed the board columns to match the OEP.
[proposal] We implement this process: 2025-05 DEPR Board Review and Process Improvements
01 May 2025
Retro the Studio waffle-flip.
Of interest to @Kyle McCormick @Jeremy Ristau @Robert Raposa
Question: Is it helpful/useful to flip waffle flags from opt-in to opt-out before making a feature mandatory? Is it worth the time? Are there ways to implement this that makes it easier on everyone?
This might be tentatively scheduled for the next meeting on the 15th.
codejail-service readiness
I think this might want to wait another release
Draft DEPR: https://github.com/openedx/edx-platform/issues/36639
Process improvements for temporary edx-platform toggle clean-up and increased ownership for removing newly introduced toggles.
https://docs.openedx.org/projects/edx-platform/en/latest/references/featuretoggles.html (search for “temporary”)
Tickets with ideas for improvements: https://github.com/orgs/openedx/projects/9/views/7?filterQuery=deprecation-ticket-type%3A"Supporting+Deprecation+Work"+toggle
https://docs.openedx.org/projects/openedx-proposals/en/latest/best-practices/oep-0017-bp-feature-toggles.html - OEP for handling toggles.
Maybe some of the new folks can pick these up.
Hackathon ideas:
Create and implement DEPR for individual temporary toggles.
Does the DEPR OEP need notes for handling different use cases?
A toggle tied to a larger DEPR doesn’t need any special considerations.
A temporary rollout toggle either might not need a DEPR, or potentially automatically be accepted?
Are there other temporary toggle use cases that needs special docs?
Implement some of the process improvement ideas already ticketed and/or ADRed.
2 PRs from WGU to review:
cors_csrf middleware and utilities: feat!: [DEPR] cors_csrf middleware and utilities by dwong2708 · Pull Request #36598 · openedx/edx-platform
Will work with AXIM/Open edX security WG to get this in
karma-selenium-webdriver-launcher: fix: remove dependency by tonybusa · Pull Request #36589 · openedx/edx-platform
Will separate the lint commit and rebase the merge commit
01 April 2025
Axim can’t make this one
Check in on readiness of the codejail-service for the Teak release
20 March 2025
Programs dashboard
legacy page
no DEPR or MFE replacement
Might make sense to make it part of the learner dashboard MFE
the API can be improved to prepare it for MFE migration
Can be pushed through after the Studio Legacy frontends deprecation work
Codejail service will be coming up as soon as the replacement in a good place.
Will want to try to merge the repos into one, maybe as part of the deprecation
We can ask the maintainers about trying to do this work once the ‘official’ implementation is in a good place
Discussed possibility of releasing this as part of Teak
We aren’t sure. Is about to be dark launched on edx.org.
We will check in during next DEPR
2U/Arch-BOM will write the DEPR as the team who is doing the bulk of the work to develop the new codejail-service, but they won’t own the ticket going forward.
6 March 2025
Kyle: Will probably have questions for 2U w.r.t. edx-proctoring-proctortrack deprecation.
Diana: Should make sure the owning team is aware (Cosmonauts)
Forums v2 work will start up again soon. SOW sent out this week. No breaking changes until after Teak cut.
Diana: Work starting on codejail service replacement, but no immediate plan to remove codejail itself.
Dave: Is there place to tune in to this work?
Diana: Mostly internal. You can follow the tickets and there’s a public repo.
20 February 2025
Old studio frontends DEPRs got announced
[DEPR]: All Legacy Studio Frontends · Issue #36275 · openedx/edx-platform
Bringing the new Studio MFE up to par to
bug in the new problem editor that has manifested on edx.org
This concerns pre-existing content and how configurations get reset when being edited in the new problem editor
Have a workaround but could cause data loss if unprepared
bug has been filed
OEP updates ongoing
Account and Profile pages finally removed from edxapp!
🪅🪅🪅🪅
This has been a long journey, but fewer frontends in edxapp
Updated MFE Rewrite Tracker
Forums v2
Blocking issues found during 2U testing.
Timeline has been changed or pushed out to ensure those changes can get addressed before migration.
6 February 2025
Forums
Recent activity on the DEPR for cs_comments_service.
New DEPR for non-MFE course tab interface for discussions.
(Dave): I intend to make another DEPR for inline discussion block.
Editors (Kyle)
still compiling information…
Four deprs… one for old unit page, 3 for old editors:
Major points of feedback
Floating modals rather than full-page modals. “Open in new tab” should also work.
Markdown support, will fix:
Cross-instance copying
Multipart editing
Needs product blessing
Needs resourcing (MIT is likely able to contribute)
2U might have designs?
Performance - should be resolved by switching to new unit
New video editor is generally an improvement (other than general editor feedback, namely, opening in a modal)
Goal: Have all of this enabled by default in Teak, toggle-off available until Ulmo
23 January 2025
forums
2U testing has revealed issues with the new forums code
bugs have been filed against the forums repo: https://github.com/openedx/forum/issues
can we deprecate CourseGraph?
check in with 2U to make sure there’s no more need for/usages of it
https://github.com/openedx/open-edx-proposals/pull/660 - continue making updates and changes to the pilot
09 January 2025
New year, new us - Migrating everything to point to new page
@Kyle McCormick - finish up tasks from https://openedx.atlassian.net/wiki/spaces/COMM/pages/3996745737[Diana] Forums deprecation - when is removal of support for v1 forums planned to land in master? Sometime before Teak, but obviously, 2U needs more solid dates.
This seems to have the date of March 1 now
We’ll start deleting the parts of code that talk to the ruby forums service.
Bugs with the software should be filed with the new repo
Internal to 2U, Arbi-BOM will be doing most of the engineering, supported by the Infinity team with their domain expertise.
[Kyle] Paver deprecation is very close to being completed!
Hooray.
[Feanil] Updates to the DEPR OEP - https://github.com/openedx/open-edx-proposals/pull/660