> On Mar 25, 2016, at 06:10, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000: >> >> All docs need to be drafted somewhere. I don't care where that is, but make >> the suggestion of /developer because at least it's accessible there, and >> also because it's managed in the project's own repo. If you want to create a >> different place, or rename /developer to be more inclusive, I think that's a >> great idea. > > I think we'll want to add a new location, or publish to a similar > location to the existing install guide. I found, for example > http://docs.openstack.org/mitaka/install-guide-ubuntu/ > > If we take ironic as the example, and assume all OS-types would be > covered in one manual, we could make that: > > (1) http://docs.openstack.org/mitaka/ironic/install-guide/ > (2) http://docs.openstack.org/ironic/mitaka/install-guide/ > (3) http://docs.openstack.org/install-guide/ironic/ > (4) http://docs.openstack.org/ironic/install-guide/
I like option 3. All install guides would be discoverable at /install-guides that are rendered docs from individual projects' repos. Regardless of what direction people would like to go here, I will be happy to spearhead this from a cross-project perspective. -- Mike Perez __________________________________________________________________________ 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
