<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thanks </div><div id="AppleMailSignature">I am happy to hear that as I was in different meetings during the summit I was not able to meet anyone from the i18n team. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I will be happy to also hear more on some of those options. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Sincerely </div><div id="AppleMailSignature">Remo<br><br>Inviato da iPhone</div><div><br>Il giorno 25 mag 2017, alle ore 06:42, Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>> ha scritto:<br><br></div><blockquote type="cite"><div>
<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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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;}
@font-face
{font-family:"Apple Color Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:500781762;
mso-list-type:hybrid;
mso-list-template-ids:1118725330 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New",serif;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Docs update below </span><span style="font-size:11.0pt;font-family:"Apple Color Emoji"">☺</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><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"><b><span style="color:black">From: </span></b><span style="color:black">Alexandra Settle <<a href="mailto:a.settle@outlook.com">a.settle@outlook.com</a>><br>
<b>Date: </b>Friday, May 19, 2017 at 12:12 PM<br>
<b>To: </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>Cc: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Subject: </b>[OpenStack-docs] [openstack-doc] [dev] What's up doc? Summit recap edition<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi everyone,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
The OpenStack manuals project had a really productive week at the OpenStack summit in Boston. You can find a list of all the etherpads and attendees here:
<a href="https://etherpad.openstack.org/p/docs-summit">https://etherpad.openstack.org/p/docs-summit</a>
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As we all know, we are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010,
we’ve been climbing higher and higher trying to achieve the best documentation we could, and uphold our high standards. This is something to be incredibly proud of. However, we now need to take a step back and realise that the amount of work we are attempting
to maintain is now out of reach for the team size that we have. At the moment we have 13 cores, of which none are full time contributors or reviewers. This includes myself.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">That being said! I have spent the last week at the summit talking to some of our leaders, including Doug Hellmann (cc’d), Jonathan Bryce and Mike Perez regarding the future of the project. Between myself and
other community members, we have been drafting plans and coming up with a new direction that will hopefully be sustainable in the long-term.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I am interested to hear your thoughts. I want to make sure that everyone feels that we’re headed in the right direction first and foremost. All of these action items are documented in this WIP etherpad:
<a href="https://etherpad.openstack.org/p/doc-planning">https://etherpad.openstack.org/p/doc-planning</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Some further highlights from the event…
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">The documentation team was represented by myself, Olga, and Alex Adamov for the Project Update: Documentation on the Monday. If you’d like to catch up
with what we talked about, the video is available online now: <a href="https://www.youtube.com/watch?v=jcfbKxbpRvc">
https://www.youtube.com/watch?v=jcfbKxbpRvc</a> The translation team PTL, Ian Choi, also had a session about getting more involved with the I18N team. You can view that video here:
<a href="https://www.youtube.com/watch?v=ybFI4nez_Z8">https://www.youtube.com/watch?v=ybFI4nez_Z8</a></span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">Ian and I also hosted the joint I18N and documentation onboarding session. We were visited by some friendly faces, and some new ones. Between Ian and
myself, we discussed the documentation and translation workflows, and how to get involved (the mailing list, IRC channel, etc). Which was lots of fun :) we’d love to see more people there in the future, hopefully we’ll slowly get there!</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">This week I was focusing heavily on making the community aware that the documentation team was struggling to maintain contributors, but continuing with
the same amount of work. This was a heavy conversation to be having, but it posed some really interesting questions to key leaders, and hopefully raised appropriate concerns. Ildiko and I hosted “OpenStack documentation: The future depends on all of us”. This
was a really interesting session. I was able to pose to the group of attendees that the documentation team was struggling to maintain contributions. Major Hayden was kind enough to take notes during the session, you can find those here:
<a href="https://etherpad.openstack.org/p/doc-future">https://etherpad.openstack.org/p/doc-future</a> The project teams that came and represented their groups were interested in discussing the project-specific documentation (is living in the project’s repo
tree the best place?) and voiced concerns I had otherwise not heard before. I recommend reading the notes to get a better idea :)</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">Kendall Nelson and Ildiko also hosted a session on the OpenStack Upstream Institute highlights. I recommend watching the video which is now live and
available here: <a href="https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-highlights">
https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-highlights</a>
</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt">One of the key takeaways from the summit was the session that I joint moderated with Melvin Hillsman regarding the Operations and Administration Guides.
You can find the etherpad with notes here: <a href="https://etherpad.openstack.org/p/admin-ops-guides">
https://etherpad.openstack.org/p/admin-ops-guides</a> The session was really helpful – we were able to discuss with the operators present the current situation of the documentation team, and how they could help us maintain the two guides, aimed at the same
audience. The operator’s present at the session agreed that the Administration Guide was important, and could be maintained upstream. However, they voted and agreed that the best course of action for the Operations Guide was for it to be pulled down and put
into a wiki that the operators could manage themselves. We will be looking at actioning this item as soon as possible.</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">These action items will free up the documentation team to become gate keepers and reviewers of documentation. Our key focus as a team will be on the tooling for the <a href="http://docs.openstack.org">docs.openstack.org</a> site (including the API
docs).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’m really interested to hear everyone’s thoughts going forward – this is not set in stone. We need to change our strategy, and now is the time. If you’d rather reach out and discuss this personally, <i>asettle</i> on
IRC is always the best place to find me.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Alex</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
!DSPAM:5926df686371192914247!
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-I18n mailing list</span><br><span><a href="mailto:OpenStack-I18n@lists.openstack.org">OpenStack-I18n@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a></span><br><span></span><br><span>!DSPAM:5926df686371192914247!</span><br></div></blockquote></body></html>