/
DEPR Meeting Notes (2024)

DEPR Meeting Notes (2024)

DEPR Project board

 

09 January 2025

  • New year, new us - Migrating everything to point to new page

  • [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

12 December 2024

14 November 2024

17 October 2024

  • devstack settings file deprecation has a few more weeks, due to AXIM priorities.

3 October 2024

  • Discuss how to close https://github.com/openedx/public-engineering/issues/189#issuecomment-2310391093 (see linked comments).

    • https://github.com/openedx/edx-rest-api-client/pull/303

    • This has been deployed to most of the repos without complaint

    • The remaining issue is only related to communicating with ecommerce, which is about to be deprecated anyway.

      • This will be removed with ecommerce cleanup out of edx-platform

    • DEPR ticket has now been closed

  • ecommerce deprecation is happening imminently

    • This will be happening before the Sumac cut.

    • Within the next couple of weeks or so.

    • 2U will need to be prepared for it on their end.

    • Both the ecommerce repo and all associated MFEs.

  • learner dashboard may have a feature (or features) that are not handled in the MFE.

  • concerns about parity in new replacements

    • how can we ensure that the replacement isn’t going to drop features without notifying the rest of the community that they will be missing?

    • this seems to be mainly concerns with MFE development right now, but it will also continue to be relevant to things like libraries

    • course authoring MFE will probably be coming down the pipe

    • This will be brought up during the release planning meeting for Sumac.

  • Review the page https://openedx.atlassian.net/wiki/spaces/COMM/pages/4262363137 and ensure that all the information is as up to date as possible.

    @Robert Raposa clean list of accessed legacy frontend views from edx.org / Datadog and use it to supplement the above page.
    https://docs.google.com/spreadsheets/d/1X81NJB20hcBHcfsswenP5FhECe1w1LzXWrBlga4RmX4/edit?gid=0#gid=0 - spreadsheet was created
    @Kyle McCormick file a bug for view live on custom-pages studio view

  • [inform] Attempt to complete https://github.com/openedx/edx-drf-extensions/issues/371 did not go as planned.

    • There is an updated plan, that may sit for a very long time.

    • DEPR of a CORS Allowed header ain’t easy.

  • Devstack deprecation coming up

    • What are the planned timelines?

      • devstack.py will probably be going away in the next couple of months

    • 2U is working on pulling out the devstack images from the repos. currently our new process is being tested.

  • DEPR coming up (unclear about timeline):

    • removal of the FEATURES dictionary from the settings

    • turn these flags into standard django settings

    • this is almost definitely going to happen, but we aren’t sure when or the specific details of how.

22 August 2024

  • new DEPR tickets

    • a wave of new tickets have been filed

    • coming out of discussions about maintenance and what we (the community) would like to continue to maintain

    • ecommerce repos are really, really going to deprecated this time?

  • depr tickets getting announced to the depr channel

    • is this too noisy?

    • decided this isn’t for now. will re-evaluate as more depr work comes in

  • keep track of action items at the top of the page

    • want to make sure we ensure these things get done

  • how do we handle legacy frontends in edx-platform?

    • ticket for conversion of: https://github.com/openedx/edx-platform/issues/31620

    • try to enforce bugfix only in edx-platform for legacy frontends

      • can require codeowners approval for any changes to legacy frontend code

      • allow for an appeals process for exceptions

    • do we have a good catalog of the legacy frontends/views left?

    • can we allow people to copy/paste old code from edx-platform?

      • ‘crappy’ MFEs

      • need to be able to make decent, reusable APIs in edx-platform, though

        • prevent APIs from becoming tightly wedded to the frontend as much as possible

      • are their performance implications?

    • do we have the capacity to handle these sorts of requests to update/change the legacy frontends?

    • current focus is to remove old frontends with replacements

      • this is easier than doing the full conversion

    • other replatforming work?

      • we got updates to learner dashboard and studio frontend.

      • big thing is instructor dashboard

        • APIs underlying it is being rewritten to be DRF APIs

        • can we be able to do the conversion tab by tab?

          • create a shell for new tabs to be added to?

        • we already have the gradebook mfe. can we turn this into the instructor dashboard mfe?

8 August 2024

  • Legacy Text Editors - What would it take to move off of them?

    • DEPR Ticket

    • Two Categories of Issues

      • Perf Issues, the new editor takes a long time to load large amounts of text.

      • UX Issues

        • How do we have the UX conversation about the editor?

          • 2U had a practice to add a “Feedback” button into interfaces to easily give feedback changes on UX changes.

            • The feedback buttons went out with openedx but where does that feedback go?

            • In Redwood.2 it will be removed instead of going to 2U

          • It’s unclear what the plan was with the studio MFE and the editor, what are our options for solutions?

          • This should go in as a new enhancement request to the Product WG so that we can plan and discuss this as a community.

        • FYI, Course Authoring MFE will have a full replacement for studio

          • The course outline is replaced in Redwood

          • In Sumac the Unit editor will also be replaced with an MFE Page

            • This new page will not work with the legacy editor so it implicitly drops the old editor support in the new UI.

            • In Sumac you can still drop back to the old UI/editor but in Teak, this might not work.

        • What’s the plan for the problem editor? The new MFE has a lot more issues than the old problem editor MFE.

          • Similar, to the text editor, the MFE is on by default in Redwood but the old one will still be available.

  • Review of https://openedx.atlassian.net/wiki/spaces/COMM/pages/4262363137 to fill in DEPR ticket section.

    • Note: @Feanil Patel @Robert Raposa are also discussing this in Maintenance WG.

 

@Peter Pinch to put up some product tickets around improvements to the new Text Editor and new Problem Editor, Peter will get people closer to the problem to open the ticket.
@Kyle McCormick to check in with Jenna about re-prioritizing content-libraries work if having only the new editor might prevent people like MIT from using content-libraries all together.
@Kyle McCormick will make VideoBlock and ProblemBlock editor DEPRs so there is a place to collect feedback on those
Update this page with known views and add suggestions of which MFEs they should be added to: https://openedx.atlassian.net/wiki/spaces/COMM/pages/4262363137

25 July 2024

  • Open edX conference happened!

    • is there anything that came up that is particularly relevant to this group?

      • More conversations around https://github.com/openedx/open-edx-proposals/issues/595 occurred

        • There is a lot of desire to communicate more breaking changes via DEPR.

        • Many saw DEPR as one of the more mature and clear process in the open edx community.

      • Pinata was destroyed

        image-20240715-160032.png

         

        • Celebrating

          • paver cleanup and soon to be removal

          • platform assets cleanup

          • badges implementation

          • bok-choy

          • many other things

  • Automating cross-posting to Discourse/Slack

    • if a ticket moves into ‘Announced’ can we have that auto-announced to Discourse and Slack?

    • this requires development to get done

  • Maint WG proposal for DEPR process changes

11 June 2024

  • Profile and Account MFEs deployed to edge

  • Maintenance working group proposed using the DEPR process to communicate/manage all breaking changes in Open edX.

    • Seems like a good way of leveraging the existing knowledge and infrastructure to reduce duplication.

    • What do we need to do in order to make this change?

    • Could we make it more automated to reduce friction?

      • if a ticket moves into ‘Announced’ can we have that auto-announced to Discourse and Slack?

      • this could be similar to the discourse to slack automation to some degree

27 June 2024

  • replacement/extensibility of ID verification system: https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4307386369

  • Node 18 deprecation

  • problem-builder deprecation: https://github.com/openedx/public-engineering/issues/268

    • this seems to be just for an already existing XBlock in the open-craft repository

    • good to see other parts of the Open edX ecosystem using the DEPR process to announce changes!

  • maintenance working group: expand and and contract for changes

    • use the DEPR process to announce breaking changes, not just deprecations

    • this would necessitate a change to the deprecation OEP to match this update to the process

    • overall, it seems good to leverage the existing process that people know about for this

    • adding metadata to track dates so we can filter/graph/etc them instead of relying on reading and parsing the ticket only

13 June 2024

  • testeng-ci deprecation

    • cleaning up the last few things still using it instead of repo-tools

    • mostly being used for Python upgrade

  • Studio frontend MFE DEPR ticket incoming

    • will trying to farm out work to CCs to help clean up the old views in edx-platform

  • Removed old calendar invite in favor of a new one set up by AXIM

30 May 2024

2 May 2024

18 April 2024

4 April 2024

  • Update the OEP to match the new process listed below

    • Hopefully the new process has been updated to accommodate everyone’s feedback

      @Deborah Kaplan to draft a proposal (create a PR) to update the OEP to match the proposed changes below

  • Go through the board, move tickets to the appropriate status according to the process

    • Moved tickets around and assigned new owners to some of them.

  • Send out announcements about the changes to the DEPR process.

    • This will happen once the PR to update the OEP has been created

  • [Diana] 2U is in the process of planning out how to handle the removal of the devstack infrastructure from openedx

21 March 2024

  • [Diana] [inform] Devstack has been deprecated/archived. 2u has created a fork.

  • [Feanil] https://github.com/openedx/public-engineering/issues/51 - Does Kyle’s latest suggestion here make sense? Should we proceed with this?

  • Discussion: how do we handle breaking changes in, for example, edx-platform in the future?

    • tutor maintainers will handle updating Tutor, but all the other operators will need to be informed and make the appropriate changes

    • ex: moving static asset compilation out of paver

    • 2U interested in maintaining a list of incoming work from DEPR/other community work that needs to be addressed by 2U

      • Can we make this information available to the public as well?

      • We are currently maintaining it within 2U boards, but maybe we can do this going forward

      • We aren’t doing a good job of marking tickets with the last open edx release