Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

Excerpts from Andreas Jaeger's message of 2017-06-28 08:45:47 +0200:
> For those migrating from oslosphinx to openstackdocstheme, I strongly
> advise to follow the docs for openstackdocstheme 1.11 on how to set it up:
> 
> https://docs.openstack.org/openstackdocstheme/latest/
> 
> Andreas

Another work item is moving the automatically generated class
documentation that pbr produces by setting the api_doc_dir value
in the pbr section of setup.cfg.

See https://docs.openstack.org/developer/pbr/user/using.html#pbr
for details and https://review.openstack.org/#/c/478294/2/setup.cfg
for an example.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

Excerpts from Alexandra Settle's message of 2017-06-23 12:09:41 +:
> Hi everyone,
> 
> This morning (afternoon) the specification for the documentation migration 
> was merged. Thanks to all that took time to review :)
> 
> You can now view here in all its glory: 
> https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
> 
> If you have any questions, feel free to shoot them to me or Doug :)
> 
> Let’s begin!
> 
> Alex

Based on some work Sean did with the nova API reference project, I've
set up a burndown chart to track our progress. It updates hourly.

https://doughellmann.com/doc-migration/

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Andreas Jaeger]

For those migrating from oslosphinx to openstackdocstheme, I strongly
advise to follow the docs for openstackdocstheme 1.11 on how to set it up:

https://docs.openstack.org/openstackdocstheme/latest/

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

Excerpts from Jeremy Stanley's message of 2017-06-27 17:55:57 +:
> On 2017-06-22 16:27:34 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > The new job is configured to update the docs for all repos every
> > time a patch is merged, not just when we tag releases. The server
> > projects have been working that way, but this is different for some
> > of the libraries, especially the clients.
> [...]
> 
> I think the past concern had been that since the default document
> presented was the latest one built from the master branch tip rather
> than a redirect to the documentation for the latest release, readers
> might get confused when seeing options or behaviors documented which
> didn't match the software they had downloaded.

That makes sense. The openstackdocstheme makes it easy to link to
specific versions of documentation, so we should be able to address this
concern that way. We will also have series-specific landing pages
linking directly to the appropriate guides.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Jeremy Stanley]

On 2017-06-22 16:27:34 -0400 (-0400), Doug Hellmann wrote:
[...]
> The new job is configured to update the docs for all repos every
> time a patch is merged, not just when we tag releases. The server
> projects have been working that way, but this is different for some
> of the libraries, especially the clients.
[...]

