openedx / openedx/openedx-events
Marking events experimental
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 33
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 4
Description
Someone (not me, but I am completely blanking on who at the moment 😞 ) brought up the idea of marking new events "experimental" for a certain period of time after initial introduction so that we have a little more flexibility to change things before we mark them as "supported" for long term usage. I thought this was a good idea, but I'm curious what others thought.
FYI: @mariajgrimaldi, @felipemontoya, @feanil, @robrap
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 reviewing how this repository currently introduces and labels events; the issue does not name specific files, tests, or entry points. Clarify the proposed experimental period, lifecycle states, and compatibility expectations before implementation; done would mean an agreed design and corresponding repository changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100