From 1ad072d3474c00b70fc7c06a273555b2a530d3d3 Mon Sep 17 00:00:00 2001 From: jivoi Date: Mon, 29 May 2017 13:40:06 +0300 Subject: [PATCH] fix --- CONTRIBUTING.md | 32 ++++++++++++++------------------ 1 file changed, 14 insertions(+), 18 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5727980..3f15763 100755 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,22 +1,18 @@ # Contribution Guidelines -This is a compilation of **Free and Libre Open Source Software ([FLOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software))**. Restrictive licenses (aka Freeware, Shareware) are *not awesome*. +Please ensure your pull request adheres to the following guidelines: -## Commits -* Search previous suggestions before making a new one. -* Use the following format: `[RESOURCE](LINK) - DESCRIPTION.` - * Keep descriptions short (<80 characters). - * End descriptions with a full stop. -* Make an individual commit for each category. - * Order projects alphabetically. - * Consolidate multiple commits. +- Read [the awesome manifesto](https://github.com/sindresorhus/awesome/blob/master/awesome.md) and ensure your list complies. +- Search previous suggestions before making a new one, as yours may be a duplicate. +- Make sure your list is useful before submitting. That implies it having enough content and every item a good succinct description. +- A link back to this list from yours, so users can discover more lists, would be appreciated. +- Make an individual pull request for each suggestion. +- Titles should be [capitalized](http://grammar.yourdictionary.com/capitalization/rules-for-capitalization-in-titles.html). +- Use the following format: `[List Name](link)` +- Link additions should be added to the bottom of the relevant category. +- New categories or improvements to the existing categorization are welcome. +- Check your spelling and grammar. +- Make sure your text editor is set to remove trailing whitespace. +- The pull request and commit should have a useful title. -## Pull Requests -* Use imperative (e.g. add instead of added/adding) in the PR title. -* Include application names, categories and a link to the open source project page in the description. - -## Issues -* Discussion, questions and bug reports only. -* If you are sure software meets the guidelines, create a Pull Request (see above). -* Check spelling and grammar. -* Suggestions for improvements to existing structure are welcome. +Thank you for your suggestions! \ No newline at end of file