<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Do we need two books? </div>
<div><br>
</div>
<div>Can the reference tables be appendices in the Cloud Admin Guide, and rename that book "Cloud Admin Guide and Reference"?</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>
<div>
<div style="color: rgb(0, 0, 0); "><font class="Apple-style-span" color="rgb(0, 0, 0)" face="Apple Chancery"><i>Diane</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)"><i>----------------------------------------------</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)">Diane Fleming</font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Software Developer II - US</div>
</div>
diane.fleming@rackspace.com</div>
<div>Cell 512.323.6799</div>
<div>Office 512.874.1260<br>
<span class="Apple-style-span" style="font-family: Calibri, sans-serif; ">
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Skype drfleming0227</div>
<div style="color: rgb(0, 0, 0); ">Google-plus diane.fleming@gmail.com</div>
</div>
</span></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Nermina Miller <<a href="mailto:nerminamiller@gmail.com">nerminamiller@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, November 5, 2013 12:18 PM<br>
<span style="font-weight:bold">To: </span>Nicholas Chase <<a href="mailto:nchase@mirantis.com">nchase@mirantis.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-docs] What's Up Doc? Special Summit Edition Nov 5 2013<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">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</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Nov 5, 2013 at 1:10 PM, Nicholas Chase <span dir="ltr">
<<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
On 11/5/2013 12:37 PM, Anne Gentle wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
<br>
On Tue, Nov 5, 2013 at 10:02 AM, Nicholas Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a><br>
</div>
<div class="im"><mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>> wrote:<br>
<br>
Restructure:<br>
Despite the tradeoff that we have to re-communicate some more<br>
moves to<br>
all the teams, we want to trim the configuration reference down<br>
to just<br>
listings of options, no how-to or explanatory information. Move this<br>
type of info to the Cloud Admin Guide. Are we good with this<br>
plan for<br>
Icehouse?<br>
<br>
<br>
Are you suggesting that the Config References just lists parameters<br>
without any explanation of what they mean? I agree with eliminating<br>
conceptual or how-to information and moving it to cloud admin, but<br>
I'm against removing explanations of what the parameters mean/do.<br>
<br>
<br>
No, it'll be a book with just xi:includes of the current tables. What do<br>
you think?<br>
</div>
</blockquote>
<br>
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.
<div class="HOEnZb">
<div class="h5"><br>
<br>
---- Nick<br>
<br>
______________________________<u></u>_________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Thank you!
<div><br>
</div>
<div>Nermina Miller</div>
<div>Tech Writer and Editor</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>