New draft of the contribution guidelines

checkGoreportcard
Matt Holt 10 years ago
parent e6e331f2ec
commit 7147e6e13c

@ -1,11 +1,33 @@
# Contributing
This resource was made by the Go community and wouldn't be possible without you! We appreciate and recognize [all contributors](https://github.com/avelino/awesome-go/graphs/contributors).
As a newcomer on a large project, its easy to experience frustration. Heres some advice to make your work on **awesome-go** more useful and rewarding.
# Contribution Guidelines
* Packages sort alphabetically
* Package must be in godoc.org or is documented
* Packages need to have tests
* Package must be active (make sure the package is active)
* Add package that you have used
* Be bold! Leave feedback!
* Be rigorous
- **To add to the list:** Submit a pull request
- **To remove from the list:** Open an issue
To set this list apart from and compliment the excellent [Go wiki Projects page](https://code.google.com/p/go-wiki/wiki/Projects), awesome-go is a specially curated list for high-quality, actively maintained Go packages and resources.
- List items should be sorted *alphabetically*.
- Each item should be limited to one link
- The link should be the name of the package or project
- Descriptions should be clear, concise, and non-promotional
- Descriptions should follow the link, on the same line
Please contribute links to packages/projects you have used or are familiar with. This will help ensure high-quality entries.
## Quality standard
To stay on the list, package repositories should adhere to these quality standards:
- Generally useful to the community
- Functional
- Actively maintained (even if that just means acknowledging open issues when they arise)
- Stable, or progressing toward stable
- Documented (preferably godoc.org)
- Tests are preferred (when possible)
## Reporting issues
Please open an issue if you find anything that could be improved or have suggestions for making the list a more valuable resource. We realize sometimes packages fall into abandonment or have breaking builds for extended periods of time, so if you see that, please let us know. We also realize that sometimes projects are just going through transitions or are more experimental in nature. These can still be cool, but we can indicate them as transitory or experimental -- again, just open an issue. Thanks everyone!

Loading…
Cancel
Save