Open Stack

I agree, centralize the content, it's part of deploying and operating an
openstack environment and it makes sense to have it integrated rather than
separate.

On Mon, May 2, 2016 at 5:29 PM, Matt Kassawara <mkassawara at gmail.com> wrote:

> Fewer places to put content = easier to contribute and reference.
>
> On Mon, May 2, 2016 at 4:52 PM, Lana Brindley <openstack at lanabrindley.com>
> wrote:
>
>> Hi everyone,
>>
>> One of the tasks for this release is to bring the Ops Guide back into the
>> openstack-manuals repo, and this prompted a discussion about bringing the
>> HA Guide back into our repo as well. We also discussed the possibility of
>> perhaps just merging the contents of the HA Guide into other docs instead
>> of keeping it as a separate book.
>>
>> Right now, the HA Guide is not only in its own repo but also has its own
>> core team (which appears quite outdated, actually). From conversations
>> among the HA Guide and core teams, it seems the best thing to do is bring
>> it back into the openstack-manuals repo (which also brings it under the
>> purview of the openstack-manuals core team), but keep it as a separate
>> book, at least for now.
>>
>> What do people think?
>>
>> Lana
>>
>> --
>> Lana Brindley
>> Technical Writer
>> Rackspace Cloud Builders Australia
>> http://lanabrindley.com
>>
>>
>> _______________________________________________
>> 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/20160503/321bd130/attachment-0001.html>