openstack-doc-core team mailing list archive

[Lana Brindley <openstack@xxxxxxxxxxxxxxxx>]

Bogdan agrees that we can move the HA Guide into the repo. This means that Adam will need to go through the normal process for obtaining core.

L


-------- Forwarded Message --------
Subject: 	Re: HA Guide - future plans?
Date: 	Sat, 30 Apr 2016 07:02:05 +0000
From: 	bdobrelia@xxxxxxxxxxxx
To: 	Lana Brindley <openstack@xxxxxxxxxxxxxxxx>



Hi, Lana.
I see no reasons to keep HA guide as a separate repo with a separate core team. The guide seems alive as few contributors submit patches and improve its content. I believe they will keep doing that whatever repo contained the guide. And it's better off doing reviews with a non-obsolete core team 😊 Thus, a separate guide in Openstack manuals will be a better fit than user guides.

Regarding future plans, I hope we will create content for HA for Computes (lead by Adam Spiers) and user instances. May be we should dedicate space for DLM as well (Joshua Harlow leads that effort, AFAIK)

Regards,
Bogdan.


*Od:* Lana Brindley <mailto:openstack@xxxxxxxxxxxxxxxx>
*Wysłano:* ‎piątek‎, ‎29‎ ‎kwietnia‎ ‎2016 ‎23‎:‎03
*Do:* Bogdan Dobrelya <mailto:bdobrelia@xxxxxxxxxxxx>

Hi Bogdan,

The HA Guide has come up a few times at Summit this week, and I wanted to make contact with you directly to ensure you've had a chance to voice your opinion.

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). In your opinion, is there a good reason for us to keep it this way? And if not, would you prefer to keep it as a separate guide in the openstack-manuals repo (which also brings it under the purview of the openstack-manuals core team), or do you think it's better to review the content and add it to, say, user guides instead?

Interested to hear what you think.

Thanks,
Lana

-- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com

Attachment: signature.asc
Description: OpenPGP digital signature