Remove dependency on Discovery IDA
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 83
- Avg merge
- 11h 51m
- Merged PRs (30d)
- 1
Description
Context
During discussion about the future of Credentials IDA and it's functionality, it came up to discussion that dependency on Discovery brings a lot of complexity for operating Discovery. Discovery is used to provide Programs and Course Runs data to form a Learner Record for a user. Furthermore, programs can be configured only in Discovery IDA, therefore the dependency between Credentials and Discovery can't be removed without changes to programs implementation in Open edX.
It was decided to evaluate the possibility of reimagining the Program's implementation, so this functionality can be moved out of Discovery IDA and integrated directly into LMS, for example via a separate plugin. This would reduce operational complexity, but also make it possible to evolve and provide more value for community installations.
This ticket can be used for tracking purposes for this initiative.
Next steps
- Prepare a proposal for updating Programs implementation in Open edX
- Review and discuss proposal in the community
- Outline roadmap for Credentials IDA to remove Discovery IDA as dependency and integrate with LMS more closely
Additional References:
Discovery IDA DEPR ticket - https://github.com/openedx/course-discovery/issues/4449
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the prepared proposal for updating Programs implementation in Open edX and the Discovery IDA DEPR ticket, course-discovery#4449. Review the community discussion, then outline a roadmap for removing Discovery IDA as a Credentials dependency and integrating Programs more closely with LMS. Done means the proposal has been reviewed and discussed and the roadmap is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100