awesome/nodejs
1
0
Fork 0
mirror of https://github.com/sindresorhus/awesome-nodejs.git synced 2024-11-20 11:27:17 -05:00
Code Activity

Fix typo in contribution guidelines (#780)

Browse source
This commit is contained in:
Jeff Dickey 2018-02-15 00:35:52 -08:00 committed by Sindre Sorhus
parent c7525e5c0a
commit ea74c6f6da
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
contributing.md
View file

@ -8,7 +8,7 @@ Ensure your pull request adheres to the following guidelines:
- **If you just created something, wait at least 30 days before submitting.** This is to give it some time to mature and ensure it's not just a publish-and-forget type of project. - **If you just created something, wait at least 30 days before submitting.** This is to give it some time to mature and ensure it's not just a publish-and-forget type of project.
- Keep in mind that the list is very mature by now, so the bar of getting something accepted is high. Only submit something unique and generally useful. The world (and this list) doesn't need yet another ORM or framework. For CLI tools, the bar is especially high, and unless it's something very awesome, I would suggest submitting to [awesome-cli-apps](https://github.com/aharris88/awesome-cli-apps) instead. - Keep in mind that the list is very mature by now, so the bar of getting something accepted is high. Only submit something unique and generally useful. The world (and this list) doesn't need yet another ORM or framework. For CLI tools, the bar is especially high, and unless it's something very awesome, I would suggest submitting to [awesome-cli-apps](https://github.com/aharris88/awesome-cli-apps) instead.
- If you submit a project that is similar to an existing project in the list, argument how it's better. - If you submit a project that is similar to an existing project in the list, argue how it's better.
- Search previous suggestions before making a new one, as yours may be a duplicate. - Search previous suggestions before making a new one, as yours may be a duplicate.
- Suggested packages should be tested and documented. - Suggested packages should be tested and documented.
- Make an individual pull request for each suggestion. - Make an individual pull request for each suggestion.