openedx / openedx/openedx-events
Improve how to contribute and review expectations
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:
The most confusing part for me was figuring out WHO should be reviewing requests? Or if there was a process for requesting a review. Otherwise, I found documentation to be very helpful. My biggest complaint, last time I was working in these repos the documentation was still in PRs and a WIP, but it contained a lot of useful and important info. Hopefully those PRs made their way into being merged at this point to help discoverability.
The events and filter definitions are in a separate repo and that always creates some friction with PRs since you have a multi-step process of merging and bumping versions based on another pr.
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 does not name files, tests, or entry points. Start by reviewing the repository's contribution and review guidance, then clarify how contributors request reviews and how the separate events and filter definitions repository affects version bumps; done means these workflows and expectations are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100