-
Notifications
You must be signed in to change notification settings - Fork 71
/
CONTRIBUTING.md
29 lines (21 loc) · 1.35 KB
/
CONTRIBUTING.md
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# Contribution Guidelines
Please ensure your pull request adheres to the following guidelines:
* Please search previous suggestions before making a new one, as yours may be a duplicate.
* Please make an individual pull request for each suggestion.
* Use the following format: \[RESOURCE\]\(REPO-LINK\) - DESCRIPTION. [LICENCE] \[website\]\(WEB-LINK\)
* Keep descriptions short and simple.
* End all descriptions with a full stop/period.
* Make sure your text editor is set to remove trailing whitespace.
* Order projects alphabetically within each category.
* Check your spelling and grammar.
* New categories, or improvements to the existing categorisation are welcome.
## Pull requests workflow
Please, submit one pull requests with one link per PR. If you want to add several links, you should create PR for each links, unless all of the proposed projects are belong to the same category. Pull request should have meaningful description what this project do, why do you want to add it to the list and any other info which might be useful. This will help maintainers with the review process.
## Quality standard
To stay on the list, projects should follow these quality standards:
* Generally useful to the community
* Actively maintained (even if that just means acknowledging open issues when they arise)
* Stable
* Documented
* Tests
Thank you for your suggestions!