Update CONTRIBUTING.md

Author: doublerr

CONTRIBUTING.md

@@ -3,16 +3,27 @@ CONTRIBUTING
 
 # General
 * The following document will serve as a guide on what and how to contribute to any cookbook within [rackspace-cookbooks](https://github.com/rackspace-cookbooks/).
+* The cookbookname, attribute namespace and git repo should all have the same name
+ * i.e. rackspace_yum 
+
+## Attributes
+* All attributes should by ruby symbols instead of strings
+ * i.e. `default[:rackspace_apache]` instead of `default['apache']`
+* All Attributes namespace should match the cookbook name
+ * i.e. `default[:rackspace_user]`
+* All Attributes that will be written a configuration file must fall under a [:config] hash
+ * i.e. `default[:rackspace_apache][:config]`
+
 
 ## Licensing
 * All Cookbooks must be Apache 2.0 licensed. 
 * Include a `LICENSE` file in the top level directory of the cookbook with the Apache 2.0 Official license
-* Include a `License and Authors` section of the `README.md`. See example at [chef-client](https://github.com/rackspace-cookbooks/chef-client)
+* Include a `License and Authors` section of the `README.md`. See example at [rackspace-user](https://github.com/rackspace-cookbooks/rackspace-user)
 * If you've forked the cookbook from another repo, please add notes attributing the original work to that repo
 
 ## README.md / Documentation
 * Please include a README.md file in the cookbook root directory.
-* Please include Descriptions, Platform support, notes, nots on recipes, attributes, etc
+* Please include Descriptions, Platform support, notes, nots on recipes, attributes, CONTRIBUTING and testing specifications.
 
 ## CHANGELOG.md
 * Please include a `CHANGELOG.md` in the cookbook root directory
@@ -27,13 +38,18 @@ CONTRIBUTING
 
 ## test-kitchen support
 * test-kitchen 1.0 support is required for all cookbooks. Please see [test-kitchen](https://github.com/opscode/test-kitchen) for more details.
+* test-kitchen should include platforms for
+* 
 
 ### test-kitchen structure
 * Tests should be handled as a sub cookbook under /test/cookbooks/$name_test similar to how the opscode [chef-client](https://github.com/rackspace-cookbooks/chef-client) cookbook is layed out. 
-* The tests should be called and have any needed attributes set in a .kitchen.yml file with seperate suites as appropiate. We will append our own .kitchen.local.yml that provides kitchen-openstack support for our own testing.
+* The tests should be called and have any needed attributes set in a .kitchen.yml file with seperate suites as appropiate. We will append our own .kitchen.local.yml via branch `testint` that provides kitchen-openstack support for our testing against openstack.
 
 ## foodcritic
 * TODO: Add notes regarding foodcritic
+* 
+
+## chefspec/serverspec/minitest
 
 # Code Review
 * All code additions and pull requests are subject to the following: