<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Joseph,<div class=""><br class=""></div><div class="">Thanks for the feedback and ideas. I added further comments in line below.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Ildikó</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 2017. Feb 2., at 21:51, Joseph Robinson <<a href="mailto:joseph.robinson@RACKSPACE.COM" class="">joseph.robinson@RACKSPACE.COM</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Hi all,</div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">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 style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">It seems like the next step since the user and admin guides were separated.</div></div></blockquote><div><br class=""></div><div>+1</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">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></blockquote><div><br class=""></div><div>Do we have projects where they store the docs in separate repo from the code or it’s usually in-tree?</div><div><br class=""></div><div>I’m happy to start discussions/activities even before the PTG if we can, I think that should help with having a good progress with this in Pike.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Also, with the original bug: <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1458820" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px;" class="">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></blockquote><div><br class=""></div><div>I think it is a great plan. It’s better to track the activities in a blueprint once we agreed on the direction and the next steps.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Those are my thoughts for now. Thanks for bringing the idea forward :).</div></div></blockquote><div><br class=""></div>Thank you for your support. :)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><div class=""><div class=""><font class="Apple-style-span"><font class="Apple-style-span" face="Calibri">Best Regards,</font></font></div><div class=""> </div><div class="">Joe Robinson</div><div class="">Information Developer II</div><div class=""> -------------------------------</div><div class=""><a href="mailto:Joseph.Robinson@Rackspace.com" style="color: purple; text-decoration: underline;" class="">Joseph.Robinson@Rackspace.com</a></div></div></div></div><div style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=""><span style="font-weight: bold;" class="">From:<span class="Apple-converted-space"> </span></span>Alexandra Settle <<a href="mailto:a.settle@outlook.com" style="color: purple; text-decoration: underline;" class="">a.settle@outlook.com</a>><br class=""><span style="font-weight: bold;" class="">Date:<span class="Apple-converted-space"> </span></span>Thursday, 2 February 2017 at 1:06 AM<br class=""><span style="font-weight: bold;" class="">To:<span class="Apple-converted-space"> </span></span>Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com" style="color: purple; text-decoration: underline;" class="">ildiko.vancsa@gmail.com</a>>, Lana Brindley <<a href="mailto:openstack@lanabrindley.com" style="color: purple; text-decoration: underline;" class="">openstack@lanabrindley.com</a>><br class=""><span style="font-weight: bold;" class="">Cc:<span class="Apple-converted-space"> </span></span>"<a href="mailto:openstack-docs@lists.openstack.org" style="color: purple; text-decoration: underline;" class="">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org" style="color: purple; text-decoration: underline;" class="">openstack-docs@lists.openstack.org</a>><br class=""><span style="font-weight: bold;" class="">Subject:<span class="Apple-converted-space"> </span></span>Re: [OpenStack-docs] Admin Guide enhancements<br class=""></div><div class=""><br class=""></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" class=""><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class=""><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 11pt; font-family: Calibri;" class="">Thanks Ildiko<span class="Apple-converted-space"> </span></span><span style="font-size: 11pt; font-family: Wingdings;" class="">J</span><span style="font-size: 11pt; font-family: Calibri;" class=""><span class="Apple-converted-space"> </span>looking forward to discussing this with you at the PTG!<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 11pt; font-family: Calibri;" class=""><o:p class=""> </o:p></span></div><div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><b class=""><span style="font-family: Calibri;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-family: Calibri;" class="">Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com" style="color: purple; text-decoration: underline;" class="">ildiko.vancsa@gmail.com</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Tuesday, January 31, 2017 at 5:43 PM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>Lana Brindley <<a href="mailto:openstack@lanabrindley.com" style="color: purple; text-decoration: underline;" class="">openstack@lanabrindley.com</a>><br class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b>"<a href="mailto:openstack-docs@lists.openstack.org" style="color: purple; text-decoration: underline;" class="">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org" style="color: purple; text-decoration: underline;" class="">openstack-docs@lists.openstack.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>Re: [OpenStack-docs] Admin Guide enhancements<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">Hi Lana,<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">Thank you, it all sounds great!<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">I added the topic to the PTG etherpad and linked in the mail thread fro the archive.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">Thanks,<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">Ildikó<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div><div class=""><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class="">On 2017. Jan 29., at 16:23, Lana Brindley <<a href="mailto:openstack@lanabrindley.com" style="color: purple; text-decoration: underline;" class="">openstack@lanabrindley.com</a>> wrote:<o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">Hi Ildikó,<br class=""><br class="">Comments inline ...<br class=""><br class="">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;" class=""><br class=""></span><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">Hi Docs Team,<br class=""><br class="">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 class=""><br class="">The bug report is the following:<span class="Apple-converted-space"> </span><a href="https://bugs.launchpad.net/openstack-manuals/+bug/1458820" style="color: purple; text-decoration: underline;" class="">https://bugs.launchpad.net/openstack-manuals/+bug/1458820</a><br class=""><br class="">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 class=""><br class="">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 class=""></o:p></span></div></blockquote><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class="">I agree, it gets messy.<br class=""><br style="font-variant-caps: normal; orphans: auto; text-align: start; widows: auto; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class=""><br class=""></span><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class="">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 class=""></o:p></span></div></blockquote><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class="">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 class=""><br style="font-variant-caps: normal; orphans: auto; text-align: start; widows: auto; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class=""><br class=""></span><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class="">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 class=""><br class="">What is your view about this? Could this be a good topic for the upcoming PTG too maybe?<o:p class=""></o:p></span></div></blockquote><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class="">I think it's sensible to consider, at the very least. Can you add it to the PTG etherpad for discussion?<br class=""><br class="">Lana<br class=""><br class="">--<span class="apple-converted-space"> </span><br class="">Lana Brindley<br class="">Technical Writer<br class="">Rackspace Cloud Builders Australia<br class=""></span><a href="http://lanabrindley.com/" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">http://lanabrindley.com</span></a><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class=""><br class="">_______________________________________________<br class="">OpenStack-docs mailing list<br class=""></span><a href="mailto:OpenStack-docs@lists.openstack.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">OpenStack-docs@lists.openstack.org</span></a><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class=""></span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</span></a><o:p class=""></o:p></div></div></blockquote></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman';" class=""><o:p class=""> </o:p></div></div></div></div></div></span><span style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""> </span><hr style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">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<span class="Apple-converted-space"> </span></span><a href="http://www.rackspace.com.au/company/legal-privacy-statement.php" style="color: purple; text-decoration: underline; font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">www.rackspace.com.au/company/legal-privacy-statement.php</a><span style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><span class="Apple-converted-space"> </span>- 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<span class="Apple-converted-space"> </span></span><a href="mailto:abuse@rackspace.com" style="color: purple; text-decoration: underline; font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">abuse@rackspace.com</a><span style="font-family: Calibri, sans-serif; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><span class="Apple-converted-space"> </span>and delete the original message. Your cooperation is appreciated.</span></div></blockquote></div><br class=""></div></body></html>