[Openstack-docs] OpenStack docs review policy
Anne Gentle
anne at openstack.org
Thu Aug 22 02:00:49 UTC 2013
On Wed, Aug 21, 2013 at 8:15 PM, Sean Roberts <seanrob at yahoo-inc.com> wrote:
> I disagree with having to wait for another core member before +2 approve
> in all situations. For example, the training docs are very early, changing
> often, and with only a few active contributors. If I find a bug in the how
> to contribute instructions, I need to get it published right away.
> Once we have more members and have grown up a bit, I'm good with reviews
> requiring more eyes.
>
>
Yes Sean, I agree that the openstack-training folder is one exception here.
> ~sean
>
> On Aug 21, 2013, at 11:33, "Andreas Jaeger" <aj at suse.com> wrote:
>
> > On 08/21/2013 05:25 PM, Anne Gentle wrote:
> >> Hi all,
> >> I'm updating the Documentation/HowTo wiki page with the following
> >> description of our review policy. Please let me know if there are any
> >> questions. I'll definitely update the wiki page as we refine our policy.
> >> ---
> >> All community members can review doc patches and give them +1 or -1.
> >> Documentation Core members can give +2 or -2 votes and also click
> >> Approve so that the doc goes live, published to docs.openstack.org
> >> <http://docs.openstack.org> or api.openstack.org
> >> <http://api.openstack.org>, based on the branch the patch is applied
> to.
> >>
> >> Because the Docs team is small, core members have the choice when
> >> reviewing and must use best judgement before publishing. Generally
> >> speaking, core members will wait for one other core member to +2 a doc
> >> patch. However if the change is small and the build works, a doc core
> >> member can +2 and Approve a change without waiting for another reviewer.
> >> This is a judgement call so docs core people should exercise judgement
> >> when using this option.
> >>
> >> Once two community members approve a doc patch, a doc core member can
> >> also review it and push it through without waiting for a second core
> member.
> >> ---
> >
> > In other words - or as summary: Before a core member approves a patch,
> > it needs either another core members +2 or two +1s - and non-core
> > members are welcome to +1 a patch.
> >
> > Andreas
> > --
> > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
> > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> > GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
> > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> >
> > _______________________________________________
> > Openstack-docs mailing list
> > Openstack-docs at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130821/15a67203/attachment-0001.html>
More information about the Openstack-docs
mailing list