I think the past concern had been that since the default document
presented was the latest one built from the master branch tip rather
than a redirect to the documentation for the latest release, readers
might get confused when seeing options or behaviors documented which
didn't match the software they had downloaded.
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
> Hi everyone,
> 
> Doug and I have written up a spec following on from the conversation [0] that 
> we had regarding the documentation publishing future.
> 
> Please take the time out of your day to review the spec as this affects 
> *everyone*.
> 
> See: https://review.openstack.org/#/c/472275/
> 
> I will be PTO from the 9th – 19th of June. If you have any pressing concerns, 
> please email me and I will get back to you as soon as I can, or, email Doug 
> Hellmann and hopefully he will be able to assist you.
> 
> Thanks,
> 
> Alex
> 
> [0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html

Someone left a few questions about the directions on the tracking
etherpad [1]. I tried to answer them in place, but next time *please*
post to the mailing list. I have no idea how long those questions were
there before I noticed them, and given how little time we have to do the
work I want to make sure everyone understands as soon as possible.

Doug

[1] https://etherpad.openstack.org/p/doc-migration-tracking

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

> On Jun 23, 2017, at 12:10 PM, j.kl...@cloudbau.de wrote:
> 
> Hi Doug,
> 
> first of all sorry for the late response. I am the current PTL of the 
> openstack-chef project and read the spec a while ago, but did not really 
> connect it to our project. To be honest, i am not really sure what we would 
> move and how to do it. Currently we have some wiki pages, but most of them 
> are pretty old and completely outdated since we stopped caring for them after 
> we dropped to only a few contributors and moved our focus to maintaining the 
> project code itself.
> 
> Currently we own and maintain 12 service and ops cookbook repositories:
> 
> cookbook-openstack-block-storage
> cookbook-openstack-common
> cookbook-openstack-compute
> cookbook-openstack-dashboard
> cookbook-openstack-identity
> cookbook-openstack-image
> cookbook-openstack-integration-test
> cookbook-openstack-network
> cookbook-openstack-ops-database
> cookbook-openstack-ops-messaging
> cookbook-openstack-orchestration
> cookbook-openstack-telemetry
> 
> one (not very often used) specs repository:
> 
> openstack-chef-specs
> 
>  and one repo to integrate them all:
> 
> openstack-chef-repo
> 
> All of these repos have some READMEs that contain some of the documentation 
> needed to use these. The documentation on how to use the openstack-chef 
> project as a combination of all these cookbooks, is located under 
> https://github.com/openstack/openstack-chef-repo/tree/master/doc 
>  (which 
> might already be close to the right space ?). Looking through the 
> openstack-manuals repo, i did not find any documentation specific for our 
> projects, so i think we do not need to export/import any of it. In my opinion 
> the easiest way to follow the proposed change of us would be to just move the 
> stuff we have under the ‘openstack-chef-repo’ mentioned above and add some 
> more files to follow the ‘minimal layout’. If you agree on this, i can try to 
> push a patch for it next week and add you as a reviewer?

Yes, it sounds like you only need to move things you already have around into 
the new structure. You don’t need to create empty directories or pages for 
content that doesn’t apply, so if you don’t have any configuration guide 
instructions for example then you don’t need to create the configuration/ 
directory.

If you add me as a reviewer, I’ll help make sure you have it organized as 
expected. And if you use the doc-migration tag the other folks working on the 
migration will review the patch, too.

Doug

> 
> Cheers,
> Jan
> 
> 
> On 23. June 2017 at 16:16:58, Doug Hellmann (d...@doughellmann.com 
> ) wrote:
> 
>> 
>>> On Jun 23, 2017, at 8:57 AM, Renat Akhmerov >> > wrote:
>>> 
>>> I can say for Mistral . We only planned to add Mistral docs to the central 
>>> repo but didn’t do it yet. So, as far as I understand, we don’t need to 
>>> move anything. We’ll review the spec and adjust the folder structure 
>>> according to the proposed.
>> 
>> Please do review the steps in the spec. Not all of them are about moving 
>> content. There are steps for setting up the new build job so that the 
>> content will be published to the new URLs as well.
>> 
>> Doug
>> 
>>> 
>>> Thanks
>>> 
>>> Renat Akhmerov
>>> @Nokia
>>> 
>>> 23 июня 2017 г., 3:32 +0700, Doug Hellmann >> >, писал:
 Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
> Hi everyone,
> 
> Doug and I have written up a spec following on from the conversation [0] 
> that we had regarding the documentation publishing future.
> 
> Please take the time out of your day to review the spec as this affects 
> *everyone*.
> 
> See: https://review.openstack.org/#/c/472275/ 
> 
> 
> I will be PTO from the 9th – 19th of June. If you have any pressing 
> concerns, please email me and I will get back to you as soon as I can, 
> or, email Doug Hellmann and hopefully he will be able to assist you.
> 
> Thanks,
> 
> Alex
> 
> [0] 
> http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html 
> 
 
 Andreas pointed out that the new documentation job will behave a
 little differently from the old setup, and thought I should mention
 it so that people aren't surprised.
 
 The new job is configured to update the docs for all repos every
 time a patch is merged, not just when we tag releases. The server
 projects have been working that way, but this is different for some
 of the libraries, especially the clients.
 
 I will be going back and adding a step to build the docs when we
 tag releases after the move actually 

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[j.kl...@cloudbau.de]

Hi Doug,

first of all sorry for the late response. I am the current PTL of the 
openstack-chef project and read the spec a while ago, but did not really 
connect it to our project. To be honest, i am not really sure what we would 
move and how to do it. Currently we have some wiki pages, but most of them are 
pretty old and completely outdated since we stopped caring for them after we 
dropped to only a few contributors and moved our focus to maintaining the 
project code itself.

Currently we own and maintain 12 service and ops cookbook repositories:

cookbook-openstack-block-storage
cookbook-openstack-common
cookbook-openstack-compute
cookbook-openstack-dashboard
cookbook-openstack-identity
cookbook-openstack-image
cookbook-openstack-integration-test
cookbook-openstack-network
cookbook-openstack-ops-database
cookbook-openstack-ops-messaging
cookbook-openstack-orchestration
cookbook-openstack-telemetry

one (not very often used) specs repository:

openstack-chef-specs

 and one repo to integrate them all:

openstack-chef-repo

All of these repos have some READMEs that contain some of the documentation 
needed to use these. The documentation on how to use the openstack-chef project 
as a combination of all these cookbooks, is located under 
https://github.com/openstack/openstack-chef-repo/tree/master/doc (which might 
already be close to the right space ?). Looking through the openstack-manuals 
repo, i did not find any documentation specific for our projects, so i think we 
do not need to export/import any of it. In my opinion the easiest way to follow 
the proposed change of us would be to just move the stuff we have under the 
‘openstack-chef-repo’ mentioned above and add some more files to follow the 
‘minimal layout’. If you agree on this, i can try to push a patch for it next 
week and add you as a reviewer?

