<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:11.0pt;
font-family:"Calibri",sans-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.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle18
{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">I think this is a good idea :) thanks Mike. We get a lot of people coming to the docs chan or ML asking for help/where to start and sometimes it’s difficult to point them in the right direction.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just from experience working with contributor documentation, I’d avoid all screen shots if you can – updating them whenever the process changes (surprisingly often) is a lot of unnecessary technical debt.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The docs team put a significant amount of effort in a few releases back writing a pretty comprehensive Contributor Guide. For the purposes you describe below, I imagine a lot of the content here could be adapted. The process of setting
up for code and docs is exactly the same: <a href="http://docs.openstack.org/contributor-guide/index.html">
http://docs.openstack.org/contributor-guide/index.html</a> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I also wonder if we could include a ‘what is openstack’ 101 for new contributors. I find that there is a *<b>lot</b>* of material out there, but it is often very hard to explain to people what each project does, how they all interact, why
we install from different sources, why do we have official and unofficial projects etc. It doesn’t have to be seriously in-depth, but an overview that points people who are interested in the right directions. Often this will help people decide on what project
they’d like to undertake.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Alex<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Mike Perez <thingee@gmail.com><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Friday, June 23, 2017 at 9:17 PM<br>
<b>To: </b>OpenStack Development Mailing List <openstack-dev@lists.openstack.org><br>
<b>Cc: </b>Wes Wilson <wes@openstack.org>, "ildiko@openstack.org" <ildiko@openstack.org>, "knelson@openstack.org" <knelson@openstack.org><br>
<b>Subject: </b>[openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hello all,<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">Every month we have people asking on IRC or the dev mailing list having interest in working on OpenStack, and sometimes they're given different answers from people, or worse, no answer at all.
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Suggestion: lets work our efforts together to create some common documentation so that all teams in OpenStack can benefit.<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">First it’s important to note that we’re not just talking about code projects here. OpenStack contributions come in many forms such as running meet ups, identifying use cases (product working group), documentation,
testing, etc. We want to make sure those potential contributors feel welcomed too!<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">What is common documentation? Things like setting up Git, the many accounts you need to setup to contribute (gerrit, launchpad, OpenStack foundation account). Not all teams will use some common documentation, but
the point is one or more projects will use them. Having the common documentation worked on by various projects will better help prevent duplicated efforts, inconsistent documentation, and hopefully just more accurate information.<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">A team might use special tools to do their work. These can also be integrated in this idea as well.<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">Once we have common documentation we can have something like:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> 1. Choose your own adventure: I want to contribute by code<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> 2. What service type are you interested in? (Database, Block storage, compute)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> 3. Here’s step-by-step common documentation to setting up Git, IRC, Mailing Lists, Accounts, etc.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> 4. A service type project might choose to also include additional documentation in that flow for special tools, etc.<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">Important things to note in this flow:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * How do you want to contribute?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Here are **clear** names that identify the team. Not code names like Cloud Kitty, Cinder, etc.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * The documentation should really aim to not be daunting:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Someone should be able to glance at it and feel like they can finish things in five minutes. Not be yet another tab left in their browser that they’ll eventually forget about<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * No wall of text!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Use screen shots<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Avoid covering every issue you could hit along the way.<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">## Examples of More Simple Documentation<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I worked on some documentation for the Upstream University preparation that has received excellent feedback meet close to these suggestions:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * IRC [1]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Git [2]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Account Setup [3]<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">## 500 Feet Birds Eye view<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">There will be a Contributor landing page on the
<a href="http://openstack.org">openstack.org</a> website. Existing contributors will find reference links to quickly jump to things. New contributors will find a banner at the top of the page to direct them to the choose your own adventure to contributing to
OpenStack, with ordered documentation flow that reuses existing documentation when necessary. Picture also a progress bar somewhere to show how close you are to being ready to contribute to whatever team. Of course there are a lot of other fancy things we
can come up with, but I think getting something up as an initial pass would be better than what we have today.<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">Here's an example of what the sections/chapters could look like:<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">- Code<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Volumes (Cinder)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * IRC<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Git <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Account Setup<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Generating Configs<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Compute (Nova)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * IRC<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Git<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Account Setup<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Something about hypervisors (matrix?)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">- Use Cases<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* Products (Product working group)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* IRC<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> * Git<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* Use Case format<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">There are some rough mock up ideas [4]. Probably Sphinx will be fine for this. Potentially we could use this content for conference lunch and learns, upstream university, and the on-boarding events at the Forum.
What do you all think?<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">[1] - <a href="http://docs.openstack.org/upstream-training/irc.html">
http://docs.openstack.org/upstream-training/irc.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">[2] - <a href="http://docs.openstack.org/upstream-training/git.html">
http://docs.openstack.org/upstream-training/git.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">[3] - <a href="http://docs.openstack.org/upstream-training/accounts.html">
http://docs.openstack.org/upstream-training/accounts.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">[4] - <span style="color:black"><a href="https://www.dropbox.com/s/o46xh1cp0sv0045/OpenStack%20contributor%20portal.pdf?dl=0">https://www.dropbox.com/s/o46xh1cp0sv0045/OpenStack%20contributor%20portal.pdf?dl=0</a></span><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">—<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">Mike Perez<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>