Permalink
Browse files

Specify Contribution Guide to FRC

  • Loading branch information...
ErikBoesen committed Nov 9, 2017
1 parent 750acbb commit e828ecdca6f291100329128e6b9a5a237d63f61d
Showing with 8 additions and 6 deletions.
  1. +8 −6 CONTRIBUTING.md
View
@@ -1,6 +1,6 @@
# Contribution Guidelines
Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms.
The Awesome List [Contributor Code of Conduct](https://github.com/sindresorhus/awesome/tree/master/code-of-conduct.md) applies to this repository. By participating in this project you agree to abide by its terms.
## Table of Contents
@@ -11,16 +11,18 @@ Please note that this project is released with a [Contributor Code of Conduct](c
Please ensure your pull request adheres to the following guidelines:
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description.
- **If you just created something, wait 30 days before submitting.** This is a list of important and Awesome FRC materials, not every small project every contributor has given. Similarly, please don't submit projects for which there's no plan of maintenance. If you're going to graduate next year and abandon your prokect, don't add it to this list.
- Some parts of this list are quite saturated. If you're planning to add your scouting app, it should offer something not covered by existing apps (a new platform or use case, for instance).
- If your submission is not your own work, search prior pull requests to check you're not duplicating a suggesion.
- If your submission is a GitHub repository, it should have a complete and well-written README, LICENSE file, and the like.
- Make an individual pull request for each suggestion.
- Use [title-casing](http://titlecapitalization.com) (AP style).
- 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.
- New categories, recategorization of existing resources, or improvements to the existing categorization are welcome.
- Neither poor spelling nor grammar will be tolerated in your changes or your project.
- Make sure your text editor is set to remove trailing whitespace.
- The pull request and commit should have a useful title.
- Your pull request and commit should have a useful title.
- The body of your commit message should contain a link to the repository.
Thank you for your suggestions!

0 comments on commit e828ecd

Please sign in to comment.