Change rules to simplify PR analysis

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +0,0 @@
-### Application name / category
-[awesometool](https://example.com) / Devops
-
-### Source URL
-https://github.example.com/repo
-
-### why it is awesome
-This tool is so awesome because it allows me to do awesome things in my
-awesome corp, especially when I use it to manage awesome othersoftware.

.travis.yml

@@ -1,7 +0,0 @@
-language: ruby
-rvm:
-  - 2.2
-before_script:
-  - gem install awesome_bot
-script:
-  - awesome_bot README.md --allow-dupe --allow-redirect --white-list bestpractical.com/rt,mogilefs,harding,archipel,linuxcontainers,spiceworks

CONTRIBUTING.md

@@ -1,23 +1,23 @@
 # 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 adhere to the following guidelines or your Pull Request will be closed.
-
-**Submitting your own software is not awesome**, unless you have a healthy ecosystem with a few contributors which aren't your sock puppet accounts.
+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*.
 
 ## 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.
+  
 ## Pull Requests
-
-* Consolidate multiple commits.
 * Use imperative (e.g. add instead of added/adding) in the PR title.
+* Insert only one software per PR.
 * Include application names, categories and a link to the open source project page in the description.
-* Write a short text why the application you're adding is actually awesome.
-  * Put only stuff on the list you or another contributor can personally recommend
-  * Recommending your own software is discouraged.
+
+## 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.