openedx / openedx/openedx-events
How to implement events with long term support
Open
Nobody has claimed this yet.
documentation
- 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:
Each event/filter needs to be well thought out with a longish term support so how to structure it can be a heavy decision .
How can we document this better to make the design process easier?
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
No files, tests, or entry points are named. Start by reviewing the issue context and linked community survey, then determine what documentation would make long-term event and filter design easier; done means the design process and support considerations are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100