Re: [openstack-dev] [docs][neutron] doc-migration status

[Akihiro Motoki]

2017-07-24 23:44 GMT+09:00 Doug Hellmann :
> Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700:
>> Yeah, the networking guide does include configuration for some of the
>> sub-projects (e.g. BGP is at [1]). For the remaining ones there is work
>> that needs to be done because their docs live in wiki pages.
>>
>> 1.
>> https://docs.openstack.org/ocata/networking-guide/config-bgp-dynamic-routing.html
>
> OK, that's good to know. It would be good to be consistent with the
> approach to the stadium projects, so we can either eliminate the list of
> projects from landing pages that show things like "all of the admin
> guides" or we can add the projects so users can find the docs. If
> they're all covered in the networking guide, we could include that
> information on the admin landing page, for example.

Thanks for the advise.

Yeah, we need some consistency across the stadium projects.
The installation and/or config guide can be covered by the networking
guide (admin guide).
Regarding the configuration reference, I think it is better to have
them in individual projects
as they are generated automatically from the code.

The stadium projects are roughly categorized into two:
service project (like FWaaS, BGP, SFC...) and back-end project
(networking-ovn/odl/midonet...).
Around the service projects, the networking guide looks the best place
to cover various things.
A single place will help readers.
Regarding back-end projects, individual projects have their own
contents in their repository
and I am not sure which is better.
Anyway we can discuss and get consensus in the neutron team.

> In the mean time, if someone from the neutron project will review
> the list of "Missing URLs" on https://doughellmann.com/doc-migration/
> and let me know which ones represent content included in other
> documents, I can update the burndown chart generator to reflect
> that.

I am usually checking the doc-migration burndown chart including missing URLs
on the neutron stadium projects.
The progress is generally good and the remaining things are as follows:
- Configuration reference for all listed projects are under review
  (all have been proposed and I am taking care of them).
- The installation guide of networking-odl is also under review and I
believe will land soon.
All progresses are tracked on the doc-migration etherpad (neutron section).

Akihiro

>
> Doug
>
>>
>>
>> On Sun, Jul 23, 2017 at 1:32 PM, Doug Hellmann 
>> wrote:
>>
>> > Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700:
>> > > Yeah, I was just thinking it makes it more explicit that we haven't just
>> > > skipped doing an admin guide for a particular project.
>> >
>> > Sure, you can do that. I don't think we want to link to all of those
>> > pages from the list of admin guides, though.
>> >
>> > I've updated the burndown chart generator to ignore the missing
>> > admin guide URLs for networking subprojects.
>> >
>> > I don't see configuration or installation guides for quite a few
>> > of those, either. Are those also handled within the neutron main
>> > tree docs?
>> >
>> > 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] [docs][neutron] doc-migration status

[Doug Hellmann]

Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700:
> Yeah, the networking guide does include configuration for some of the
> sub-projects (e.g. BGP is at [1]). For the remaining ones there is work
> that needs to be done because their docs live in wiki pages.
> 
> 1.
> https://docs.openstack.org/ocata/networking-guide/config-bgp-dynamic-routing.html

OK, that's good to know. It would be good to be consistent with the
approach to the stadium projects, so we can either eliminate the list of
projects from landing pages that show things like "all of the admin
guides" or we can add the projects so users can find the docs. If
they're all covered in the networking guide, we could include that
information on the admin landing page, for example.

In the mean time, if someone from the neutron project will review
the list of "Missing URLs" on https://doughellmann.com/doc-migration/
and let me know which ones represent content included in other
documents, I can update the burndown chart generator to reflect
that.

Doug

> 
> 
> On Sun, Jul 23, 2017 at 1:32 PM, Doug Hellmann 
> wrote:
> 
> > Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700:
> > > Yeah, I was just thinking it makes it more explicit that we haven't just
> > > skipped doing an admin guide for a particular project.
> >
> > Sure, you can do that. I don't think we want to link to all of those
> > pages from the list of admin guides, though.
> >
> > I've updated the burndown chart generator to ignore the missing
> > admin guide URLs for networking subprojects.
> >
> > I don't see configuration or installation guides for quite a few
> > of those, either. Are those also handled within the neutron main
> > tree docs?
> >
> > 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] [docs][neutron] doc-migration status

[Kevin Benton]

