<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>Hi all,</div>
<div><br>
</div>
<div>Ildiko, this sounds like a good plan – especially if moving the admin guide content into the developer repository is easier for the project teams to work with. </div>
<div><br>
</div>
<div>It seems like the next step since the user and admin guides were separated.</div>
<div><br>
</div>
<div>This is pre-empting the PTG discussion somewhat, however I’m ready to help create repositories and build environments with the project teams to migrate the admin guide content, if we decide to use a similar process to the install guides and deploy guide. </div>
<div><br>
</div>
<div>Also, with the original bug: <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1458820" style="font-family: Helvetica; font-size: 12px;">https://bugs.launchpad.net/openstack-manuals/+bug/1458820</a> after the PTG meetings, I could mark this as
closed, and we can move to a specification, and then blueprint to migrate admin guide content? </div>
<div><br>
</div>
<div>Those are my thoughts for now. Thanks for bringing the idea forward :).</div>
<div><br>
</div>
<div>
<div>
<div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Best Regards,</font></font></div>
<div> </div>
<div>Joe Robinson</div>
<div>Information Developer II</div>
<div> -------------------------------</div>
<div>Joseph.Robinson@Rackspace.com</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>Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, 2 February 2017 at 1:06 AM<br>
<span style="font-weight:bold">To: </span>Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com">ildiko.vancsa@gmail.com</a>>, Lana Brindley <<a href="mailto:openstack@lanabrindley.com">openstack@lanabrindley.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] Admin Guide enhancements<br>
</div>
<div><br>
</div>
<div xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks Ildiko
</span><span style="font-size:11.0pt;font-family:Wingdings">J</span><span style="font-size:11.0pt;font-family:Calibri"> looking forward to discussing this with you at the PTG!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com">ildiko.vancsa@gmail.com</a>><br>
<b>Date: </b>Tuesday, January 31, 2017 at 5:43 PM<br>
<b>To: </b>Lana Brindley <<a href="mailto:openstack@lanabrindley.com">openstack@lanabrindley.com</a>><br>
<b>Cc: </b>"<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>
<b>Subject: </b>Re: [OpenStack-docs] Admin Guide enhancements<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">Hi Lana, <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Thank you, it all sounds great!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I added the topic to the PTG etherpad and linked in the mail thread fro the archive.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Ildikó<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:.5in">On 2017. Jan 29., at 16:23, Lana Brindley <<a href="mailto:openstack@lanabrindley.com">openstack@lanabrindley.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica">Hi Ildikó,<br>
<br>
Comments inline ...<br>
<br>
On 27/01/17 20:12, Ildiko Vancsa wrote:<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica">Hi Docs Team,<br>
<br>
TL;DR I have an old bug report for the Admin Guide which targeted the way how it is versioned, or maybe rather not versioned and which also implied other actions on that document, for which we weren’t ready at the time of reporting the issue.<br>
<br>
The bug report is the following: <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1458820">
https://bugs.launchpad.net/openstack-manuals/+bug/1458820</a><br>
<br>
The bug report itself highlights that it is hard both from usage and from maintenance perspective to handle a document which contains information about at least three OpenStack releases in an iterative way. When someone tries to figure out what belongs to one
single OpenStack release in it they need to put it together from an original state and the changes since that. In case of Telemetry we had issues with listing the collected meters in a user friendly way for instance.<br>
<br>
Another big issue with the Admin Guide is the maintenance, which is tough with having the source files in a separate, centralized repository far away from the code where the changes happen. This way core reviewers have a hard time to keep the document in sync
with the code as they cannot effectively -1 a code change as it *cannot* contain the doc changes.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica"><br>
I agree, it gets messy.<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica"><br>
The reason I bring this up now again as I see the experiment with moving the Install Guide chapters to the project repositories a successful initiative, I remember seeing positive feedbacks about that move on the ML, etc. I think someone brought even up the
Admin Guide as next candidate to a similar move.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica"><br>
We implemented the Deployment Guides in Ocata, and if we go by requests alone, then the Admin Guide is the next on the list.<br>
<br style="font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica"><br>
I would like to ask the Docs Team for their opinions about this topic. I see a lot of advantage in having the documentation living together with the code and also having version controlled together with the code. This would also remove some of the burden from
the Docs team as well, which I see a beneficial change too.<br>
<br>
What is your view about this? Could this be a good topic for the upcoming PTG too maybe?<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:9.0pt;font-family:Helvetica"><br>
I think it's sensible to consider, at the very least. Can you add it to the PTG etherpad for discussion?<br>
<br>
Lana<br>
<br>
--<span class="apple-converted-space"> </span><br>
Lana Brindley<br>
Technical Writer<br>
Rackspace Cloud Builders Australia<br>
</span><a href="http://lanabrindley.com/"><span style="font-size:9.0pt;font-family:Helvetica">http://lanabrindley.com</span></a><span style="font-size:9.0pt;font-family:Helvetica"><br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
</span><a href="mailto:OpenStack-docs@lists.openstack.org"><span style="font-size:9.0pt;font-family:Helvetica">OpenStack-docs@lists.openstack.org</span></a><span style="font-size:9.0pt;font-family:Helvetica"><br>
</span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"><span style="font-size:9.0pt;font-family:Helvetica">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</span>
<hr>
Rackspace Hosting Australia PTY LTD a company registered in the state of Victoria, Australia (company registered number ACN 153 275 524) whose registered office is at Level 1, 37 Pitt Street, Sydney, NSW 2000, Australia. Rackspace Hosting Australia PTY LTD
privacy policy can be viewed at www.rackspace.com.au/company/legal-privacy-statement.php - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material
is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.
</body>
</html>