|
1 | 1 | # Contribution Guidelines
|
2 |
| -Please ensure your pull request adheres to the following guidelines: |
| 2 | +Ensure your pull request adheres to the following guidelines: |
3 | 3 |
|
4 |
| -* This is an open source compilation, please check that the license of the software is suitable. |
5 |
| -* Search previous suggestions before making a new one, as yours may be a duplicate. |
6 |
| -* Make an individual commit for each suggestion. |
| 4 | +* This is an open source compilation. |
| 5 | + * Check the license of the software is suitable. |
| 6 | +* Search previous suggestions before making a new one. |
| 7 | + * Don't create duplicates. |
| 8 | +* Make an individual commit for each category. |
7 | 9 | * Consolidate multiple commits to a pull request.
|
8 | 10 | * In pull request descriptions:
|
9 |
| - * Don't use past tense or present progressive (added, adding) |
10 |
| - * Include the application names and categories |
| 11 | + * Use imperative (e.g. add instead of added/adding). |
| 12 | + * Include application names and categories. |
| 13 | + * Include a link to the open source project page. |
11 | 14 | * Example: *Add mosh, openSSH to SSH*
|
12 | 15 | * Use the following format: \[RESOURCE\]\(LINK\) - DESCRIPTION.
|
13 |
| -* Keep descriptions short. |
14 |
| -* End all descriptions with a full stop/period. |
| 16 | + * Keep descriptions short. |
| 17 | + * End descriptions with a full stop/period. |
15 | 18 | * Order projects alphabetically within each category.
|
16 |
| -* Check your spelling and grammar. |
17 |
| -* New categories, or improvements to the existing categorisation are welcome. |
| 19 | +* Check spelling and grammar. |
| 20 | +* Improvements to the existing categorisation are welcome. |
18 | 21 |
|
19 |
| -Thank you for your suggestions! |
| 22 | +Thank you very much for your suggestions! |
0 commit comments