Document the existing process to help reviewers, especially newcomers, understand how to review specs. This is migrating the existing wiki documentation into a policy.
Care should be taken when approving specs. An approved spec, and an associated blueprint, indicate that the proposed change has some priority for the TripleO project. We don’t want a bunch of approved specs sitting out there that no community members are owning or working on. We also want to make sure that our specs and blueprints are easy to understand and have sufficient enough detail to effectively communicate the intent of the change. The more effective the communication, the more likely we are to elicit meaningful feedback from the wider community.
To this end, we should be cognizant of the following checklist when reviewing and approving specs.
This is migrating the already agreed upon policy from the wiki.
Once the policy has merged, an email should be sent to openstack-dev referring to this document.
|Ocata||Migrated from wiki|
This work is licensed under a Creative Commons Attribution 3.0 Unported License. http://creativecommons.org/licenses/by/3.0/legalcode