Create proposal-process.md

[abadger]

• s/committee/team/
• We don't operate by consensus. Maybe "we attempt to operate by consensus of its members; falling back on a vote of the members if an impasse is reached" ?
• I don't think we're going to have acceptance tests and multiple implementations.
• Proposals is really more about getting the specification/design done
• Needs to have information about how the champion pushes the proposal through these stages (ie: put it on the meeting agenda, announce to the mailing list, etc)
• I really would like to see an "Alternatives" section mentioned. "An alternative to address this problem was Foo. We decided on this over Foo because of Reason X, Y, Z."

[jctanner]

The Core committee is responsible for evolving Ansible (the language), and authoring the specification.

There is a range of factors behind us deciding to press the merge button on PRs. To name a few:

1) Fixes an existing issue found by many members of the community 2) Many community members find a feature desirable 3) Security concerns 4) Fixes broken CI tests

What problem is this proposed process really trying to solve?