[Openstack-docs] What's Up Doc? Special Summit Edition Nov 5 2013
Diane Fleming
diane.fleming at RACKSPACE.COM
Tue Nov 5 18:22:10 UTC 2013
Do we need two books?
Can the reference tables be appendices in the Cloud Admin Guide, and rename that book "Cloud Admin Guide and Reference"?
I'm fine with it either way – though it might be nice to have everything in one place given the book isn't too big.
Diane
----------------------------------------------
Diane Fleming
Software Developer II - US
diane.fleming at rackspace.com
Cell 512.323.6799
Office 512.874.1260
Skype drfleming0227
Google-plus diane.fleming at gmail.com
From: Nermina Miller <nerminamiller at gmail.com<mailto:nerminamiller at gmail.com>>
Date: Tuesday, November 5, 2013 12:18 PM
To: Nicholas Chase <nchase at mirantis.com<mailto:nchase at mirantis.com>>
Cc: "openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>" <openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>>
Subject: Re: [Openstack-docs] What's Up Doc? Special Summit Edition Nov 5 2013
I just wonder what would happen if an install gal/guy needs to know how to configure something and it's in the Cloud Admin Guide instead of Config Ref. - Nermina
On Tue, Nov 5, 2013 at 1:10 PM, Nicholas Chase <nchase at mirantis.com<mailto:nchase at mirantis.com>> wrote:
On 11/5/2013 12:37 PM, Anne Gentle wrote:
On Tue, Nov 5, 2013 at 10:02 AM, Nicholas Chase <nchase at mirantis.com<mailto:nchase at mirantis.com>
<mailto:nchase at mirantis.com<mailto:nchase at mirantis.com>>> wrote:
Restructure:
Despite the tradeoff that we have to re-communicate some more
moves to
all the teams, we want to trim the configuration reference down
to just
listings of options, no how-to or explanatory information. Move this
type of info to the Cloud Admin Guide. Are we good with this
plan for
Icehouse?
Are you suggesting that the Config References just lists parameters
without any explanation of what they mean? I agree with eliminating
conceptual or how-to information and moving it to cloud admin, but
I'm against removing explanations of what the parameters mean/do.
No, it'll be a book with just xi:includes of the current tables. What do
you think?
That makes more sense, as long as it's convenient (read: reasonably intuitive) to find the additional information for those who will need it, regardless of their function.
---- Nick
_______________________________________________
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
--
Thank you!
Nermina Miller
Tech Writer and Editor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20131105/879d4af2/attachment.html>
More information about the Openstack-docs
mailing list