<html 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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",serif;}
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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Ohhhh I like your thinking – I’m a pandoc fan, so, I’d be interested in moving this along using any tools to make it easier.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I think my only proviso (now I’m thinking about it more) is that we still have a link on docs.o.o, but it goes to the wiki page for the Ops Guide.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black">Anne Gentle <annegentle@justwriteclick.com><br>
<b>Date: </b>Friday, June 2, 2017 at 1:53 PM<br>
<b>To: </b>Alexandra Settle <a.settle@outlook.com><br>
<b>Cc: </b>Blair Bethwaite <blair.bethwaite@gmail.com>, OpenStack Operators <openstack-operators@lists.openstack.org>, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>, "openstack-docs@lists.openstack.org" <openstack-docs@lists.openstack.org><br>
<b>Subject: </b>Re: [Openstack-operators] [dev] [doc] Operations Guide future<o:p></o:p></span></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'm okay with option 3. <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">Since we hadn't heard from anyone yet who can do the work, I thought I'd describe a super small experiment to try. If you're interested in the export, run an experiment with Pandoc to convert from RST to Mediawiki. <a href="http://pandoc.org/demos.html">http://pandoc.org/demos.html</a>
<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">You'll likely still have cleanup but it's a start. Only convert troubleshooting to start, which gets the most hits:
<a href="http://docs.openstack.org/">docs.openstack.org/</a><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black">ops-guide/ops-network-troubleshooting.html</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Then see how much you get from Pandoc.<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">Let us know how it goes, I'm curious!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Anne<o:p></o:p></p>
</div>
<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>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Fri, Jun 2, 2017 at 4:03 AM, Alexandra Settle <<a href="mailto:a.settle@outlook.com" target="_blank">a.settle@outlook.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-left:.5in">Blair – correct, it was the majority in the room. I just wanted to reach out and ensure that operators had a chance to voice opinions and see where we were going (<br>
<br>
Sounds like option 3 is still the favorable direction. This is going to be a really big exercise, lifting the content out of the repos. Are people able to help?<br>
<br>
Thanks everyone for getting on board (<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><br>
On 6/2/17, 2:44 AM, "Blair Bethwaite" <<a href="mailto:blair.bethwaite@gmail.com">blair.bethwaite@gmail.com</a>> wrote:<br>
<br>
Hi Alex,<br>
<br>
Likewise for option 3. If I recall correctly from the summit session<br>
that was also the main preference in the room?<br>
<br>
On 2 June 2017 at 11:15, George Mihaiescu <<a href="mailto:lmihaiescu@gmail.com">lmihaiescu@gmail.com</a>> wrote:<br>
> +1 for option 3<br>
><br>
><br>
><br>
> On Jun 1, 2017, at 11:06, Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>> wrote:<br>
><br>
> Hi everyone,<br>
><br>
><br>
><br>
> I haven’t had any feedback regarding moving the Operations Guide to the<br>
> OpenStack wiki. I’m not taking silence as compliance. I would really like to<br>
> hear people’s opinions on this matter.<br>
><br>
><br>
><br>
> To recap:<br>
><br>
><br>
><br>
> Option one: Kill the Operations Guide completely and move the Administration<br>
> Guide to project repos.<br>
> Option two: Combine the Operations and Administration Guides (and then this<br>
> will be moved into the project-specific repos)<br>
> Option three: Move Operations Guide to OpenStack wiki (for ease of<br>
> operator-specific maintainability) and move the Administration Guide to<br>
> project repos.<br>
><br>
><br>
><br>
> Personally, I think that option 3 is more realistic. The idea for the last<br>
> option is that operators are maintaining operator-specific documentation and<br>
> updating it as they go along and we’re not losing anything by combining or<br>
> deleting. I don’t want to lose what we have by going with option 1, and I<br>
> think option 2 is just a workaround without fixing the problem – we are not<br>
> getting contributions to the project.<br>
><br>
><br>
><br>
> Thoughts?<br>
><br>
><br>
><br>
> Alex<br>
><br>
><br>
><br>
> From: Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>><br>
> Date: Friday, May 19, 2017 at 1:38 PM<br>
> To: Melvin Hillsman <<a href="mailto:mrhillsman@gmail.com">mrhillsman@gmail.com</a>>, OpenStack Operators<br>
> <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
> Subject: Re: [Openstack-operators] Fwd: [openstack-dev] [openstack-doc]<br>
> [dev] What's up doc? Summit recap edition<br>
><br>
><br>
><br>
> Hi everyone,<br>
><br>
><br>
><br>
> Adding to this, I would like to draw your attention to the last dot point of<br>
> my email:<br>
><br>
><br>
><br>
> “One of the key takeaways from the summit was the session that I joint<br>
> moderated with Melvin Hillsman regarding the Operations and Administration<br>
> Guides. You can find the etherpad with notes here:<br>
> <a href="https://etherpad.openstack.org/p/admin-ops-guides" target="_blank">
https://etherpad.openstack.org/p/admin-ops-guides</a> The session was really<br>
> helpful – we were able to discuss with the operators present the current<br>
> situation of the documentation team, and how they could help us maintain the<br>
> two guides, aimed at the same audience. The operator’s present at the<br>
> session agreed that the Administration Guide was important, and could be<br>
> maintained upstream. However, they voted and agreed that the best course of<br>
> action for the Operations Guide was for it to be pulled down and put into a<br>
> wiki that the operators could manage themselves. We will be looking at<br>
> actioning this item as soon as possible.”<br>
><br>
><br>
><br>
> I would like to go ahead with this, but I would appreciate feedback from<br>
> operators who were not able to attend the summit. In the etherpad you will<br>
> see the three options that the operators in the room recommended as being<br>
> viable, and the voted option being moving the Operations Guide out of<br>
> <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> into a wiki. The aim of this was to empower the<br>
> operations community to take more control of the updates in an environment<br>
> they are more familiar with (and available to others).<br>
><br>
><br>
><br>
> What does everyone think of the proposed options? Questions? Other thoughts?<br>
><br>
><br>
><br>
> Alex<br>
><br>
><br>
><br>
> From: Melvin Hillsman <<a href="mailto:mrhillsman@gmail.com">mrhillsman@gmail.com</a>><br>
> Date: Friday, May 19, 2017 at 1:30 PM<br>
> To: OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
> Subject: [Openstack-operators] Fwd: [openstack-dev] [openstack-doc] [dev]<br>
> What's up doc? Summit recap edition<br>
><br>
><br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>><br>
> Date: Fri, May 19, 2017 at 6:12 AM<br>
> Subject: [openstack-dev] [openstack-doc] [dev] What's up doc? Summit recap<br>
> edition<br>
> To: "<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>"<br>
> <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>><br>
> Cc: "OpenStack Development Mailing List (not for usage questions)"<br>
> <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
><br>
><br>
> Hi everyone,<br>
><br>
><br>
> The OpenStack manuals project had a really productive week at the OpenStack<br>
> summit in Boston. You can find a list of all the etherpads and attendees<br>
> here: <a href="https://etherpad.openstack.org/p/docs-summit" target="_blank">
https://etherpad.openstack.org/p/docs-summit</a><br>
><br>
><br>
><br>
> As we all know, we are rapidly losing key contributors and core reviewers.<br>
> We are not alone, this is happening across the board. It is making things<br>
> harder, but not impossible. Since our inception in 2010, we’ve been climbing<br>
> higher and higher trying to achieve the best documentation we could, and<br>
> uphold our high standards. This is something to be incredibly proud of.<br>
> However, we now need to take a step back and realise that the amount of work<br>
> we are attempting to maintain is now out of reach for the team size that we<br>
> have. At the moment we have 13 cores, of which none are full time<br>
> contributors or reviewers. This includes myself.<br>
><br>
><br>
><br>
> That being said! I have spent the last week at the summit talking to some of<br>
> our leaders, including Doug Hellmann (cc’d), Jonathan Bryce and Mike Perez<br>
> regarding the future of the project. Between myself and other community<br>
> members, we have been drafting plans and coming up with a new direction that<br>
> will hopefully be sustainable in the long-term.<br>
><br>
><br>
><br>
> I am interested to hear your thoughts. I want to make sure that everyone<br>
> feels that we’re headed in the right direction first and foremost. All of<br>
> these action items are documented in this WIP etherpad:<br>
> <a href="https://etherpad.openstack.org/p/doc-planning" target="_blank">https://etherpad.openstack.org/p/doc-planning</a><br>
><br>
><br>
><br>
> Some further highlights from the event…<br>
><br>
><br>
><br>
> · The documentation team was represented by myself, Olga, and Alex<br>
> Adamov for the Project Update: Documentation on the Monday. If you’d like to<br>
> catch up with what we talked about, the video is available online now:<br>
> <a href="https://www.youtube.com/watch?v=jcfbKxbpRvc" target="_blank">https://www.youtube.com/watch?v=jcfbKxbpRvc</a> The translation team PTL, Ian<br>
> Choi, also had a session about getting more involved with the I18N team. You<br>
> can view that video here: <a href="https://www.youtube.com/watch?v=ybFI4nez_Z8" target="_blank">
https://www.youtube.com/watch?v=ybFI4nez_Z8</a><br>
><br>
><br>
><br>
> · Ian and I also hosted the joint I18N and documentation onboarding<br>
> session. We were visited by some friendly faces, and some new ones. Between<br>
> Ian and myself, we discussed the documentation and translation workflows,<br>
> and how to get involved (the mailing list, IRC channel, etc). Which was lots<br>
> of fun :) we’d love to see more people there in the future, hopefully we’ll<br>
> slowly get there!<br>
><br>
><br>
><br>
> · This week I was focusing heavily on making the community aware<br>
> that the documentation team was struggling to maintain contributors, but<br>
> continuing with the same amount of work. This was a heavy conversation to be<br>
> having, but it posed some really interesting questions to key leaders, and<br>
> hopefully raised appropriate concerns. Ildiko and I hosted “OpenStack<br>
> documentation: The future depends on all of us”. This was a really<br>
> interesting session. I was able to pose to the group of attendees that the<br>
> documentation team was struggling to maintain contributions. Major Hayden<br>
> was kind enough to take notes during the session, you can find those here:<br>
> <a href="https://etherpad.openstack.org/p/doc-future" target="_blank">https://etherpad.openstack.org/p/doc-future</a> The project teams that came and<br>
> represented their groups were interested in discussing the project-specific<br>
> documentation (is living in the project’s repo tree the best place?) and<br>
> voiced concerns I had otherwise not heard before. I recommend reading the<br>
> notes to get a better idea :)<br>
><br>
><br>
><br>
> · Kendall Nelson and Ildiko also hosted a session on the OpenStack<br>
> Upstream Institute highlights. I recommend watching the video which is now<br>
> live and available here:<br>
> <a href="https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-highlights" target="_blank">
https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-highlights</a><br>
><br>
><br>
><br>
> · One of the key takeaways from the summit was the session that I<br>
> joint moderated with Melvin Hillsman regarding the Operations and<br>
> Administration Guides. You can find the etherpad with notes here:<br>
> <a href="https://etherpad.openstack.org/p/admin-ops-guides" target="_blank">
https://etherpad.openstack.org/p/admin-ops-guides</a> The session was really<br>
> helpful – we were able to discuss with the operators present the current<br>
> situation of the documentation team, and how they could help us maintain the<br>
> two guides, aimed at the same audience. The operator’s present at the<br>
> session agreed that the Administration Guide was important, and could be<br>
> maintained upstream. However, they voted and agreed that the best course of<br>
> action for the Operations Guide was for it to be pulled down and put into a<br>
> wiki that the operators could manage themselves. We will be looking at<br>
> actioning this item as soon as possible.<br>
><br>
><br>
><br>
> These action items will free up the documentation team to become gate<br>
> keepers and reviewers of documentation. Our key focus as a team will be on<br>
> the tooling for the <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> site (including the API docs).<br>
><br>
><br>
><br>
> I’m really interested to hear everyone’s thoughts going forward – this is<br>
> not set in stone. We need to change our strategy, and now is the time. If<br>
> you’d rather reach out and discuss this personally, asettle on IRC is always<br>
> the best place to find me.<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> Alex<br>
><br>
><br>
><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
> --<br>
><br>
> Kind regards,<br>
><br>
> Melvin Hillsman<br>
><br>
> <a href="mailto:mrhillsman@gmail.com">mrhillsman@gmail.com</a><br>
> mobile: <a href="tel:%28832%29%20264-2646">(832) 264-2646</a><br>
><br>
> Learner | Ideation | Belief | Responsibility | Command<br>
><br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
<br>
<br>
<br>
--<br>
Cheers,<br>
~Blairo<br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br clear="all">
<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">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Read my blog: <a href="https://justwriteclick.com" target="_blank">
justwrite.click</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Subscribe to Docs|Code: <a href="http://docslikecode.com" target="_blank">
docslikecode.com</a> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>