Open Stack

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 <aj at suse.com> 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`_
> <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 <doug at doughellmann.com
>> <mailto:doug at doughellmann.com>> 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 <doug at doughellmann.com
>>     <mailto:doug at doughellmann.com>>:
>>      > > We've made huge progress, and are launching the updated landing
>>      > > pages for docs.openstack.org <http://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/
>>     <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-docs at lists.openstack.org
>>     <mailto:OpenStack-docs at lists.openstack.org>
>>      > >
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>
>>      >
>>
>>     ____________________________________________________________
>> ______________
>>     OpenStack Development Mailing List (not for usage questions)
>>     Unsubscribe:
>>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
>> >
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>     <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>
>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170723/48e2251e/attachment.html>