[DOCS] "Contributing" page sets unrealistic expectations
@scriptautomate-bc is already working on this.
Since Apr 10, 2025.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
The CONTRIBUTING page claims that PRs with test cases will generally receive some kind of response the same business day, and sometimes even been merged that day.
Suggested Fix
The documentation should be updated to reflect the kind of response that contributors should expect, rather than presenting such an optimistically ambitious standard.
Also, what is the preferred way of kicking loose an issue that seems to have fallen through the cracks? How long should one wait before pinging an assigned reviewer if we haven't heard from them?
Type of documentation
CONTRIBUTING guide.
Location or format of documentation
https://github.com/saltstack/salt/blob/master/CONTRIBUTING.rst#now-what
Additional context
n/a
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.
Assessment
This issue has not been assessed yet.