Added initial draft of platform support policy
Update ChefDK Mac support
Added missing RHEL row
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'
Missing period at end of sentence.

Per our discussion that this RFC is "aspirational", I've added what I think is the desired target list
for Chef-DK platforms. The diff shows exactly the delta between where we are today and where it sounds
like we want to be (modulo my error about RHEL 5.x which isn't supported today).
Again, since this is aspirational: we want to support EL7 as a target platform for server binaries.
An RFC to standarize on two workflows

This RFC proposes two workflows as "supported", and abstracts
as much of their differences as possible through the use of
additional generators and functionality in the 'chef' command.

If accepted, this RFC would also serve as a guide for tool makers,
as to what the requirements are for maximum converage in the Chef
community.

While other workflows are possible, this RFCs job is to say which
ones we support officially.
Initial RFC for community guidlines

Start by capturing the current community guidlines as outlined on
http://docs.getchef.com/community_guidelines.html
Spell guidelines correctly
Update the list of influences on this document
reformat the copyright section
Initial draft

* Not complete
* Ready for feedback and comments though
Update motiviation

Provides unique verbage that more closely fits the template.
Delete "short version"

This summarizes other text. Perhaps it is ultimately valuable, but if so I believe
we should add it as an amendment after we've come to agreement on the long form.