Yeah, the networking guide does include configuration for some of the
sub-projects (e.g. BGP is at [1]). For the remaining ones there is work
that needs to be done because their docs live in wiki pages.

1.
https://docs.openstack.org/ocata/networking-guide/config-bgp-dynamic-routing.html


On Sun, Jul 23, 2017 at 1:32 PM, Doug Hellmann 
wrote:

> Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700:
> > Yeah, I was just thinking it makes it more explicit that we haven't just
> > skipped doing an admin guide for a particular project.
>
> Sure, you can do that. I don't think we want to link to all of those
> pages from the list of admin guides, though.
>
> I've updated the burndown chart generator to ignore the missing
> admin guide URLs for networking subprojects.
>
> I don't see configuration or installation guides for quite a few
> of those, either. Are those also handled within the neutron main
> tree docs?
>
> 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] [docs][neutron] doc-migration status

[Anne Gentle]

On Sat, Jul 22, 2017 at 12:13 PM, Akihiro Motoki  wrote:
> Hi,
>
> I have a question on admin/ document related to the networking guide
> and would like to have advices from the documentation experts.
>
> It seems the check site by Doug expect all project have admin/ page.
> In the case of neutron the situation is a bit special. We have the
> networking guide as admin/ document
> in the neutron repo and it covers not only neutron itself but also
> neutron stadium projects.
> It means the neutron stadium projects sometimes (often?) have no
> admin/ directory in their own repos
> in favor of adding contents to the networking guide in neutron.
>
> Should Individual neutron stadium projects have their own admin guide
> in their repositories,
> or is it better to keep the networking guide which covers all
> networking stuff in a single guide?

It's better to keep the networking guide as close to what it is now as
possible, based on the web stats and prior input on that guide's
popularity.

Could you list all the neutron stadium projects? That might help
answer the next question, because if they require neutron, it seems
like a single networking guide is a good way forward. If my memory
serves, it was vpnaas, fwaas, and lbaas, and a whole lot more.
Reviewing 
https://specs.openstack.org/openstack/neutron-specs/specs/newton/neutron-stadium.html
I see a lot more with varying amounts of docs. My general guideline at
first glance would be, if they require neutron, let's put them in the
networking guide in the neutron repo.

I may not say the same for storage, because that's a different set of
interdependencies and decisions for operators to make. I don't think
cinder ever had a stadium, for example. But, since the "neutron
stadium" was very contributor-specific, let's make sure we're meeting
consumer needs.

> What is the suggested way on the networking guide as the document expert?

Keep working with us with specific scenarios and details and we can
fill in a set of reader needs, hopefully.

Anne

>
> Thanks,
> Akihiro
>
> 2017-07-22 3:26 GMT+09:00 Doug Hellmann :
>> We've made huge progress, and are launching the updated landing
>> pages for docs.openstack.org as I write this. Thanks to all of the
>> contributors who have stepped up to write nearly 1,000 patches to
>> improve the health of our documentation!
>>
>> We still have around 70 URLs we expected to see after the migration
>> was complete but that produce a 404. I know some of the patches to
>> produce those pages are in progress, but please check the list at
>> https://doughellmann.com/doc-migration/ if your team is listed below
>> to ensure that nothing has been missed.
>>
>>   cinder
>>   cloudkitty
>>   congress
>>   designate
>>   heat
>>   ironic
>>   karbor
>>   keystone
>>   magnum
>>   manila
>>   murano
>>   neutron
>>   nova
>>   sahara
>>   senlin
>>   swift
>>   tacker
>>   telementry
>>   tricircle
>>   trove
>>   vitrage
>>   watcher
>>   zaqar
>>   zun
>>
>> Reply here or ping me in #openstack-docs if you have questions or need a
>> hand.
>>
>> Doug
>>
>> ___
>> OpenStack-docs mailing list
>> openstack-d...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
> __
> 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



-- 

Read my blog: justwrite.click
Subscribe to Docs|Code: docslikecode.com

__
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] [docs][neutron] doc-migration status

[Doug Hellmann]

Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700:
> Yeah, I was just thinking it makes it more explicit that we haven't just
> skipped doing an admin guide for a particular project.

Sure, you can do that. I don't think we want to link to all of those
pages from the list of admin guides, though.

I've updated the burndown chart generator to ignore the missing
admin guide URLs for networking subprojects.

