How about top-level organization by project/service, each with consistent topics that pertain to installation, configuration, upgrades, development, API, etc? Projects can determine whether some or all of those topics reside in the openstack-manuals or project repository.
On Fri, Nov 18, 2016 at 12:27 PM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500: > > In the keystone docs we have notes about how to upgrade between releases > > [1], so does the nova team [2]. > > > > Is it time we create an official guides to [3] for this subject? > > > > [1] http://docs.openstack.org/developer/keystone/upgrading.html > > [2] http://docs.openstack.org/developer/nova/upgrade.html > > [3] http://docs.openstack.org/ > > Maybe, instead of creating a separate project-specific guide for > every topic (install, upgrade, config, API, etc.), it would make > sense to have developer, deployer, and user facing guides and create > separate chapters in each for topics relevant to the audiences? > > 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
