...
Admin note: can someone run the 30 November meeting?
Robert says he can show up for itIt seems like this
courseware_studentmodule work
Do we have a process for removing code that we don’t think is actually accessed from the frontend?
Just go through the DEPR process as normal
For 2U-checking, we have ways to do some observability work to check for whether or not codepaths are used.
https://github.com/openedx/edx-toggles/issues/283
Covered if we want to require the toggle_depr_ticket field.
Likely incoming DEPRs for obscure video features.
New version of the video player
Will need to communicate out within 2U and 2U partners
Can we check for New Relic information about usage?
What version of OpenSearch are we targeting?
We don’t have any in particular, but latest stable seems the best option (2.11)
What client to use?
No determination on this yet.
(Add these questions to the DEPR ticket).
Bok Choy update:
We're getting closer and closer to removing bok choy from openedx
Python 3.11
Targeting Redwood
Hoping to start this in January
02 November 2023
Introducing Brian!
https://openedx.atlassian.net/wiki/spaces/COMM/pages/3768188929/Contributor+Coordination+Working+Group?focusedCommentId=3894607915 - providing DEPR updates to the rest of the community
Maybe we can just see if the meeting notes are sufficient for their purposes and if they are not, revisit this topic
[Robert] [inform] Progress being made on https://github.com/openedx/edx-drf-extensions/issues/371.
Testing (again) on ecommerce. If that works, will enable by default.
Making sure folks have enough work to do (if they want)
Looked through the temporary toggles spreadsheet, have a few possible candidates, though we will want to do some vetting to ensure that they’re ready to be worked on instead of breaking it.
[Jeremy] [inform] FED-BOM making another attempt to remove legacy account, profile, and ecommerce UI pages
Splitting them up into 3 separate PRs this time to increase odds of each one getting through
[Jeremy] FED-BOM is looking to use Webpack build output to identify unused direct dependencies. Should we try something similar with Python test suite coverage data?
Unsure how much this lines up with depsplorer exploration that we already looked at: https://github.com/openedx/edx-platform/issues/32604
We don’t know if there’s an existing coverage plugin that would already give us this information.
Could write up some tickets for running some of these existing tools on some of our python repos.
go to repo-health-dashboard and sort by the repositories with the most dependencies, start with the one that has the most.
Alternatives to https://github.com/Nathan-Furnal/depslorer ?
...