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

Move content_libraries to cms? #33428

Open
Tracked by #33640
kdmccormick opened this issue Oct 5, 2023 · 0 comments
Open
Tracked by #33640

Move content_libraries to cms? #33428

kdmccormick opened this issue Oct 5, 2023 · 0 comments
Labels
code health Proactive technical investment via refactorings, removals, etc. content libraries misc Libraries Overhaul tech work not captured in the stories

Comments

@kdmccormick
Copy link
Member

kdmccormick commented Oct 5, 2023

Background

The content_libraries django app, exists in the openedx/ source dir, which is used by both LMS and CMS. This means that all content_libraries-related code is available to be imported and invoked in LMS, which could lead to some unintended bugs or architectural issues down the line.

Opinion: Content libraries are used by authors, but NOT learners or instructions. The entire purpose of content libraries is for authors to create content that is NOT visible to the LMS, and then use that content in their courses. There is no reason that content-libraries-supporting code should need to execute in LMS. (We don't have consensus on this opinion.)

Tasks

Figure out whether content_libraries belongs in openedx/ or cms/.

If it belongs in cms/:

Details

TBD. Needs refinement.

@kdmccormick kdmccormick changed the title Move content_libraries to cms Move content_libraries to cms? Oct 5, 2023
@kdmccormick kdmccormick added code health Proactive technical investment via refactorings, removals, etc. content libraries misc Libraries Overhaul tech work not captured in the stories labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Proactive technical investment via refactorings, removals, etc. content libraries misc Libraries Overhaul tech work not captured in the stories
Projects
None yet
Development

No branches or pull requests

1 participant