<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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
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">Flanders,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">This is awesome!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Erin and Jimmy,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Please, add these details to the UC session that you have extended.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Edgar<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><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="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">David F Flanders <flanders@openstack.org><br>
<b>Date: </b>Tuesday, September 20, 2016 at 5:53 PM<br>
<b>To: </b>user-committee <user-committee@lists.openstack.org><br>
<b>Cc: </b>Edgar Magana <edgar.magana@workday.com>, Shilla Saebi <shilla.saebi@gmail.com>, Jon Proulx <jon@csail.mit.edu><br>
<b>Subject: </b>Re: [User-committee] Efficiency of WGs?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Dear WG and UC chairs,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">As per the UC's request, below is a proposed Title and Abstract for an additional session at the Barcelona Summit. Amendments, suggestions and agenda items most welcome, I've attempted to summarise this
thread via the 'proposed agenda items" below, please do add additional items in reply if I've missed your point.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Title: Efficiency of working groups - working together to advance the community leadership of the user committee.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Primary Audience: Working Group Chairs and Regular WG attendees.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Secondary Audience: Any community member looking to participate and/or hep organise a user-committee working group.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Abstract: Running a Working Group which represents one of the many users of the OpenStack community is not a trivial task, especially when best practices with regards to the open principles are observed.
This session will be lead by the User Committee and attended by Working Group chairs to discuss "good practice" in how to run a working group which has been approved by the User-Committee. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Proposed agenda items:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- Goal setting methodologies by chairs for each cycle, buy-in, tracking, deliverable, shared ownership by WG. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- User Committee engagement with WGs and leadership role of UC.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - Good practice for running F2F meetings at Summit: 2-3 session to assure outcomes, social gatherings, etc.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - Recruitment of new members.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - Timezones and cultural considerations.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - International perception and foreign language member participation.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - Communication between WG co-chairs and UC chairs.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - Input by WGs into Blueprints, working with the TC/PTLs in cycle planning.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- Sub-teams/activities in WGs and/or new WGs... to sub-WG or not to sub-WG... aka WG scope.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- Joint midcycles with other WGs? Organised by the UC?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- Co-located WG meetings, i.e. WGs with overlapping membership to meet after one another?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- WG Co-Chairs: different regions and remits? EU+USA+APAC?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">- WG meeting preparation: calendar items, call for agenda items, use of etherpads, wiki updates, email to user-committee, agreed open meeting channel (voice vs irc), etc<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - WG meeting runtime: irc meeting bot, agenda with note taking, recorded actions, reminder of overall objectives for cycle, etc<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"> - WG post-meeting remit: summary of meeting posted to user-committee mailing list, list of follow up actions per member name and suggested ETA, etc.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Naturally, most of the above cannot be covered in a single hour so I'll leave it up to the UC and WGs to place +1s next to the items which they feel are of most significance. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Kind Regards, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma">Flanders<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Sep 21, 2016 at 2:11 AM, Edgar Magana <<a href="mailto:edgar.magana@workday.com" target="_blank">edgar.magana@workday.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">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri">Jimmy,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri">We have requested already the UC one. Maybe we can extend that one to make sure that we have time for all WGs chairs and co-chairs.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri">Edgar</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:Calibri"> </span><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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">Jimmy Mcarthur <<a href="mailto:jimmy@tipit.net" target="_blank">jimmy@tipit.net</a>><br>
<b>Date: </b>Tuesday, September 20, 2016 at 9:05 AM<br>
<b>To: </b>David F Flanders <<a href="mailto:flanders@openstack.org" target="_blank">flanders@openstack.org</a>><br>
<b>Cc: </b>Edgar Magana <<a href="mailto:edgar.magana@workday.com" target="_blank">edgar.magana@workday.com</a>>, user-committee <<a href="mailto:user-committee@lists.openstack.org" target="_blank">user-committee@lists.openstack.org</a>><br>
<b>Subject: </b>Re: [User-committee] Efficiency of WGs?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt">If this is a need, please let us know so that we can schedule a room for you :)<br>
<br>
Thanks!<br>
Jimmy<br>
<br>
<o:p></o:p></p>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div style="margin-left:18.75pt;margin-top:22.5pt;margin-right:18.75pt;margin-bottom:7.5pt">
<div style="border:none;border-top:solid #EDEEF0 1.0pt;padding:4.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:middle">
<a href="mailto:flanders@openstack.org" target="_blank"><b>David F Flanders</b></a><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right;vertical-align:middle">
<span style="color:#9FA2A5">September 19, 2016 at 5:54 PM</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.25in;margin-right:.25in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-family:Tahoma;color:#888888">Is there plans for the WG chairs to meet together in Barcelona to make some decisions on these efficiencies?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:Tahoma;color:#888888">/me smiles cheekily at a very busy Edgar ;-)</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#888888"><br>
<br>
<br clear="all">
<br>
-- </span><o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:7.5pt;font-family:Tahoma;color:#888888">Flanders | OpenStack Foundation | Community Manager (Cloud Application Communities)<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__superuser.openstack.org_articles_meet-2Dopenstack-2Ds-2Dcommunity-2Dwrangler-2Ddavid-2Dflanders&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=w43IRGshZRnYy0DjwPq4TvJR_SCYutjVGu9n1Rb3jjE&e=" target="_blank">http://superuser.openstack.org/articles/meet-openstack-s-community-wrangler-david-flanders</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#888888">_______________________________________________<br>
User-committee mailing list<br>
<a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a></span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:18.75pt;margin-top:22.5pt;margin-right:18.75pt;margin-bottom:7.5pt">
<div style="border:none;border-top:solid #EDEEF0 1.0pt;padding:4.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;vertical-align:middle">
<a href="mailto:doc@aedo.net" target="_blank"><b>Christopher Aedo</b></a><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right;vertical-align:middle">
<span style="color:#9FA2A5">September 13, 2016 at 1:31 PM</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.25in;margin-right:.25in">
<pre><span style="color:#888888">On Wed, Sep 7, 2016 at 7:27 AM, Jimmy Mcarthur <a href="mailto:jimmy@tipit.net" target="_blank"><jimmy@tipit.net></a> wrote:</span><o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#888888">Christopher,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">We might be able to lend a hand with the authentication piece if you're able</span><o:p></o:p></pre>
<pre><span style="color:#888888">to use OpenStackID.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.openstack.org_infra_system-2Dconfig_openstackid.html&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=kLlsJeK7C_8XheMoYCl510yBa4FEgacFXjAFv7LAe9s&e=" target="_blank">http://docs.openstack.org/infra/system-config/openstackid.html</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack-2Dinfra_openstackid&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=PcCe2WgSuUykVQi5T2Gz20F4u3iysESjtwEU4sP6AmY&e=" target="_blank">https://github.com/openstack-infra/openstackid</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">If this is something you're interested in, let me know. I believe we can</span><o:p></o:p></pre>
<pre><span style="color:#888888">help you out.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Thanks!</span><o:p></o:p></pre>
<pre><span style="color:#888888">Jimmy McArthur</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
</blockquote>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Jimmy, this is definitely something I'd love to have some help on!</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The Lounge is a NodeJS app and is available at</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_thelounge_lounge_&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=Q5wMUmHcNU4peXFHfgtZ1_rI_2PQZMngNCRoCi_5vqk&e=" target="_blank">https://github.com/thelounge/lounge/</a> They also have an active</span><o:p></o:p></pre>
<pre><span style="color:#888888">presence on Freenode IRC (#thelounge).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The need is to integrate authentication using OpenStackID. It should</span><o:p></o:p></pre>
<pre><span style="color:#888888">be similar to this PR (recently merged) which implemented support for</span><o:p></o:p></pre>
<pre><span style="color:#888888">authentication against LDAP:</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_thelounge_lounge_pull_477&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=aOagbTh4FQi-dYkiJdDUbbkb3WVMr9-eCuxcbHZ_3l0&e=" target="_blank">https://github.com/thelounge/lounge/pull/477</a> ..</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">In conversation with the lounge devs on IRC they've indicated they</span><o:p></o:p></pre>
<pre><span style="color:#888888">would welcome this work, so I don't anticipate any major issues</span><o:p></o:p></pre>
<pre><span style="color:#888888">getting the code accepted. They're pretty responsive with</span><o:p></o:p></pre>
<pre><span style="color:#888888">contributors and have been really friendly in my experience. Let me</span><o:p></o:p></pre>
<pre><span style="color:#888888">know if you have questions, and if there's anything more I can to do</span><o:p></o:p></pre>
<pre><span style="color:#888888">help coordinate this.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">-Christopher</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#888888">Christopher Aedo</span><o:p></o:p></pre>
<pre><span style="color:#888888">September 7, 2016 at 2:34 AM</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">On Mon, Sep 5, 2016 at 3:24 PM, Blair Bethwaite</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="mailto:blair.bethwaite@monash.edu" target="_blank"><blair.bethwaite@monash.edu></a> wrote:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Hi Flanders,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Great discussion. Prompted me to go remind myself of the role and/or</span><o:p></o:p></pre>
<pre><span style="color:#888888">definition of an OS UC Working Group... I didn't find anything "formal", but</span><o:p></o:p></pre>
<pre><span style="color:#888888">w.o.o/UserCommittee says:</span><o:p></o:p></pre>
<pre><span style="color:#888888">=====</span><o:p></o:p></pre>
<pre><span style="color:#888888">The user committee's role is to represent the needs of the diverse range of</span><o:p></o:p></pre>
<pre><span style="color:#888888">OpenStack users. The user committee is advised by Working Groups, each of</span><o:p></o:p></pre>
<pre><span style="color:#888888">whom represents different user audiences and interests.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The user committee mission is to:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Consolidate user requirements and present these to the management board and</span><o:p></o:p></pre>
<pre><span style="color:#888888">technical committee[1].</span><o:p></o:p></pre>
<pre><span style="color:#888888">Provide guidance for the development teams where user feedback is requested</span><o:p></o:p></pre>
<pre><span style="color:#888888">Track OpenStack deployments and usage, helping to share user stories and</span><o:p></o:p></pre>
<pre><span style="color:#888888">experiences</span><o:p></o:p></pre>
<pre><span style="color:#888888">Work with the user groups worldwide to keep the OpenStack community vibrant</span><o:p></o:p></pre>
<pre><span style="color:#888888">and informed</span><o:p></o:p></pre>
<pre><span style="color:#888888">=====</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">>From the WG activity perspective I would highlight it is very</span><o:p></o:p></pre>
<pre><span style="color:#888888">useful/important to have some direction (as well as support) coming from the</span><o:p></o:p></pre>
<pre><span style="color:#888888">UC - I think our experience with the scientific-wg is roughly that we have a</span><o:p></o:p></pre>
<pre><span style="color:#888888">large interest base and plenty of people who find good value in talking to</span><o:p></o:p></pre>
<pre><span style="color:#888888">and sharing with their peers, but it is quite hard to turn that into</span><o:p></o:p></pre>
<pre><span style="color:#888888">concrete forward momentum or to even mint well articulated goals from within</span><o:p></o:p></pre>
<pre><span style="color:#888888">the group.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">On engagement, IRC is useful for reasons already mentioned in this thread</span><o:p></o:p></pre>
<pre><span style="color:#888888">(and we've been fortunate to have some valuable interactions thanks some</span><o:p></o:p></pre>
<pre><span style="color:#888888">core devs having keyword watches setup on OpenStack channels), but I think</span><o:p></o:p></pre>
<pre><span style="color:#888888">we alienate and/or make things too hard for some potential contributors. And</span><o:p></o:p></pre>
<pre><span style="color:#888888">I don't think it makes a great watercooler discussion tool (e.g. no offline</span><o:p></o:p></pre>
<pre><span style="color:#888888">history etc without setting up a bouncer - and that is fairly opaque even</span><o:p></o:p></pre>
<pre><span style="color:#888888">for a CS major).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">I'm a huge fan of the way we use IRC in the OpenStack community, but</span><o:p></o:p></pre>
<pre><span style="color:#888888">have also recognized getting up and running with a persistent IRC</span><o:p></o:p></pre>
<pre><span style="color:#888888">connection can pose a significant barrier to many very smart and</span><o:p></o:p></pre>
<pre><span style="color:#888888">technically sharp humans. To that end I wrote a spec to provide a</span><o:p></o:p></pre>
<pre><span style="color:#888888">hosted, persistent IRC web-client [1]. Lately however the effort has</span><o:p></o:p></pre>
<pre><span style="color:#888888">been stalled due to my lack of experience with JS; if we can find</span><o:p></o:p></pre>
<pre><span style="color:#888888">someone who can plumb in the auth piece, we could be up and running</span><o:p></o:p></pre>
<pre><span style="color:#888888">with this fairly quickly.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">I think getting that right will be worth the effort, and could get a</span><o:p></o:p></pre>
<pre><span style="color:#888888">whole lot more people engaged across all our various domains.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">[1] <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_319506&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=oZligmX5wJX3LmxYW2RJCQ7IJCBKT9NUd2ZmMRsbsc8&e=" target="_blank">https://review.openstack.org/319506</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">-Christopher</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Having (myself) done a fairly woeful job of keeping pace with the dev side</span><o:p></o:p></pre>
<pre><span style="color:#888888">of OS progression this cycle I'm also interested in exploring ways of</span><o:p></o:p></pre>
<pre><span style="color:#888888">highlighting activities/work that may be of interest to any particular WG.</span><o:p></o:p></pre>
<pre><span style="color:#888888">The first thing that springs to mind is tagging of blueprints and reviews,</span><o:p></o:p></pre>
<pre><span style="color:#888888">e.g., where a dev or other community member is looking for</span><o:p></o:p></pre>
<pre><span style="color:#888888">input/support/resolution from a specific target user group. This could be a</span><o:p></o:p></pre>
<pre><span style="color:#888888">mechanism we as chairs utilise to surface agenda items, solicit input and</span><o:p></o:p></pre>
<pre><span style="color:#888888">then respond on behalf of the group.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Cheers,</span><o:p></o:p></pre>
<pre><span style="color:#888888">Blair</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">On 30 August 2016 at 10:36, David F Flanders <a href="mailto:flanders@openstack.org" target="_blank"><flanders@openstack.org></a> wrote:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Dear Working Group Co-Chairs and User Committee Chairs,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,</span><o:p></o:p></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly</span><o:p></o:p></pre>
<pre><span style="color:#888888">basis to run a global meeting:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe</span><o:p></o:p></pre>
<pre><span style="color:#888888">members)</span><o:p></o:p></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad</span><o:p></o:p></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda</span><o:p></o:p></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is</span><o:p></o:p></pre>
<pre><span style="color:#888888">occurring along with agenda links</span><o:p></o:p></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)</span><o:p></o:p></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well</span><o:p></o:p></pre>
<pre><span style="color:#888888">taken notes if via voice)</span><o:p></o:p></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting</span><o:p></o:p></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for</span><o:p></o:p></pre>
<pre><span style="color:#888888">consideration, etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888">h.) follow up actions.</span><o:p></o:p></pre>
<pre><span style="color:#888888">i.) recruit new members</span><o:p></o:p></pre>
<pre><span style="color:#888888">j.) plan for summit meetings</span><o:p></o:p></pre>
<pre><span style="color:#888888">k.) etc etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an</span><o:p></o:p></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and</span><o:p></o:p></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some</span><o:p></o:p></pre>
<pre><span style="color:#888888">of their massive communities.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Other options include:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing</span><o:p></o:p></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one</span><o:p></o:p></pre>
<pre><span style="color:#888888">after another).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create</span><o:p></o:p></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging</span><o:p></o:p></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may</span><o:p></o:p></pre>
<pre><span style="color:#888888">be?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Kind Regards,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Flanders</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">--</span><o:p></o:p></pre>
<pre><span style="color:#888888">Blair Bethwaite</span><o:p></o:p></pre>
<pre><span style="color:#888888">Senior HPC Consultant</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Monash eResearch Centre</span><o:p></o:p></pre>
<pre><span style="color:#888888">Monash University</span><o:p></o:p></pre>
<pre><span style="color:#888888">Room G26, 15 Innovation Walk, Clayton Campus</span><o:p></o:p></pre>
<pre><span style="color:#888888">Clayton VIC 3800</span><o:p></o:p></pre>
<pre><span style="color:#888888">Australia</span><o:p></o:p></pre>
<pre><span style="color:#888888">Mobile: <a href="tel:0439-545-002" target="_blank">0439-545-002</a></span><o:p></o:p></pre>
<pre><span style="color:#888888">Office: <a href="tel:%2B61%203-9903-2800" target="_blank">+61 3-9903-2800</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">_______________________________________________</span><o:p></o:p></pre>
<pre><span style="color:#888888">User-committee mailing list</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">_______________________________________________</span><o:p></o:p></pre>
<pre><span style="color:#888888">User-committee mailing list</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Blair Bethwaite</span><o:p></o:p></pre>
<pre><span style="color:#888888">September 5, 2016 at 5:24 PM</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Hi Flanders,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Great discussion. Prompted me to go remind myself of the role and/or</span><o:p></o:p></pre>
<pre><span style="color:#888888">definition of an OS UC Working Group... I didn't find anything "formal", but</span><o:p></o:p></pre>
<pre><span style="color:#888888">w.o.o/UserCommittee says:</span><o:p></o:p></pre>
<pre><span style="color:#888888">=====</span><o:p></o:p></pre>
<pre><span style="color:#888888">The user committee's role is to represent the needs of the diverse range of</span><o:p></o:p></pre>
<pre><span style="color:#888888">OpenStack users. The user committee is advised by Working Groups, each of</span><o:p></o:p></pre>
<pre><span style="color:#888888">whom represents different user audiences and interests.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The user committee mission is to:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Consolidate user requirements and present these to the management board and</span><o:p></o:p></pre>
<pre><span style="color:#888888">technical committee[1].</span><o:p></o:p></pre>
<pre><span style="color:#888888">Provide guidance for the development teams where user feedback is requested</span><o:p></o:p></pre>
<pre><span style="color:#888888">Track OpenStack deployments and usage, helping to share user stories and</span><o:p></o:p></pre>
<pre><span style="color:#888888">experiences</span><o:p></o:p></pre>
<pre><span style="color:#888888">Work with the user groups worldwide to keep the OpenStack community vibrant</span><o:p></o:p></pre>
<pre><span style="color:#888888">and informed</span><o:p></o:p></pre>
<pre><span style="color:#888888">=====</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">>From the WG activity perspective I would highlight it is very</span><o:p></o:p></pre>
<pre><span style="color:#888888">useful/important to have some direction (as well as support) coming from the</span><o:p></o:p></pre>
<pre><span style="color:#888888">UC - I think our experience with the scientific-wg is roughly that we have a</span><o:p></o:p></pre>
<pre><span style="color:#888888">large interest base and plenty of people who find good value in talking to</span><o:p></o:p></pre>
<pre><span style="color:#888888">and sharing with their peers, but it is quite hard to turn that into</span><o:p></o:p></pre>
<pre><span style="color:#888888">concrete forward momentum or to even mint well articulated goals from within</span><o:p></o:p></pre>
<pre><span style="color:#888888">the group.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">On engagement, IRC is useful for reasons already mentioned in this thread</span><o:p></o:p></pre>
<pre><span style="color:#888888">(and we've been fortunate to have some valuable interactions thanks some</span><o:p></o:p></pre>
<pre><span style="color:#888888">core devs having keyword watches setup on OpenStack channels), but I think</span><o:p></o:p></pre>
<pre><span style="color:#888888">we alienate and/or make things too hard for some potential contributors. And</span><o:p></o:p></pre>
<pre><span style="color:#888888">I don't think it makes a great watercooler discussion tool (e.g. no offline</span><o:p></o:p></pre>
<pre><span style="color:#888888">history etc without setting up a bouncer - and that is fairly opaque even</span><o:p></o:p></pre>
<pre><span style="color:#888888">for a CS major).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Having (myself) done a fairly woeful job of keeping pace with the dev side</span><o:p></o:p></pre>
<pre><span style="color:#888888">of OS progression this cycle I'm also interested in exploring ways of</span><o:p></o:p></pre>
<pre><span style="color:#888888">highlighting activities/work that may be of interest to any particular WG.</span><o:p></o:p></pre>
<pre><span style="color:#888888">The first thing that springs to mind is tagging of blueprints and reviews,</span><o:p></o:p></pre>
<pre><span style="color:#888888">e.g., where a dev or other community member is looking for</span><o:p></o:p></pre>
<pre><span style="color:#888888">input/support/resolution from a specific target user group. This could be a</span><o:p></o:p></pre>
<pre><span style="color:#888888">mechanism we as chairs utilise to surface agenda items, solicit input and</span><o:p></o:p></pre>
<pre><span style="color:#888888">then respond on behalf of the group.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Cheers,</span><o:p></o:p></pre>
<pre><span style="color:#888888">Blair</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">On 30 August 2016 at 10:36, David F Flanders <a href="mailto:flanders@openstack.org" target="_blank"><flanders@openstack.org></a> wrote:</span><o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#888888">Dear Working Group Co-Chairs and User Committee Chairs,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,</span><o:p></o:p></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly</span><o:p></o:p></pre>
<pre><span style="color:#888888">basis to run a global meeting:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe</span><o:p></o:p></pre>
<pre><span style="color:#888888">members)</span><o:p></o:p></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad</span><o:p></o:p></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda</span><o:p></o:p></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is</span><o:p></o:p></pre>
<pre><span style="color:#888888">occurring along with agenda links</span><o:p></o:p></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)</span><o:p></o:p></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well</span><o:p></o:p></pre>
<pre><span style="color:#888888">taken notes if via voice)</span><o:p></o:p></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting</span><o:p></o:p></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for</span><o:p></o:p></pre>
<pre><span style="color:#888888">consideration, etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888">h.) follow up actions.</span><o:p></o:p></pre>
<pre><span style="color:#888888">i.) recruit new members</span><o:p></o:p></pre>
<pre><span style="color:#888888">j.) plan for summit meetings</span><o:p></o:p></pre>
<pre><span style="color:#888888">k.) etc etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an</span><o:p></o:p></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and</span><o:p></o:p></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some</span><o:p></o:p></pre>
<pre><span style="color:#888888">of their massive communities.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Other options include:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing</span><o:p></o:p></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one</span><o:p></o:p></pre>
<pre><span style="color:#888888">after another).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create</span><o:p></o:p></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging</span><o:p></o:p></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may</span><o:p></o:p></pre>
<pre><span style="color:#888888">be?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Kind Regards,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Flanders</span><o:p></o:p></pre>
</blockquote>
<pre><span style="color:#888888">--</span><o:p></o:p></pre>
<pre><span style="color:#888888">Blair Bethwaite</span><o:p></o:p></pre>
<pre><span style="color:#888888">Senior HPC Consultant</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Monash eResearch Centre</span><o:p></o:p></pre>
<pre><span style="color:#888888">Monash University</span><o:p></o:p></pre>
<pre><span style="color:#888888">Room G26, 15 Innovation Walk, Clayton Campus</span><o:p></o:p></pre>
<pre><span style="color:#888888">Clayton VIC 3800</span><o:p></o:p></pre>
<pre><span style="color:#888888">Australia</span><o:p></o:p></pre>
<pre><span style="color:#888888">Mobile: <a href="tel:0439-545-002" target="_blank">0439-545-002</a></span><o:p></o:p></pre>
<pre><span style="color:#888888">Office: <a href="tel:%2B61%203-9903-2800" target="_blank">+61 3-9903-2800</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">_______________________________________________</span><o:p></o:p></pre>
<pre><span style="color:#888888">User-committee mailing list</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a></span><o:p></o:p></pre>
<pre><span style="color:#888888">David F Flanders</span><o:p></o:p></pre>
<pre><span style="color:#888888">August 29, 2016 at 7:36 PM</span><o:p></o:p></pre>
<pre><span style="color:#888888">Dear Working Group Co-Chairs and User Committee Chairs,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,</span><o:p></o:p></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly</span><o:p></o:p></pre>
<pre><span style="color:#888888">basis to run a global meeting:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe members)</span><o:p></o:p></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad</span><o:p></o:p></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda</span><o:p></o:p></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is</span><o:p></o:p></pre>
<pre><span style="color:#888888">occurring along with agenda links</span><o:p></o:p></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)</span><o:p></o:p></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well</span><o:p></o:p></pre>
<pre><span style="color:#888888">taken notes if via voice)</span><o:p></o:p></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting</span><o:p></o:p></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for</span><o:p></o:p></pre>
<pre><span style="color:#888888">consideration, etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888">h.) follow up actions.</span><o:p></o:p></pre>
<pre><span style="color:#888888">i.) recruit new members</span><o:p></o:p></pre>
<pre><span style="color:#888888">j.) plan for summit meetings</span><o:p></o:p></pre>
<pre><span style="color:#888888">k.) etc etc.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an</span><o:p></o:p></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and</span><o:p></o:p></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some</span><o:p></o:p></pre>
<pre><span style="color:#888888">of their massive communities.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to</span><o:p></o:p></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Other options include:</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing</span><o:p></o:p></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one</span><o:p></o:p></pre>
<pre><span style="color:#888888">after another).</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create</span><o:p></o:p></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging</span><o:p></o:p></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may</span><o:p></o:p></pre>
<pre><span style="color:#888888">be?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Kind Regards,</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">Flanders</span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888">_______________________________________________</span><o:p></o:p></pre>
<pre><span style="color:#888888">User-committee mailing list</span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a></span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
<pre><span style="color:#888888"> </span><o:p></o:p></pre>
</blockquote>
</div>
</blockquote>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
User-committee mailing list<br>
<a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DQMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Cvm-NPS-_gKD2tfvEq7ch6eNNM6vsnnhRo-3fTQhgIE&s=9AJcjeXmNIkn6MDfS4BgN0-qeouoP8M1R0yMFHLPExg&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:Tahoma">Flanders | OpenStack Foundation | Community Manager (Cloud Application Communities)<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__superuser.openstack.org_articles_meet-2Dopenstack-2Ds-2Dcommunity-2Dwrangler-2Ddavid-2Dflanders&d=DQMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Cvm-NPS-_gKD2tfvEq7ch6eNNM6vsnnhRo-3fTQhgIE&s=FlPkeTL1lGbQwLVxaqzsyaLJf2VMnZA6Wd2KhphPanI&e=" target="_blank">http://superuser.openstack.org/articles/meet-openstack-s-community-wrangler-david-flanders</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>