Cheers,
Jan


On 23. June 2017 at 16:16:58, Doug Hellmann (d...@doughellmann.com) wrote:


On Jun 23, 2017, at 8:57 AM, Renat Akhmerov  wrote:

I can say for Mistral . We only planned to add Mistral docs to the central repo 
but didn’t do it yet. So, as far as I understand, we don’t need to move 
anything. We’ll review the spec and adjust the folder structure according to 
the proposed.

Please do review the steps in the spec. Not all of them are about moving 
content. There are steps for setting up the new build job so that the content 
will be published to the new URLs as well.

Doug


Thanks

Renat Akhmerov
@Nokia

23 июня 2017 г., 3:32 +0700, Doug Hellmann , писал:
Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
Hi everyone,

Doug and I have written up a spec following on from the conversation [0] that 
we had regarding the documentation publishing future.

Please take the time out of your day to review the spec as this affects 
*everyone*.

See: https://review.openstack.org/#/c/472275/

I will be PTO from the 9th – 19th of June. If you have any pressing concerns, 
please email me and I will get back to you as soon as I can, or, email Doug 
Hellmann and hopefully he will be able to assist you.

Thanks,

Alex

[0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html

Andreas pointed out that the new documentation job will behave a
little differently from the old setup, and thought I should mention
it so that people aren't surprised.

The new job is configured to update the docs for all repos every
time a patch is merged, not just when we tag releases. The server
projects have been working that way, but this is different for some
of the libraries, especially the clients.

I will be going back and adding a step to build the docs when we
tag releases after the move actually starts, so that we can link
to docs for specific versions of projects. That change will be
transparent to everyone else, so I have it on the list for after
the migration is under way.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

> On Jun 23, 2017, at 8:57 AM, Renat Akhmerov  wrote:
> 
> I can say for Mistral . We only planned to add Mistral docs to the central 
> repo but didn’t do it yet. So, as far as I understand, we don’t need to move 
> anything. We’ll review the spec and adjust the folder structure according to 
> the proposed.

Please do review the steps in the spec. Not all of them are about moving 
content. There are steps for setting up the new build job so that the content 
will be published to the new URLs as well.

Doug

> 
> Thanks
> 
> Renat Akhmerov
> @Nokia
> 
> 23 июня 2017 г., 3:32 +0700, Doug Hellmann , писал:
>> Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
>>> Hi everyone,
>>> 
>>> Doug and I have written up a spec following on from the conversation [0] 
>>> that we had regarding the documentation publishing future.
>>> 
>>> Please take the time out of your day to review the spec as this affects 
>>> *everyone*.
>>> 
>>> See: https://review.openstack.org/#/c/472275/
>>> 
>>> I will be PTO from the 9th – 19th of June. If you have any pressing 
>>> concerns, please email me and I will get back to you as soon as I can, or, 
>>> email Doug Hellmann and hopefully he will be able to assist you.
>>> 
>>> Thanks,
>>> 
>>> Alex
>>> 
>>> [0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html
>> 
>> Andreas pointed out that the new documentation job will behave a
>> little differently from the old setup, and thought I should mention
>> it so that people aren't surprised.
>> 
>> The new job is configured to update the docs for all repos every
>> time a patch is merged, not just when we tag releases. The server
>> projects have been working that way, but this is different for some
>> of the libraries, especially the clients.
>> 
>> I will be going back and adding a step to build the docs when we
>> tag releases after the move actually starts, so that we can link
>> to docs for specific versions of projects. That change will be
>> transparent to everyone else, so I have it on the list for after
>> the migration is under way.
>> 
>> Doug
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Renat Akhmerov]

I can say for Mistral . We only planned to add Mistral docs to the central repo 
but didn’t do it yet. So, as far as I understand, we don’t need to move 
anything. We’ll review the spec and adjust the folder structure according to 
the proposed.

Thanks

Renat Akhmerov
@Nokia

23 июня 2017 г., 3:32 +0700, Doug Hellmann , писал:
> Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
> > Hi everyone,
> >
> > Doug and I have written up a spec following on from the conversation [0] 
> > that we had regarding the documentation publishing future.
> >
> > Please take the time out of your day to review the spec as this affects 
> > *everyone*.
> >
> > See: https://review.openstack.org/#/c/472275/
> >
> > I will be PTO from the 9th – 19th of June. If you have any pressing 
> > concerns, please email me and I will get back to you as soon as I can, or, 
> > email Doug Hellmann and hopefully he will be able to assist you.
> >
> > Thanks,
> >
> > Alex
> >
> > [0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html
>
> Andreas pointed out that the new documentation job will behave a
> little differently from the old setup, and thought I should mention
> it so that people aren't surprised.
>
> The new job is configured to update the docs for all repos every
> time a patch is merged, not just when we tag releases. The server
> projects have been working that way, but this is different for some
> of the libraries, especially the clients.
>
> I will be going back and adding a step to build the docs when we
> tag releases after the move actually starts, so that we can link
> to docs for specific versions of projects. That change will be
> transparent to everyone else, so I have it on the list for after
> the migration is under way.
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[Doug Hellmann]

Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
> Hi everyone,
> 
> Doug and I have written up a spec following on from the conversation [0] that 
> we had regarding the documentation publishing future.
> 
> Please take the time out of your day to review the spec as this affects 
> *everyone*.
> 
> See: https://review.openstack.org/#/c/472275/
> 
> I will be PTO from the 9th – 19th of June. If you have any pressing concerns, 
> please email me and I will get back to you as soon as I can, or, email Doug 
> Hellmann and hopefully he will be able to assist you.
> 
> Thanks,
> 
> Alex
> 
> [0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html

Andreas pointed out that the new documentation job will behave a
little differently from the old setup, and thought I should mention
it so that people aren't surprised.

The new job is configured to update the docs for all repos every
time a patch is merged, not just when we tag releases. The server
projects have been working that way, but this is different for some
of the libraries, especially the clients.

I will be going back and adding a step to build the docs when we
tag releases after the move actually starts, so that we can link
to docs for specific versions of projects. That change will be
transparent to everyone else, so I have it on the list for after
the migration is under way.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev