<div dir="ltr"><div><div><div>Hi,<br><br></div>I would like to discuss the documentation process and align it to OpenStack flow.<br><br></div>At the moment we add special tags to bugs in Launchpad which is not optimal as everyone can add/remove tags<br></div><div>cannot participate in documentation process or<br></div><div>enforce documentation process.<br><br></div><div>I suggest to switch to standard workflow that is used by OpenStack community<br></div><div>All we need is to move the process of tracking documentation from launchpad to gerrit<br><br></div><div>This process gives more control to individual developers or community for tracking the changes and reflect them in documentation.<br><br></div><div>Every reviewer checks the commit. If he thinks that this commit requires documentation update, he will set -1 with comment message "Docs impact required"<br><br></div><div>This will force the author of patchset to update commit with "DocImpact" commit message<br><br></div><div>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.<br><br></div><div>Patches in fuel-docs may have the same Change-ID as original patch. It will allow us to match documentation and patches in Gerrit. <br><br></div><div>More details about DocImpact flow ban be obtained at<br></div><div><br><a href="https://wiki.openstack.org/wiki/Documentation/DocImpact">https://wiki.openstack.org/wiki/Documentation/DocImpact</a><br><br></div><div><div><div><div><div><div><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div>
</div></div></div></div></div></div>