awesome-php/CONTRIBUTING.md

# Contribution Guidelines
Unfortunately, not every library, tool or framework can be considered for inclusion. The aim of Awesome PHP is to be a concise list of noteworthy and interesting software written in modern PHP. Therefore, suggested software should: 

a) Be widely recommended regardless of personal opinion  
b) Well known or discussed within the PHP community  
c) Be unique in its approach or function  
d) Fill a niche gap in the market  

Self-promotion is frowned upon, so please consider seriously whether your project meets the criteria before opening a pull request, otherwise it may be closed without being reviewed.

Also, please ensure your pull request adheres to the following guidelines:

* Software that is PHP 5.5+, Composer-installable, PSR compliant, semantically versioned, united tested and well documented in English is preferred.
* Please search previous suggestions before making a new one, as yours may be a duplicate.
* Enter a meaningful pull request description.
* Please make an individual commit for each suggestion in a separate pull request.
* Put a link to each library in your pull request ticket so it's easier to review.
* Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
* Prefix duplicate library names with their vendor or namespace followed by a space: Foo\Bar would be Foo Bar.
* New categories, or improvements to the existing categorisation, are always welcome.
* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon. 
* End all descriptions with a full stop/period.
* Check your spelling and grammar.
* Make sure your text editor is set to remove trailing whitespace.

Thank you for your suggestions!
Add contribution guidelines. 2013-12-30 07:33:17 +00:00			`# Contribution Guidelines`
Improve formatting 2016-01-21 23:52:04 +00:00			`Unfortunately, not every library, tool or framework can be considered for inclusion. The aim of Awesome PHP is to be a concise list of noteworthy and interesting software written in modern PHP. Therefore, suggested software should:`
Add contribution guidelines. 2013-12-30 07:33:17 +00:00
Improve formatting 2016-01-21 23:52:04 +00:00			`a) Be widely recommended regardless of personal opinion`
			`b) Well known or discussed within the PHP community`
			`c) Be unique in its approach or function`
			`d) Fill a niche gap in the market`
Improve contribution guidelines 2016-01-21 23:45:05 +00:00
Fix typo 2016-01-21 23:53:02 +00:00			`Self-promotion is frowned upon, so please consider seriously whether your project meets the criteria before opening a pull request, otherwise it may be closed without being reviewed.`
Improve contribution guidelines 2016-01-21 23:45:05 +00:00
			`Also, please ensure your pull request adheres to the following guidelines:`

Add semver to contribution guidelines 2016-01-29 15:53:16 +00:00			`* Software that is PHP 5.5+, Composer-installable, PSR compliant, semantically versioned, united tested and well documented in English is preferred.`
Tweak guidelines. 2013-12-30 23:47:47 +00:00			`* Please search previous suggestions before making a new one, as yours may be a duplicate.`
Updated contribution guidelines with note about PR titles 2015-08-03 23:36:32 +00:00			`* Enter a meaningful pull request description.`
Updated Contribution Guidelines. 2016-02-08 18:23:17 +00:00			`* Please make an individual commit for each suggestion in a separate pull request.`
Improve contribution guidelines 2016-01-21 23:45:05 +00:00			`* Put a link to each library in your pull request ticket so it's easier to review.`
Tweak guidelines. 2013-12-30 23:47:47 +00:00			`* Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.`
Tweak contribution guidelines, and add info about trailing whitespace. 2014-07-11 02:39:44 +00:00			`* Prefix duplicate library names with their vendor or namespace followed by a space: Foo\Bar would be Foo Bar.`
Updated contribution guidelines with note about PR titles 2015-08-03 23:36:32 +00:00			`* New categories, or improvements to the existing categorisation, are always welcome.`
Improve formatting 2016-01-21 23:52:04 +00:00			`* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon.`
Tweak guidelines. 2013-12-30 23:47:47 +00:00			`* End all descriptions with a full stop/period.`
			`* Check your spelling and grammar.`
Tweak contribution guidelines, and add info about trailing whitespace. 2014-07-11 02:39:44 +00:00			`* Make sure your text editor is set to remove trailing whitespace.`
Add contribution guidelines. 2013-12-30 07:33:17 +00:00
Update CONTRIBUTING.md Fixed spelling 2014-07-11 19:57:44 +00:00			`Thank you for your suggestions!`