Need states and process in RFC process

[ingenthr]

Process in Github and States

Identified >> Draft >> Review >> Accepted

Goal: use github commenting as a way to receive feedback from everyone prior to ACCEPTED.

Identified: Open an issue

Draft: Put together a branch of your own, edit away, when ready for core team review, send pull request and add to README. Core team comments. When ready for stakeholder review, send out something to circulate, no status change. Stakeholders must add their parts before it goes to REVIEW state.

Review: Update the doc to indicate REVIEW status, update the README to indicate status, and ensure it points to the correct pull request. Set an expiration of a minimum of 1 week, no maximum.

Accepted: Merge into RFCs. Further feedback should be handled by github issues.

[daschl]

So this actually breaks down into:

• Adding explicit states to the rfc process
• Changing the rfc process to the proposed approach here
• Add the concept of an errata and add information that once an rfc is accepted it is not changed, but changes are appended in the errata.