I don't see configuration or installation guides for quite a few
of those, either. Are those also handled within the neutron main
tree docs?

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] [docs][neutron] doc-migration status

[Kevin Benton]

Yeah, I was just thinking it makes it more explicit that we haven't just
skipped doing an admin guide for a particular project.

On Sun, Jul 23, 2017 at 1:18 AM, Andreas Jaeger  wrote:

> On 07/22/2017 11:44 PM, Kevin Benton wrote:
>
>> Could we just put a placeholder in those subprojects /admin directories
>> that redirects to the networking guide?
>>
>
> You mean a single page that basically says :
>
> All information is covered in the `Networking Guide <
> https://docs.openstack.org/neutron/latest/admin/networking-guide`_
> .
>
> Yes, this could be done - do we really need this?
>
> Akihiro, having an admin/ directory is not a must-have,
>
> Andreas
>
> On Sat, Jul 22, 2017 at 10:50 AM, Doug Hellmann > > wrote:
>>
>> Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900:
>> > Hi,
>> >
>> > I have a question on admin/ document related to the networking guide
>> > and would like to have advices from the documentation experts.
>> >
>> > It seems the check site by Doug expect all project have admin/ page.
>> > In the case of neutron the situation is a bit special. We have the
>> > networking guide as admin/ document
>> > in the neutron repo and it covers not only neutron itself but also
>> > neutron stadium projects.
>> > It means the neutron stadium projects sometimes (often?) have no
>> > admin/ directory in their own repos
>> > in favor of adding contents to the networking guide in neutron.
>> >
>> > Should Individual neutron stadium projects have their own admin
>> guide
>> > in their repositories,
>> > or is it better to keep the networking guide which covers all
>> > networking stuff in a single guide?
>> >
>> > What is the suggested way on the networking guide as the document
>> expert?
>>
>> If the admin guides for all of those repos are combined, then I can
>> modify the burndown chart generator to not count those as needed. Let
>> me
>> know if that's the best approach.
>>
>> Doug
>>
>>  >
>>  > Thanks,
>>  > Akihiro
>>  >
>>  > 2017-07-22 3:26 GMT+09:00 Doug Hellmann > >:
>>  > > We've made huge progress, and are launching the updated landing
>>  > > pages for docs.openstack.org  as I
>>
>> write this. Thanks to all of the
>>  > > contributors who have stepped up to write nearly 1,000 patches to
>>  > > improve the health of our documentation!
>>  > >
>>  > > We still have around 70 URLs we expected to see after the
>> migration
>>  > > was complete but that produce a 404. I know some of the patches
>> to
>>  > > produce those pages are in progress, but please check the list at
>>  > > https://doughellmann.com/doc-migration/
>>  if your team is listed
>> below
>>  > > to ensure that nothing has been missed.
>>  > >
>>  > >   cinder
>>  > >   cloudkitty
>>  > >   congress
>>  > >   designate
>>  > >   heat
>>  > >   ironic
>>  > >   karbor
>>  > >   keystone
>>  > >   magnum
>>  > >   manila
>>  > >   murano
>>  > >   neutron
>>  > >   nova
>>  > >   sahara
>>  > >   senlin
>>  > >   swift
>>  > >   tacker
>>  > >   telementry
>>  > >   tricircle
>>  > >   trove
>>  > >   vitrage
>>  > >   watcher
>>  > >   zaqar
>>  > >   zun
>>  > >
>>  > > Reply here or ping me in #openstack-docs if you have questions
>> or need a
>>  > > hand.
>>  > >
>>  > > Doug
>>  > >
>>  > > ___
>>  > > OpenStack-docs mailing list
>>  > > openstack-d...@lists.openstack.org
>> 
>>  > >
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>> 
>>  >
>>
>> 
>> __
>> 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:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> --
>  Andreas Jaeger 

Re: [openstack-dev] [docs][neutron] doc-migration status

[Andreas Jaeger]

On 07/22/2017 11:44 PM, Kevin Benton wrote:
Could we just put a placeholder in those subprojects /admin directories 
that redirects to the networking guide?


You mean a single page that basically says :

