Improve how to contribute and review expectations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Review the existing contribution and review guidance, including the survey feedback linked in the issue. Clarify who reviews requests, how review is requested, and how the separate events and filter definitions repository affects the PR and version-bump process; done means these expectations are documented and discoverable.
Written by the indexing model from the issue text.
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.
- Dominant language
- Python
- Stars
- 10
- Forks
- 30
- Avg merge
- 5h 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from openedx/openedx-filters
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
openedx/openedx-filters#420 · 2 comments ·
Maintainers usually reply within 1 day
-
Filter Integration Issues After Transition to MFEsMay be free again @mariajgrimaldi claimed this 663 days ago, and no pull request is open. Open
openedx/openedx-filters#255 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
openedx/openedx-filters#245 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
openedx/openedx-filters#196 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
openedx/openedx-filters#195 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-filters
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
mozilla-ai/cq#601 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
intcomma returns exponential notation for large floatsPossibly taken @Omarinho12345 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-humanize/humanize#521 ·
Maintainers usually reply within 1 day
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesPossibly taken @hat-im claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·