Open Stack

Hi,

I would like to discuss the documentation process and align it to OpenStack
flow.

At the moment we add special tags to bugs in Launchpad which is not optimal
as everyone can add/remove tags
cannot participate in documentation process or
enforce documentation process.

I suggest to switch to standard workflow that is used by OpenStack community
All we need is to move the process of tracking documentation from launchpad
to gerrit

This process gives more control to individual developers or community for
tracking the changes and reflect them in documentation.

Every reviewer checks the commit. If he thinks that this commit requires
documentation update, he will set -1 with comment message "Docs impact
required"

This will force the author of patchset to update commit with "DocImpact"
commit message

Our documentation team will get all messages with DocImpact from 'git log'.
The documentation team will make a documentation where the author of patch
will play a key role. All other reviewers from original patch must give own
+1 for documentation update.

Patches in fuel-docs may have the same Change-ID as original patch. It will
allow us to match documentation and patches in Gerrit.

More details about DocImpact flow ban be obtained at

https://wiki.openstack.org/wiki/Documentation/DocImpact

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140924/dd226159/attachment.html>