Open Stack

+1 to moving the ops-guide to openstack-manuals. 

Once this patch is merged, we should also comment in open ops-guide bugs and commits to make changes in this repo. 

    On Thursday, 28 April 2016, 15:41, Andreas Jaeger <aj at suse.com> wrote:
 

 On 04/28/2016 02:14 PM, Anne Gentle wrote:
>
>
> On Thu, Apr 28, 2016 at 2:04 PM, Andreas Jaeger <aj at suse.com
> <mailto:aj at suse.com>> wrote:
>
>    On 04/28/2016 12:05 PM, Lana Brindley wrote:
>
>        On 28/04/16 11:59, Anne Gentle wrote:
>
>
>
>            On Thu, Apr 28, 2016 at 11:54 AM, Christian Berendt
>            <christian at berendt.io <mailto:christian at berendt.io>
>            <mailto:christian at berendt.io <mailto:christian at berendt.io>>>
>            wrote:
>
>                  On 28 April 2016 at 11:51:16, Andreas Jaeger
>            (aj at suse.com <mailto:aj at suse.com> <mailto:aj at suse.com
>            <mailto:aj at suse.com>>(mailto:aj at suse.com
>            <mailto:aj at suse.com> <mailto:aj at suse.com
>            <mailto:aj at suse.com>>)) wrote:
>
>                  > Does anybody see problems with that? Otherwise let's
>            do that before we
>                  > tackle the rest of the RST conversion.
>
>                  Makes sense to me. What about the other guides?
>
>                  Should we discuss to move all guides (over the
>            migration to RST) into the openstack-manuals repository? I
>            do not know why we have decided in the past to create
>            separate repositories for some of the guides.
>
>
>            It was for enabling review teams who knew the content best.
>            This model still makes sense for security guide to me. I'm
>            fine with the Ops Guide going back into openstack-manuals
>            but do check with anyone who has +2 specifically on the
>            separate repo please.
>
>
>        Yeah, Security Guide needs to stay in its own repo because it
>        has different reviewing rules and needs to maintain its own core
>        team. I've got no problem with the others moving if it's
>        possible to do so, though.
>
>
>
>    So, only other repo to merge then would be api-site with:
>    * content for developer.openstack.org <http://developer.openstack.org>
>    * API guide
>    * first-app
>
>    We can do that if desired,
>
>
> No, let's leave it. It's a different set of contributors based on
> looking at last two releases.

Ok, let's do only operations-guide, here's a change:

  https://review.openstack.org/310896

I'll mark it as WIP to give some more time for discussion...

Once that's in, we can finish the RST conversion of the guide - and 
remove the content from operations-guide.

I suggest to make operations-guide repository as read-only after that, 
let's not merge anything to DocBook, let's finish ops-guide RST conversion,

Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
        HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


_______________________________________________
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/20160429/26839cba/attachment.html>