Sorry I'm so late to the party. Yes, Andreas is right, we simply cannot take on any more DocImpact in openstack-manuals, but it would be great to change the infrastructure to log against a more exact match for the bug tracker for the project with the impacted docs. Looks like you're doing so with https://review.openstack.org/125434 so I'm reviewing there.
Some additional protips for devs: There's an indicator called docimpact-group: for each project. In that setting, enter the Launchpad bug project you want bugs automatically logged into. (wow that's strange grammar). Don't use docimpact-group: openstack-manuals unless your project is integrated. We can't blow out our doc bug numbers artificially. Don't use docimpact-group: openstack-manuals for common projects like Oslo, QA, or Infra repos. I'm working on a cleanup patch. No need to use docimpact-group for specs repos or docs repos. We'll cover all this and more at a docs bootstrapping session coming soon! Thanks, Anne On Thu, Sep 25, 2014 at 1:39 AM, Andreas Jaeger <a...@suse.com> wrote: > On 09/24/2014 09:55 PM, Sergii Golovatiuk wrote: > > 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 > > Currently all bugs filed due to DocImpact land in the openstack-manuals > launchpad bug area unless the repository is setup in the infrastructure > to push them elsewhere. > > If you want to move forward with this, please setup first the > infrastructure to properly file the bugs, > > Andreas > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev