Open Stack

On Sun, May 18, 2014 at 8:00 AM, Matt Kassawara <mkassawara at gmail.com>wrote:

> I suppose we can use the "work items" section in the blueprint or note
> activities on the Wiki page.
>

If you're all willing to work this way, I think it helps us know the
"quality" of our docs set by tracking bugs as defect or inaccuracy rather
than reorg or gap-filling. What do you think? Is it work-able to track on
the wiki page?

Let's also talk about how we can make a roadmap-per-book workable while
still not causing duplication of effort. My original thinking is that you'd
update the roadmap with your patch, but now I realize 2 people could work
on a roadmap item at once without knowing the other is doing the same
thing. Thoughts?
Thanks,
Anne


>
> On Sun, May 18, 2014 at 3:51 AM, Christian Berendt <berendt at b1-systems.de>wrote:
>
>> On 05/18/2014 03:32 AM, Matt Kassawara wrote:
>> > The suggested changes currently live in an Etherpad.
>> >
>> > https://etherpad.openstack.org/p/installation-guide-audit
>>
>> Will there be bugs opened first for all the changes mentioned in the
>> Etherpad? I would like to take over some changes but I'm not sure who is
>> responsible for the several changes at the moment and if there is
>> somebody already assigned.
>>
>> Christian.
>>
>> --
>> Christian Berendt
>> Cloud Computing Solution Architect
>> Mail: berendt at b1-systems.de
>>
>> B1 Systems GmbH
>> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
> _______________________________________________
> 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/20140518/55e7850d/attachment.html>