[openstack-dev] [nova][api] API working group liaisons and responsibilities

michael mccune msm at redhat.com
Thu Apr 30 15:13:21 UTC 2015

+1, i think this is really nice


On 04/30/2015 10:54 AM, Jay Pipes wrote:
> Hi Stackers,
> OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova
> team's liaisons to the API working group. Big thank you to Matthew and
> Alex for volunteering for this important role.
> I've created a wiki page [1] that details the responsibilities of these
> liaisons. If these duties work out for Nova, we'll recommend other
> projects pick them up.
> Here are the responsibilities that the Nova/API working group liaisons
> have:
> 1. Monitor the active patch queue in nova (and nova-specs) and look out
> for any patch that adds or changes the REST API
> 2. For each patch collected in #1, determine if the constructs used in
> the patch (or proposed spec) match the guidance currently laid out in
> the API working group repo's guidance documents.
> 3. If the patch does NOT match the guidance from the API working group,
> do a code review on the patch pointing to the guidance from the API
> working group, and ask the author to align with that guidance. Include
> in your research patches to the API working group that may actually be
> in review and not merged. (An example of this recently occurred with
> Sergey Nikitin's re-proposed instance tagging spec:
> https://review.openstack.org/#/c/177112/. See Ryan Brown's reference to
> an in-progress API working group guidance on tagging)
> 4. If there is NO guidance in the API working group repo for a
> particular proposed API change or addition, the liaison should
> **either** create a proposed patch to the API working group with
> guidance that clarifies the missing functionality that is introduced in
> the new Nova patch or spec patch, and bring the proposed guidance to the
> attention of the API working group. **or** the liaison should working
> with a member of the API working group to draft such a guideline. The
> liaison should mark the corresponding Nova patch with a -1 Code Review
> vote with a link to the proposed guideline, noting that the patch should
> be put on hold (Work In Progress) until the guideline is merged.
> Best,
> -jay
> [1] https://wiki.openstack.org/wiki/Nova/APIWGLiaisons
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list