Propose universe endpoint for chef-server
Propose arbitrary cookbook identiers via new API endpoint
Resolved: name endpoint /universe

This will be most compatible with existing tooling
Specify that the location_type is "chef_server"
Clarify design constraints for arbitrary ID feature.
Added initial draft of platform support policy
Update ChefDK Mac support
Added missing RHEL row
Give an example of extended cookbook data in "list" API
Add bulk artifact API
Renumbering RFCs, reserving 0-10 for administrivia
Merge pull request #19 from opscode/universe-endpoint

Propose universe endpoint for chef-server
Assigning rfc014
Update Gentoo, Arch, OpenSUSE; add clarifications for upstream vendor
lifecycle support terminology per @danielsdeleo
Damn I don't know how to <table>
Accept most modifications from @coderanger
It's ok if Omnitruck goes into Yolo mode, it just can't fail
Forgot Ubuntu under ChefDK. Also, added OmniOS releases
Remove CVT jargon, just mention what we're doing with 'post-build verification'
Fix incorrect Solaris information
Tighten up the language around what we will do for PRs about unsupported OSes.
Spell out 'Oracle' -> 'Oracle Enterprise Linux'