openedx / openedx/openedx-events
Review current events for removal or deprecation
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 33
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 4
Description
Description
There are a few events that are not being used in any service that should be reviewed to decide whether to drop support:
- COURSE_CERTIFICATE_CONFIG_CHANGED
- COURSE_CERTIFICATE_CONFIG_DELETED
- SUBSIDY_REDEEMED
- SUBSIDY_REDEMPTION_REVERSED
And others where we should start a deprecation process because the event was replaced by a new one:
- CONTENT_OBJECT_TAGS_CHANGED
Definition of Done
- The team that implemented the event is aware of the event's status
- The events were implemented in a service, removed or deprecated.
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 by searching for the five listed event names and identifying the services that implement them, including the replacement for CONTENT_OBJECT_TAGS_CHANGED. Contact or confirm with those teams, then record whether each event is retained, removed, or deprecated and verify the definition-of-done conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100