Open Stack

On 09/14/2014 08:16 PM, Anne Gentle wrote:
> 
> 
> On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <edgar.magana at workday.com
> <mailto:edgar.magana at workday.com>> wrote:
> 
>     Can you guys include me in any further discussions?
>     I want to help..
> 
>     Thanks,
> 
>     Edgar
> 
>     From: Adam Lawson <alawson at aqorn.com <mailto:alawson at aqorn.com>>
>     Date: Tuesday, August 26, 2014 at 11:48 AM
>     To: Anne Gentle <anne at openstack.org <mailto:anne at openstack.org>>
>     Cc: David Medberry <david.medberry at canonical.com
>     <mailto:david.medberry at canonical.com>>, Sriram Subramanian
>     <sriram at sriramhere.com <mailto:sriram at sriramhere.com>>,
>     "openstack-docs at lists.openstack.org
>     <mailto:openstack-docs at lists.openstack.org>"
>     <openstack-docs at lists.openstack.org
>     <mailto:openstack-docs at lists.openstack.org>>,
>     "openstack-operators at lists.openstack.org
>     <mailto:openstack-operators at lists.openstack.org>"
>     <openstack-operators at lists.openstack.org
>     <mailto:openstack-operators at lists.openstack.org>>
>     Subject: Re: [Openstack-operators] High Availability Guide team
> 
>     I'd be happy to participate as needed Anne.
> 
>     On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org
>     <mailto:anne at openstack.org>> wrote:
> 
>         Hi all, 
>         Cross-posting to -docs and -operators. 
> 
>         At the Ops mid-cycle meetup this week, Matt Griffin, David
>         Medberry, and Sriram Subramanian offered to start a review team
>         for the High Availability Guide. It needs some updates and it's
>         best if the review team works similar to the Security Guide --
>         subject matter experts working with core docs team members for
>         reviews. So I'm proposing we pull it into its own repo just like
>         the Security Guide. Any reasons not to? I think the next steps are:
> 
>         1. Propose a patch to openstack/governance to show the repo is
>         governed by the Docs program.
>         2. Propose a patch that sets up a separate review team starting
>         with Matt, David, and Sriram. We think Emilien would be
>         interested too, sound good? Any others? We can have members of
>         openstack-docs-core as well, similar to the Security Guide.
>         3. Propose a patch that gets that guide building separately in a
>         different repo.
>         4.  Start working on the four bugs already logged [1] and logged
>         more as needed.
> 
> 
> Hi all, 
> Sounds like we still need the tasks above to happen.
> 
> Sriram and Andreas, I've got a branch with the HA Guide separated out
> at https://github.com/annegentle/ha-guide -- can you take a look and see
> if we can use it for the starting point? If it's good-to-go, I can take
> tasks 1 and 3. (Sriram, I hope you didn't get too far with the separate
> repo, holler if you want to divvy up either of those.)

That is as simple import without all the history and seems to have one
level too much.

I propose to do use git filter-branch to keep the history intact,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: 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