Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade frontend framework in the monolith #15

Closed
e0d opened this issue Oct 26, 2021 · 4 comments
Closed

Upgrade frontend framework in the monolith #15

e0d opened this issue Oct 26, 2021 · 4 comments
Labels
epic Large unit of work, consisting of multiple tasks

Comments

@e0d
Copy link

e0d commented Oct 26, 2021

Project Narrative (Summary)
Working on frontend code in edx-platform is extremely difficult today, as supported by the results of our recent developer satisfaction survey. Unfortunately, there are still times when the right (or only) way to move forward and deliver value without significant overhead is to work in this codebase, rather than re-platforming an entire feature into a new micro-frontend. Frontend code in edx-platform isn't going away completely anytime soon, and we still need to work with it, but there's significant drag inherent in doing so.

We believe we can address the root of this difficulty, and see the most positive impact for our investment, by upgrading a few of the core libraries which we use in frontend development at edX to the versions used by our micro-frontends. Specifically, Paragon, and through its required dependencies, React.

There are wide ranging implications.

  • Paragon has seen significant investment, and upgrading will improve code reuse, a11y, brandability, consistency, and developer velocity. This isn't a typo - Paragon is 11 major versions behind in edx-platform (2.6.4 -> 13.16.4).

  • React has proven to be a much faster, much more effective way for us to write frontend code, and there are a variety of features and security fixes between edx-platform's version and latest (16.1.0 -> 16.14.0). It's nearly a different framework than it was in 2017 when 16.1.0 came out, and better for it.

@e0d e0d moved this to Ideation in Open edX Roadmap Oct 26, 2021
@e0d e0d moved this from Ideation to Prioritized in Open edX Roadmap Oct 30, 2021
@jmakowski1123 jmakowski1123 added the needs definition There are gaps in opportunity scope or definition to be addressed before the opportunity can proceed label Dec 20, 2021
@jmakowski1123 jmakowski1123 removed the needs definition There are gaps in opportunity scope or definition to be addressed before the opportunity can proceed label Dec 28, 2021
@jmakowski1123 jmakowski1123 moved this from Prioritized to Backlog in Axim Roadmap: Backlog and Epics Mar 7, 2022
@jmakowski1123 jmakowski1123 moved this from Prioritized to Backlog in Open edX Roadmap Mar 21, 2022
@jmakowski1123 jmakowski1123 moved this from Backlog to Ideation in Open edX Roadmap Jun 29, 2022
@arbrandes arbrandes moved this from No status to In progress in Frontend Working Group Aug 26, 2022
@arbrandes arbrandes changed the title Upgrade Frontend Frameworks Upgrade Frontend Frameworks in the monolith Aug 26, 2022
@arbrandes arbrandes changed the title Upgrade Frontend Frameworks in the monolith Upgrade frontend framework in the monolith Aug 26, 2022
@arbrandes arbrandes moved this from In progress to To be groomed in Frontend Working Group Aug 26, 2022
@arbrandes arbrandes moved this from To be groomed to Backlog (tentatively prioritized) in Frontend Working Group Aug 26, 2022
@jmakowski1123 jmakowski1123 moved this from Ideation to Backlog in Open edX Roadmap Sep 20, 2022
@arbrandes arbrandes added the epic Large unit of work, consisting of multiple tasks label Oct 6, 2022
@arbrandes arbrandes moved this to Backlog in Frontend Working Group Nov 21, 2022
@kdmccormick
Copy link
Member

This is related to, or perhaps entirely duplicated by, this edx-platform issue: openedx/edx-platform#31616

@arbrandes
Copy link

@kdmccormick, since this is the higher-level roadmap ticket, I suggest we simply point to the edx-platform one as a subtask in the description. @jmakowski1123, thoughts?

@kdmccormick
Copy link
Member

kdmccormick commented Jan 30, 2023

I think we only need one issue. No sense in trying to keep two identical issues in sync, right? I would close one as the duplicate of the other. As for which we keep open, it doesn't matter to me.

@arbrandes
Copy link

Closing in favor of openedx/edx-platform#31616, which in spite of having come later, contains more detail.

@github-project-automation github-project-automation bot moved this from Backlog to Shipped in Nutmeg in Open edX Roadmap May 23, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Closed in Frontend Working Group May 23, 2023
@arbrandes arbrandes moved this from Shipped in Nutmeg to Done - Not Shipped in Open edX Roadmap May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Large unit of work, consisting of multiple tasks
Projects
Development

No branches or pull requests

4 participants