Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-31 Thread Michael Johnson
stack.org> Subject: [openstack-dev] [doc][ptls][all] Documentation publishing future Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since o

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-26 Thread John Garbutt
On Mon, 22 May 2017 at 10:43, Alexandra Settle wrote: > We could also view option 1 as the longer-term goal, > and option 2 as an incremental step toward it +1 doing option 2 then option 1. It just seems a good way to split up the work. Thanks, johnthetubaguy

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Tom Fifield
On 廿十七年五月廿四日 朝 09:38, Rochelle Grober wrote: From: Ildiko > On 2017. May 23., at 15:43, Sean McGinnis wrote: On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote: On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis wrote: [snip] Hey

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Rochelle Grober
From: Ildiko > On 2017. May 23., at 15:43, Sean McGinnis > wrote: > > > > On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote: > >> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis > >> > >> wrote: > >> > >>> > >>> [snip] > >>> > >> > >> Hey

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Lance Bragstad
I'm in favor of option #1. I think it encourages our developers to become better writers with guidance from the docs team. While ensuring docs are proposed prior to merging the implementation cross-repository is totally possible, I think #1 makes that flow easier. Thanks for putting together the

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Ildiko Vancsa
Hi Alex, First of all thank you for writing this up the summary and list options with their expected impacts. > > 1. We could combine all of the documentation builds, so that each project has > a single doc/source directory that includes developer, contributor, and user > documentation. This

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Ildiko Vancsa
> On 2017. May 23., at 15:43, Sean McGinnis wrote: > > On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote: >> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis >> wrote: >> >>> >>> [snip] >>> >> >> Hey Sean, is the "right to merge" the

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Anne Gentle
On Tue, May 23, 2017 at 8:56 AM, Zane Bitter wrote: > On 22/05/17 05:39, Alexandra Settle wrote: > >> 1. We could combine all of the documentation builds, so that each >> project has a single doc/source directory that includes developer, >> contributor, and user

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Zane Bitter
On 23/05/17 08:35, Alexandra Settle wrote: So, I’ve been a docs core for the OpenStack-Ansible project for some time now and this works really well within our structure. I do not merge anything unless it has a dev +2 before I come along (unless it is a trivial doc-only spelling/grammar

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Zane Bitter
On 22/05/17 05:39, Alexandra Settle wrote: 1. We could combine all of the documentation builds, so that each project has a single doc/source directory that includes developer, contributor, and user documentation. This option would reduce the number of build jobs we have to run, and cut down on

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Sean McGinnis
On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote: > On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis > wrote: > > > > > [snip] > > > > Hey Sean, is the "right to merge" the top difficulty you envision with 1 or > 2? Or is it finding people to do the writing and

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Alexandra Settle
> I prefer option 1, which should be obvious from Anne's reference to my exiting work to enable that. Option 2 seems yucky (to me) because it adds yet another docs tree and sphinx config to projects, and thus is counter to my hope that we'll have one single docs tree per repo. >

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Bogdan Dobrelya
On 23.05.2017 2:20, John Dickinson wrote: > > > On 22 May 2017, at 15:50, Anne Gentle wrote: > >> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis >> wrote: >> >>> On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: >>> >>> [snip] >>> 1. We could combine

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread John Dickinson
On 22 May 2017, at 15:50, Anne Gentle wrote: > On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis > wrote: > >> On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: >> >> [snip] >> >>> 1. We could combine all of the documentation builds, so that each >> project

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Anne Gentle
On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis wrote: > On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: > > [snip] > > > 1. We could combine all of the documentation builds, so that each > project has a single doc/source directory that includes developer,

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Sean McGinnis
On Mon, May 22, 2017 at 09:39:09AM +, Alexandra Settle wrote: [snip] > 1. We could combine all of the documentation builds, so that each project has > a single doc/source directory that includes developer, contributor, and user > documentation. This option would reduce the number of build

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Doug Hellmann
Excerpts from Anne Gentle's message of 2017-05-22 12:36:29 -0500: > > On May 22, 2017, at 9:09 AM, Doug Hellmann wrote: > > > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >>> On 05/22/2017 11:39 AM, Alexandra Settle wrote: > >>> Hi everyone, >

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Doug Hellmann
Excerpts from Michał Jastrzębski's message of 2017-05-22 10:42:44 -0700: > [snip] > > So from Kolla perspective, since our dev guide is really also > operators guide (we are operators tool so we're kinda "special" on > that front), we'd love to handle both deployment guide, user manuals > and all

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Michał Jastrzębski
[snip] So from Kolla perspective, since our dev guide is really also operators guide (we are operators tool so we're kinda "special" on that front), we'd love to handle both deployment guide, user manuals and all that in our tree. If we could create infrastructure that would allow us to segregate

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Anne Gentle
> On May 22, 2017, at 9:09 AM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: >>> On 05/22/2017 11:39 AM, Alexandra Settle wrote: >>> Hi everyone, >>> >>> The documentation team are rapidly losing key contributors and core >>>

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Doug Hellmann
Excerpts from Dmitry Tantsur's message of 2017-05-22 16:54:30 +0200: > On 05/22/2017 04:09 PM, Doug Hellmann wrote: > > Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > >> On 05/22/2017 11:39 AM, Alexandra Settle wrote: > >>> Hi everyone, > >>> > >>> The documentation team

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Dmitry Tantsur
On 05/22/2017 04:09 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: On 05/22/2017 11:39 AM, Alexandra Settle wrote: Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Doug Hellmann
Excerpts from Anne Gentle's message of 2017-05-22 08:08:40 -0500: > On Mon, May 22, 2017 at 4:39 AM, Alexandra Settle > wrote: > > > Hi everyone, > > > > > > > > The documentation team are rapidly losing key contributors and core > > reviewers. We are not alone, this is

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Doug Hellmann
Excerpts from Dmitry Tantsur's message of 2017-05-22 12:26:25 +0200: > On 05/22/2017 11:39 AM, Alexandra Settle wrote: > > Hi everyone, > > > > The documentation team are rapidly losing key contributors and core > > reviewers. > > We are not alone, this is happening across the board. It is

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Anne Gentle
On Mon, May 22, 2017 at 4:39 AM, Alexandra Settle wrote: > Hi everyone, > > > > The documentation team are rapidly losing key contributors and core > reviewers. We are not alone, this is happening across the board. It is > making things harder, but not impossible. > > Since

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Dmitry Tantsur
On 05/22/2017 11:39 AM, Alexandra Settle wrote: Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing

[openstack-dev] [doc][ptls][all] Documentation publishing future

2017-05-22 Thread Alexandra Settle
Hi everyone, The documentation team are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing higher and higher trying to achieve the best