openedx / openedx/openedx-events
How to implement organization-scoped events
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 33
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 4
Description
Description
Some comments I've gathered from the community survey on the challenges/suggestions section:
I think it would be interesting for organizations to be able to create their own events without committing them to the core or forking. For example, could I create a package of my own and associate a new event with an exception or a model change?
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
The issue contains a community-survey suggestion but names no files, tests, or entry points. Start by tracing how events and extensions are currently defined and registered in the project. Done would mean a documented design and implementation path for organizations to define events without modifying or forking the core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100