All information is covered in the `Networking Guide 
> wrote:


Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900:
> Hi,
>
> I have a question on admin/ document related to the networking guide
> and would like to have advices from the documentation experts.
>
> It seems the check site by Doug expect all project have admin/ page.
> In the case of neutron the situation is a bit special. We have the
> networking guide as admin/ document
> in the neutron repo and it covers not only neutron itself but also
> neutron stadium projects.
> It means the neutron stadium projects sometimes (often?) have no
> admin/ directory in their own repos
> in favor of adding contents to the networking guide in neutron.
>
> Should Individual neutron stadium projects have their own admin guide
> in their repositories,
> or is it better to keep the networking guide which covers all
> networking stuff in a single guide?
>
> What is the suggested way on the networking guide as the document expert?

If the admin guides for all of those repos are combined, then I can
modify the burndown chart generator to not count those as needed. Let me
know if that's the best approach.

Doug

 >
 > Thanks,
 > Akihiro
 >
 > 2017-07-22 3:26 GMT+09:00 Doug Hellmann >:
 > > We've made huge progress, and are launching the updated landing
 > > pages for docs.openstack.org  as I
write this. Thanks to all of the
 > > contributors who have stepped up to write nearly 1,000 patches to
 > > improve the health of our documentation!
 > >
 > > We still have around 70 URLs we expected to see after the migration
 > > was complete but that produce a 404. I know some of the patches to
 > > produce those pages are in progress, but please check the list at
 > > https://doughellmann.com/doc-migration/
 if your team is listed below
 > > to ensure that nothing has been missed.
 > >
 > >   cinder
 > >   cloudkitty
 > >   congress
 > >   designate
 > >   heat
 > >   ironic
 > >   karbor
 > >   keystone
 > >   magnum
 > >   manila
 > >   murano
 > >   neutron
 > >   nova
 > >   sahara
 > >   senlin
 > >   swift
 > >   tacker
 > >   telementry
 > >   tricircle
 > >   trove
 > >   vitrage
 > >   watcher
 > >   zaqar
 > >   zun
 > >
 > > Reply here or ping me in #openstack-docs if you have questions
or need a
 > > hand.
 > >
 > > Doug
 > >
 > > ___
 > > OpenStack-docs mailing list
 > > openstack-d...@lists.openstack.org

 > >
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

 >

__
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




--
 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] [docs][neutron] doc-migration status

[Kevin Benton]

Could we just put a placeholder in those subprojects /admin directories
that redirects to the networking guide?

On Sat, Jul 22, 2017 at 10:50 AM, Doug Hellmann 
wrote:

> Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900:
> > Hi,
> >
> > I have a question on admin/ document related to the networking guide
> > and would like to have advices from the documentation experts.
> >
> > It seems the check site by Doug expect all project have admin/ page.
> > In the case of neutron the situation is a bit special. We have the
> > networking guide as admin/ document
> > in the neutron repo and it covers not only neutron itself but also
> > neutron stadium projects.
> > It means the neutron stadium projects sometimes (often?) have no
> > admin/ directory in their own repos
> > in favor of adding contents to the networking guide in neutron.
> >
> > Should Individual neutron stadium projects have their own admin guide
> > in their repositories,
> > or is it better to keep the networking guide which covers all
> > networking stuff in a single guide?
> >
> > What is the suggested way on the networking guide as the document expert?
>
> If the admin guides for all of those repos are combined, then I can
> modify the burndown chart generator to not count those as needed. Let me
> know if that's the best approach.
>
> Doug
>
> >
> > Thanks,
> > Akihiro
> >
> > 2017-07-22 3:26 GMT+09:00 Doug Hellmann :
> > > We've made huge progress, and are launching the updated landing
> > > pages for docs.openstack.org as I write this. Thanks to all of the
> > > contributors who have stepped up to write nearly 1,000 patches to
> > > improve the health of our documentation!
> > >
> > > We still have around 70 URLs we expected to see after the migration
> > > was complete but that produce a 404. I know some of the patches to
> > > produce those pages are in progress, but please check the list at
> > > https://doughellmann.com/doc-migration/ if your team is listed below
> > > to ensure that nothing has been missed.
> > >
> > >   cinder
> > >   cloudkitty
> > >   congress
> > >   designate
> > >   heat
> > >   ironic
> > >   karbor
> > >   keystone
> > >   magnum
> > >   manila
> > >   murano
> > >   neutron
> > >   nova
> > >   sahara
> > >   senlin
> > >   swift
> > >   tacker
> > >   telementry
> > >   tricircle
> > >   trove
> > >   vitrage
> > >   watcher
> > >   zaqar
> > >   zun
> > >
> > > Reply here or ping me in #openstack-docs if you have questions or need
> a
> > > hand.
> > >
> > > Doug
> > >
> > > ___
> > > OpenStack-docs mailing list
> > > openstack-d...@lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
>
> __
> 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] [docs][neutron] doc-migration status

[Doug Hellmann]

Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900:
> Hi,
> 
> I have a question on admin/ document related to the networking guide
> and would like to have advices from the documentation experts.
> 
> It seems the check site by Doug expect all project have admin/ page.
> In the case of neutron the situation is a bit special. We have the
> networking guide as admin/ document
> in the neutron repo and it covers not only neutron itself but also
> neutron stadium projects.
> It means the neutron stadium projects sometimes (often?) have no
> admin/ directory in their own repos
> in favor of adding contents to the networking guide in neutron.
> 
> Should Individual neutron stadium projects have their own admin guide
> in their repositories,
> or is it better to keep the networking guide which covers all
> networking stuff in a single guide?
> 
> What is the suggested way on the networking guide as the document expert?

If the admin guides for all of those repos are combined, then I can
modify the burndown chart generator to not count those as needed. Let me
know if that's the best approach.

Doug

> 
> Thanks,
> Akihiro
> 
> 2017-07-22 3:26 GMT+09:00 Doug Hellmann :
> > We've made huge progress, and are launching the updated landing
> > pages for docs.openstack.org as I write this. Thanks to all of the
> > contributors who have stepped up to write nearly 1,000 patches to
> > improve the health of our documentation!
> >
> > We still have around 70 URLs we expected to see after the migration
> > was complete but that produce a 404. I know some of the patches to
> > produce those pages are in progress, but please check the list at
> > https://doughellmann.com/doc-migration/ if your team is listed below
> > to ensure that nothing has been missed.
> >
> >   cinder
> >   cloudkitty
> >   congress
> >   designate
> >   heat
> >   ironic
> >   karbor
> >   keystone
> >   magnum
> >   manila
> >   murano
> >   neutron
> >   nova
> >   sahara
> >   senlin
> >   swift
> >   tacker
> >   telementry
> >   tricircle
> >   trove
> >   vitrage
> >   watcher
> >   zaqar
> >   zun
> >
> > Reply here or ping me in #openstack-docs if you have questions or need a
> > hand.
> >
> > Doug
> >
> > ___
> > OpenStack-docs mailing list
> > openstack-d...@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 

__
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] [docs][neutron] doc-migration status

[Akihiro Motoki]

Hi,

I have a question on admin/ document related to the networking guide
and would like to have advices from the documentation experts.

It seems the check site by Doug expect all project have admin/ page.
In the case of neutron the situation is a bit special. We have the
networking guide as admin/ document
in the neutron repo and it covers not only neutron itself but also
neutron stadium projects.
It means the neutron stadium projects sometimes (often?) have no
admin/ directory in their own repos
in favor of adding contents to the networking guide in neutron.

Should Individual neutron stadium projects have their own admin guide
in their repositories,
or is it better to keep the networking guide which covers all
networking stuff in a single guide?

What is the suggested way on the networking guide as the document expert?

Thanks,
Akihiro

2017-07-22 3:26 GMT+09:00 Doug Hellmann :
> We've made huge progress, and are launching the updated landing
> pages for docs.openstack.org as I write this. Thanks to all of the
> contributors who have stepped up to write nearly 1,000 patches to
> improve the health of our documentation!
>
> We still have around 70 URLs we expected to see after the migration
> was complete but that produce a 404. I know some of the patches to
> produce those pages are in progress, but please check the list at
> https://doughellmann.com/doc-migration/ if your team is listed below
> to ensure that nothing has been missed.
>
>   cinder
>   cloudkitty
>   congress
>   designate
>   heat
>   ironic
>   karbor
>   keystone
>   magnum
>   manila
>   murano
>   neutron
>   nova
>   sahara
>   senlin
>   swift
>   tacker
>   telementry
>   tricircle
>   trove
>   vitrage
>   watcher
>   zaqar
>   zun
>
> Reply here or ping me in #openstack-docs if you have questions or need a
> hand.
>
> Doug
>
> ___
> OpenStack-docs mailing list
> openstack-d...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

__
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