19 October 202305 October 202321 September 202307 September 2023We have a profile MFE. Should there be a DEPR ticket for removing the legacy page from edx-platform? Askbot references still lingering: https://github.com/search?q=%28org%3Aopenedx%29+askbot&type=code We have a lot of staff grading XBlocks. Should we try consolidating them? The comment period for xQueue xQueue-watcher has passed with some requests for delaying the deprecation. What comes next? Last Old Mongo removal PR of FC-0004 has merged! (barring regressions) This just went to production Old static assets sticking around for a while to not block credentials … so I guess this is still sorta in-progress?
Upcoming Axim-funded projects that will likely kick off new DEPRs eventually, but not yet:
24 August 2023Follow up on xqueue Discussion of toggles-related DEPR work Discuss https://github.com/openedx/xblock-adventure/issues/56 Tutor is moving to MySQL 8.1 MySQL 8.1 is not an LTS release. Bumping versions on Tutor as soon as possible Concerns with falling out of sync between devstack/edx.org and Tutor and ensuring compatibility.
https://github.com/openedx/edx-platform/issues/32343 Discussion of how to handle non-depr-ticket tickets on the DEPR board Still need to track as they are deprecation work, just not specifically needing to be announced. Use a label/field to mark as ‘depr-supporting' work.
10 August 2023[Diana] xqueue + xqueue-watcher ticket https://github.com/openedx/public-engineering/issues/214 We need someone at 2U to do a coursegraph search to find the existing usages of xqueue on http://edx.org . Aiming for Quince, but MIT will need to do work to migrate existing problems onto the alternatives. We will need to talk with partners who are also using xqueue to find out what technologies they are using. Are they using xqueue-watcher? Can we do NewRelic searches to find usages?
Assigning tickets via comments? can we find docs around that? Follow up on deadcode discussion: Follow up on moving stuff from openedx org to the edx org
27 July 2023[Diana] Follow up on deprecating devstack/edx-configuration Set the dates further out, about 6 months Seems like there is still some use here that we need to be aware of and careful about Next steps? Draft up a proposal about what this transfer of ownership would look like? Figure out how to pull more people into the discussion? We do need to figure out what the lawyers have to say about the transfer as well. Initial proposal is to just move from one org to another, keeping the repositories public and available for PRs.
[Diana] Take a look at deadcode and vulture results on edx-platform: [Diana] We’ve been able to clean up some more small DEPR tickets thanks to Yagnesh! [Robert] [inform] I’ve been implementing 2U-side of https://github.com/openedx/public-engineering/issues/190, and ran into a minor issue where I may take on edx-configuration. [Peter] XQueue, XQueue Watcher Can we get a ticket created? We can get a draft written up for the ticket. LTI is the best alternative for this and should be the replacement for this code.
13 July 2023[Robert] [inform/question] I noticed that I had referred to devstack as deprecated, and have discussed edx-configuration as deprecated, but neither of those things are true because there are only draft/proposed DEPRs. Can we do better at moving DEPRs past Proposed so they are either Accepted or Rejected? Can we do better at not referring to things as deprecated when still in “Proposed”? Can we say that Proposed is just a proposal and that we don’t consider something deprecated until it reaches ‘Accepted’? This is especially useful for making sure people feel comfortable giving feedback in the ‘Announced’ stage, because it means their feedback can sway things away from being deprecated.
Does the term “Proposed” sound too official, and would “Draft” change anything here? To me, “Proposed” sounds more official than what the actual status is, especially because the ticket could be no more than a placeholder title at that point. [inform] I may miss this meeting. Feel free to discuss this topic without me, and maybe see which parts have lots of agreement and which do not. 2U is the only part of the community that uses these even. Should we move them into 2U’s org and then just let the community move on?
[Diana] Review results of deadcode: https://github.com/openedx/edx-platform/issues/32603 initial impression: this seems a little too noisy to be useful Could we find django-specific filters/plugins for this library to help filter out some of the noise? We need to do a better job of filtering out tests, because that adds to the noise. Maybe also exclude settings since we’re hopefully tackling that with toggles work. [Diana] [Action item] I’m going to leave a comment on the ticket with the feedback.
[Diana] Still need to schedule meeting around frontends How do we want to ‘deprecate’ things in Open edX that only 2U uses? Maybe we just announce that these things get moved to the edx organization. What are the gaps that still remain for non-2U developers and Tutor? Can we just move configuration? Is this the best way to go about doing it? [Action Item][Diana] Announce configuration deprecation.
29 June 202315 June 20231 June 2023Should we go through and deprecate old OEPs? Do we have a process for that? https://open-edx-proposals.readthedocs.io/en/latest/index.html Example: OEP about bootstrap - still being used by Paragon but planned not to be used anymore We can move them into ‘withdrawn’ or ‘obsolete’ Just have the same process as writing a new OEP - have an author, find an arbiter. Update OEPs to point to related OEPs Assigning WGs or teams to take a look:
Adolfo Brandes: https://github.com/openedx/edx-platform/issues/31436 https://github.com/openedx/frontend-component-cookie-policy-banner - 2U is no longer using this, so I made a DEPR ticket. There seems to be a bunch of remaining 2U-specific strings lingering here: https://github.com/openedx/frontend-component-cookie-policy-banner/issues/423 Is there any way we could hand off ownership to someone else, who can then pull out all the 2U-specific strings to their hearts' content? We will ask RG if they want to take ownership or if they’re okay with this repo being archived and they can continue to maintain their own fork.
What can new members pick up? Dave Ormsbee (Axim) : Request for assistance on Matlab student state. Anyone have (anonymous) problem state and a problem definition I can use? Mechanical Engineering is the best bet Should have a CourseGraph query for this.
Dave Ormsbee (Axim) : XQueue? Ask Aurora about writing that DEPR ticket for xqueue and a separate ticket of xqueue-watcher. Holding up some XBlock runtime simplification Try to deprecate xqueue-watcher first.
Redis - are we planning on supporting this for a while? new project is considering using Redis-specific functionality this seems fine, since Redis is the recommended backend for celery, and the community backend for caching and the message bus
[inform] I just created a DEPR for legacy marketing site cookies that no one in the community probably cares about: https://github.com/openedx/edx-platform/issues/32343 Still need to schedule a meeting to talk about deprecating frontends with both DEPR and frontend WG.
18 May 2023xqueue & xqueue-watcher - time to start deprecating? MIT says they no longer use it Owned by Aurora, Mat says the number of users is small (but he doesn’t have a list handy) May need some sort of fix for legacy certificates Let’s make a new DEPR ticket for xqueue and xqueue-watcher.
Cleaned out a bunch of unused Jenkins code 🎉 Checklist for Deprecations: what should be on it? Made a DEPR for Matlab code in edx-platform Just waiting for the acceptance date to arrive Removes another usage of xqueue! Check in with 2U about the usage internally (this is pretty broken, so we shouldn’t be).
Timeline for removing support/handling for MySQL 5.7? Tackling frontend deprecation Still need to ask FED WG to write up an OEP about their future vision of frontend. MFE domains, Paragon Product vision - don’t want to do a straight port of instructor dashboard Making sure that our OEPs are updated to clarify how the frontend code What should we do in situations when folks are stuck working in legacy frontend code?
How do we want to start some of these projects? Set an agenda for it around scoping a couple different projects: support page (how to get help) - small, and instructor dashboard - large. Diana to work with Adolfo on scheduling this.
04 May 202320 April 2023Conference happened! Legacy frontends: what’s next? Lots of energy around this. Follow up with the FED WG about next steps. Keep checking in with Frontend WG about what is going on. Not mechanical enough. Auth cleanup is a blocker here. Need to make it easier to authenticate so we can make it easier to access REST APIs.
OpenCraft’s BD-13 Modulestore cleanup work is culminating with: Major Old Mongo removal PR (this is the lobotomy PR) https://github.com/openedx/edx-platform/pull/31134 (approved, scheduled to merge) Returns an empty list when courses are asked for children. Mainly being kept around to support CourseOverview(s) and how those are regenerated periodically and otherwise anything else that tries to use the Course object instead of CourseOverview.
[Robert] Attempted to disable symmetric JWTs for my hackathon, but backed it out. I have ticketed new follow-up work. See https://github.com/openedx/public-engineering/issues/83. Palm branches cut, go through board to figure out release notes [Dave] Going to make an SOW for work to move course data off of MongoDB and into (still under construction) Learning Core data models. Discussion of maintainer work to remove temporary waffle flag things [Feanil] Sphinx theme deprecation moving along
23 March 2023Open edX Conference (3rd time around) Account settings pages PR update State of the WG update Software Engineering at Google Deprecation Chapter Advisory vs. Compulsory Deprecation Can we sequence deprecations to ensure a decent deprecation WIP? Can we turn on certain warnings for everyone everywhere vs. turning on all the warnings for everyone everywhere? Python Deprecation Best Practices
Tooling? - alerting people when they’re writing code that they’re using deprecated components/libraries Process Owners (ha ha ha) Intermediate Milestones
Shrinking the size of edx-platform requirements removing 2U-specific requirements this needs to be handled properly on http://edx.org with something like pip-compile can we rid of other dependencies? scipy is a big one, mostly used by codejail which modules get exported repo-health-dashboard work to keep track of dependency trees
Django 4.2 RC is out, so we should be preparing to have deprecation warnings and upgrade things. Removing boto from edx-platform - making progress! video uploading bulk email
Tension between putting things on the board that we are planning on working vs. putting things on the board that we want to work on and not lose track of. How can we move things along the board?
09 March 2023Old Mongo Modulestore cleanup State of the WG update
23 February 2023Open edX Conference (again) Kyle’s continued work with pavelib About half of it was already replaced/replicated with Makefile/shell scripts Some cleanup already happening (yay!) Toughest part of this is JS tests and Assets
Also work to get Python typechecking working MFE tickets for progress page and learner dashboard How do we get momentum on the stuff that is already on the board? Can we specify different levels of ownership? Would like to get this done before a bunch of upgrades. We can do more FCs/Blended, but there is a concern about getting code merged. Updates to the DEPR board: can do a workflow that can track how long a DEPR ticket has remained in the same state? custom fields to track levels of ownership to clarify what needs to happen on each thing Put things onto the Maintenance Board
09 February 2023Cross-posting should now be enabled from Discourse to Slack Open edX Conference Ticketing up replacement of legacy front end code with MFEs Update from Kyle: Mostly gotten rid of paver asset functionality in favor of bash scripts.
26 January 2023FYI: We got rid of about 1,200 lines of paver code in edx-platform: https://github.com/openedx/edx-platform/pull/31180 We are aiming to get rid of all of our custom paver tooling! Trying to remove all the testing stuff first as we target the frontend specific code as well. Trying to rewrite the asset management code into sh, ADR incoming
Getting close to removing https://github.com/openedx/edx-platform/pull/30336 Will be removing/archiving/moving to unsupported edx-e2e-tests today Looking for a review: https://github.com/openedx/edx-platform/pull/31633 toggles - can we put into the process that toggles should only last for a specific amount of time? part of the work of maintainers going forward? figure out a process for handling this
edx-sphinx-theme DEPR Update Moving things from Accepted to Removed Adding a ticket to the Maintenance GitHub Project If it impacts multiple repos, put it on the Maintenance Board and assign a coordinator to help put it on the owning teams. How does this work compared to upgrades?
Accepted vs. Deprecated Can we move more things into ‘deprecated,' even if we can’t get things into the removed column? Try it out with some of the auth DEPR tickets that we aren’t.
Can we make use of the Discourse/Discuss-Slack integration to automatically announce things to the correct Slack channel?
12 January 2023edx-e2e-tests Maintenance GitHub Project Repo health dashboard CFP for Open edX Conference Review board bok_choy: we still have some lingering tendrils in various places, but we don’t have any current work or resources yet. OpenSearch vs. ES work - who can lead this effort? can the Arbi-BOM team do so? Can the community take this on? Courseware pages - can we monitor usage of the old views on http://edx.org ? does a method (like a custom attribute) already exist?
Proposal for future DEPR: Reorganize edx-platform configuration variables Simplify the configuration overall and the various settings files. Suggested changes: what is the minimal thing we can get to run a version of edx-platform?
|