<div dir="ltr">Hi Oscar,<div>We'd be happy to have you review documentation or write more tests for Tempest. Here's some information on how you review documentation patches. If you have any questions, please feel free to ask on the openstack-docs mailing list which I've copied and you can subscribe at <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>. We're also on IRC at #openstack-doc.</div>
<div><br></div><div>For Tempest tests, read <a href="http://docs.openstack.org/developer/tempest/">http://docs.openstack.org/developer/tempest/</a> and get in touch with Matthew Trenish, CCed here. </div><div><br></div><div>
<p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">To see what documentation changes are ready for review, use the Documentation Program Dashboard, a custom URL rendered at<a rel="nofollow" class="" href="http://is.gd/openstackdocsreview" style="color:rgb(0,136,204);text-decoration:none;padding-right:13px;background:url(https://wiki.openstack.org/w/skins/strapping/images/external-link-ltr-icon.png) 100% 50% no-repeat">http://is.gd/openstackdocsreview</a>. This dashboard is organized in groupings based on the audience for the documentation.</p>
<h4 style="margin:10px 0px;font-family:'PT Sans',sans-serif;line-height:20px;color:rgb(51,51,51);font-size:17.5px"><span class="" id="Who_can_review_documentation.3F">Who can review documentation?</span></h4><p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">
All community members can review doc patches and give them +1 or -1. Documentation Core members can give +2 or -2 votes and also click Approve so that the doc goes live, published to <a href="http://docs.openstack.org">docs.openstack.org</a> or <a href="http://developer.openstack.org">developer.openstack.org</a>, based on the branch the patch is applied to. Docs core members should only click Approve if they've given a +2, otherwise the Jenkins build jobs are not triggered.</p>
<p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">Because the Docs team is small, core members have the choice when reviewing and must use best judgment before publishing. Generally speaking, core members will wait for one other core member to +2 a doc patch. However if the change is small and the build works, a doc core member can +2 and Approve a change without waiting for another reviewer. This is a judgement call so docs core people should exercise caution when using this option.</p>
<p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">Once two community members approve a doc patch, a doc core member can also review it and push it through without waiting for a second core member.</p>
<h5 style="margin:10px 0px;font-family:'Arial Unicode MS',Arial,sans-serif;line-height:20px;color:rgb(51,51,51);font-size:14px"><span class="" id="Repositories_and_core_team">Repositories and core team</span></h5>
<p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">The OpenStack Docs team is core for api-site, openstack-manuals, operations-guide and openstack-doc-tools.</p>
<p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">For the following repositories that are part of the Documentation program special rules apply:</p>
<ul style="padding:0px;margin:0.3em 0px 0px 1.6em;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px"><li>training-guides: Has a separate core team.</li><li>security-doc: Has a separate core team consisting of docs team members and security team members. The rule here is that each patch needs an approval by a Docs core and a security team core.</li>
<li>api projects: Here both the OpenStack project core and the Docs core are cores, for example for image-api the keystone cores are cores as well.</li><li>docs-specs: Has a separate core team, see <a href="https://wiki.openstack.org/wiki/Documentation/HowTo#When_to_write_a_blueprint_description_in_docs-specs" style="color:rgb(0,136,204);text-decoration:none">docs-specs section</a></li>
</ul><h4 style="margin:10px 0px;font-family:'PT Sans',sans-serif;line-height:20px;color:rgb(51,51,51);font-size:17.5px"><span class="" id="How_to_Review_a_Documentation_Patch">How to Review a Documentation Patch</span></h4>
<ol style="padding:0px;margin:0.3em 0px 0px 3.2em;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px"><li>Click a patch set.</li><li>Click a file that has changed to view the changes side by side.</li>
<li>Click on the Jenkins gate that is called "checkbuild" (for the manuals it is "gate-openstack-manuals-tox-doc-publish-checkbuild") and review the built manuals to see how the change will look on the web page and as PDF.</li>
<li>Click the Review button and vote, then enter any comments about your review.</li></ol></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 21, 2014 at 9:06 AM, Oscar Junior <span dir="ltr"><<a href="mailto:Oscar.Junior@fit-tecnologia.org.br" target="_blank">Oscar.Junior@fit-tecnologia.org.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="PT-BR" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span lang="EN-US">Hi Anne Gentle, how are you?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I would like help the Openstack community, what is necessary? What they are needing currently? I can review or write any document or help with Tempest.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="110" style="width:82.5pt;padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" align="center" style="margin-bottom:12.0pt;text-align:center">
<span style="font-size:12.0pt;font-family:"Times New Roman","serif""><img width="110" height="136" src="cid:image001.jpg@01CFBD2E.D3342930" alt="logo"><u></u><u></u></span></p>
</td>
<td style="padding:0cm 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#1a7496">Oscar Correia</span></b><b><span lang="EN-US" style="font-size:8.5pt;font-family:"Times New Roman","serif""><br>
</span></b><b><span lang="EN-US" style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#1a7496">Software Quality</span></b><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
</span><span lang="EN-US" style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#1a7496">Tel.: <a href="tel:%2B55%2015%204009-0725" value="+551540090725" target="_blank">+55 15 4009-0725</a><br>
Cel.: <a href="tel:%2B55%2011%2098973-7857" value="+5511989737857" target="_blank">+55 11 98973-7857</a></span><span lang="EN-US" style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#1a7496"><br>
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span style="font-size:7.0pt;font-family:"Tahoma","sans-serif";color:#035289"><a href="http://www.fit-tecnologia.org.br/" title="fit tecnologia" target="_blank"><span lang="EN-US" style="color:blue">www.fit-tecnologia.org.br</span></a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
</span><b><span lang="EN-US" style="font-size:6.0pt;font-family:"Tahoma","sans-serif";color:#8dc63f">Before printing, think of your responsability with planet</span></b><span lang="EN-US" style="font-size:6.0pt;font-family:"Tahoma","sans-serif"">
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><u></u><u></u></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<br clear="both">
Legal Disclaimer:<br>
The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message!<br>
</div>
</blockquote></div><br></div>