<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">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">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.<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">Jimmy Mcarthur <jimmy@tipit.net><br>
<b>Date: </b>Tuesday, September 20, 2016 at 9:05 AM<br>
<b>To: </b>David F Flanders <flanders@openstack.org><br>
<b>Cc: </b>Edgar Magana <edgar.magana@workday.com>, user-committee <user-committee@lists.openstack.org><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>
<p class="MsoNormal">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>
<br>
<o:p></o:p></p>
<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="vertical-align:middle"><a href="mailto:flanders@openstack.org"><b>David F Flanders</b></a><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="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="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?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma;color:#888888">/me smiles cheekily at a very busy Edgar ;-)<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><br>
<br>
<br clear="all">
<br>
-- <o:p></o:p></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><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><span style="color:#888888"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">_______________________________________________<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=DQMCaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=lZwtjVJEK6mz-i3EKQC5l7oI-aZ_HJZpsoOkkcQucUY&s=3D6ClNkDvvSvr60CHILSGjjv8SpgmIxfgPGC1PqxY-0&e=">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></span></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="vertical-align:middle"><a href="mailto:doc@aedo.net"><b>Christopher Aedo</b></a><o:p></o:p></p>
</div>
<p class="MsoNormal" align="right" style="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"><jimmy@tipit.net></a> wrote:<o:p></o:p></span></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#888888">Christopher,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">We might be able to lend a hand with the authentication piece if you're able<o:p></o:p></span></pre>
<pre><span style="color:#888888">to use OpenStackID.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></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=">http://docs.openstack.org/infra/system-config/openstackid.html</a><o:p></o:p></span></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=">https://github.com/openstack-infra/openstackid</a><o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">If this is something you're interested in, let me know. I believe we can<o:p></o:p></span></pre>
<pre><span style="color:#888888">help you out.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Thanks!<o:p></o:p></span></pre>
<pre><span style="color:#888888">Jimmy McArthur<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
</blockquote>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Jimmy, this is definitely something I'd love to have some help on!<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The Lounge is a NodeJS app and is available at<o:p></o:p></span></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=">https://github.com/thelounge/lounge/</a> They also have an active<o:p></o:p></span></pre>
<pre><span style="color:#888888">presence on Freenode IRC (#thelounge).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The need is to integrate authentication using OpenStackID. It should<o:p></o:p></span></pre>
<pre><span style="color:#888888">be similar to this PR (recently merged) which implemented support for<o:p></o:p></span></pre>
<pre><span style="color:#888888">authentication against LDAP:<o:p></o:p></span></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=">https://github.com/thelounge/lounge/pull/477</a> ..<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">In conversation with the lounge devs on IRC they've indicated they<o:p></o:p></span></pre>
<pre><span style="color:#888888">would welcome this work, so I don't anticipate any major issues<o:p></o:p></span></pre>
<pre><span style="color:#888888">getting the code accepted. They're pretty responsive with<o:p></o:p></span></pre>
<pre><span style="color:#888888">contributors and have been really friendly in my experience. Let me<o:p></o:p></span></pre>
<pre><span style="color:#888888">know if you have questions, and if there's anything more I can to do<o:p></o:p></span></pre>
<pre><span style="color:#888888">help coordinate this.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">-Christopher<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#888888">Christopher Aedo<o:p></o:p></span></pre>
<pre><span style="color:#888888">September 7, 2016 at 2:34 AM<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">On Mon, Sep 5, 2016 at 3:24 PM, Blair Bethwaite<o:p></o:p></span></pre>
<pre><span style="color:#888888"><a href="mailto:blair.bethwaite@monash.edu"><blair.bethwaite@monash.edu></a> wrote:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Hi Flanders,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Great discussion. Prompted me to go remind myself of the role and/or<o:p></o:p></span></pre>
<pre><span style="color:#888888">definition of an OS UC Working Group... I didn't find anything "formal", but<o:p></o:p></span></pre>
<pre><span style="color:#888888">w.o.o/UserCommittee says:<o:p></o:p></span></pre>
<pre><span style="color:#888888">=====<o:p></o:p></span></pre>
<pre><span style="color:#888888">The user committee's role is to represent the needs of the diverse range of<o:p></o:p></span></pre>
<pre><span style="color:#888888">OpenStack users. The user committee is advised by Working Groups, each of<o:p></o:p></span></pre>
<pre><span style="color:#888888">whom represents different user audiences and interests.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The user committee mission is to:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Consolidate user requirements and present these to the management board and<o:p></o:p></span></pre>
<pre><span style="color:#888888">technical committee[1].<o:p></o:p></span></pre>
<pre><span style="color:#888888">Provide guidance for the development teams where user feedback is requested<o:p></o:p></span></pre>
<pre><span style="color:#888888">Track OpenStack deployments and usage, helping to share user stories and<o:p></o:p></span></pre>
<pre><span style="color:#888888">experiences<o:p></o:p></span></pre>
<pre><span style="color:#888888">Work with the user groups worldwide to keep the OpenStack community vibrant<o:p></o:p></span></pre>
<pre><span style="color:#888888">and informed<o:p></o:p></span></pre>
<pre><span style="color:#888888">=====<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">>From the WG activity perspective I would highlight it is very<o:p></o:p></span></pre>
<pre><span style="color:#888888">useful/important to have some direction (as well as support) coming from the<o:p></o:p></span></pre>
<pre><span style="color:#888888">UC - I think our experience with the scientific-wg is roughly that we have a<o:p></o:p></span></pre>
<pre><span style="color:#888888">large interest base and plenty of people who find good value in talking to<o:p></o:p></span></pre>
<pre><span style="color:#888888">and sharing with their peers, but it is quite hard to turn that into<o:p></o:p></span></pre>
<pre><span style="color:#888888">concrete forward momentum or to even mint well articulated goals from within<o:p></o:p></span></pre>
<pre><span style="color:#888888">the group.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">On engagement, IRC is useful for reasons already mentioned in this thread<o:p></o:p></span></pre>
<pre><span style="color:#888888">(and we've been fortunate to have some valuable interactions thanks some<o:p></o:p></span></pre>
<pre><span style="color:#888888">core devs having keyword watches setup on OpenStack channels), but I think<o:p></o:p></span></pre>
<pre><span style="color:#888888">we alienate and/or make things too hard for some potential contributors. And<o:p></o:p></span></pre>
<pre><span style="color:#888888">I don't think it makes a great watercooler discussion tool (e.g. no offline<o:p></o:p></span></pre>
<pre><span style="color:#888888">history etc without setting up a bouncer - and that is fairly opaque even<o:p></o:p></span></pre>
<pre><span style="color:#888888">for a CS major).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">I'm a huge fan of the way we use IRC in the OpenStack community, but<o:p></o:p></span></pre>
<pre><span style="color:#888888">have also recognized getting up and running with a persistent IRC<o:p></o:p></span></pre>
<pre><span style="color:#888888">connection can pose a significant barrier to many very smart and<o:p></o:p></span></pre>
<pre><span style="color:#888888">technically sharp humans. To that end I wrote a spec to provide a<o:p></o:p></span></pre>
<pre><span style="color:#888888">hosted, persistent IRC web-client [1]. Lately however the effort has<o:p></o:p></span></pre>
<pre><span style="color:#888888">been stalled due to my lack of experience with JS; if we can find<o:p></o:p></span></pre>
<pre><span style="color:#888888">someone who can plumb in the auth piece, we could be up and running<o:p></o:p></span></pre>
<pre><span style="color:#888888">with this fairly quickly.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">I think getting that right will be worth the effort, and could get a<o:p></o:p></span></pre>
<pre><span style="color:#888888">whole lot more people engaged across all our various domains.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></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=">https://review.openstack.org/319506</a><o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">-Christopher<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Having (myself) done a fairly woeful job of keeping pace with the dev side<o:p></o:p></span></pre>
<pre><span style="color:#888888">of OS progression this cycle I'm also interested in exploring ways of<o:p></o:p></span></pre>
<pre><span style="color:#888888">highlighting activities/work that may be of interest to any particular WG.<o:p></o:p></span></pre>
<pre><span style="color:#888888">The first thing that springs to mind is tagging of blueprints and reviews,<o:p></o:p></span></pre>
<pre><span style="color:#888888">e.g., where a dev or other community member is looking for<o:p></o:p></span></pre>
<pre><span style="color:#888888">input/support/resolution from a specific target user group. This could be a<o:p></o:p></span></pre>
<pre><span style="color:#888888">mechanism we as chairs utilise to surface agenda items, solicit input and<o:p></o:p></span></pre>
<pre><span style="color:#888888">then respond on behalf of the group.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Cheers,<o:p></o:p></span></pre>
<pre><span style="color:#888888">Blair<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">On 30 August 2016 at 10:36, David F Flanders <a href="mailto:flanders@openstack.org"><flanders@openstack.org></a> wrote:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Dear Working Group Co-Chairs and User Committee Chairs,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,<o:p></o:p></span></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly<o:p></o:p></span></pre>
<pre><span style="color:#888888">basis to run a global meeting:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe<o:p></o:p></span></pre>
<pre><span style="color:#888888">members)<o:p></o:p></span></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad<o:p></o:p></span></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda<o:p></o:p></span></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is<o:p></o:p></span></pre>
<pre><span style="color:#888888">occurring along with agenda links<o:p></o:p></span></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)<o:p></o:p></span></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well<o:p></o:p></span></pre>
<pre><span style="color:#888888">taken notes if via voice)<o:p></o:p></span></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting<o:p></o:p></span></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for<o:p></o:p></span></pre>
<pre><span style="color:#888888">consideration, etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888">h.) follow up actions.<o:p></o:p></span></pre>
<pre><span style="color:#888888">i.) recruit new members<o:p></o:p></span></pre>
<pre><span style="color:#888888">j.) plan for summit meetings<o:p></o:p></span></pre>
<pre><span style="color:#888888">k.) etc etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an<o:p></o:p></span></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and<o:p></o:p></span></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some<o:p></o:p></span></pre>
<pre><span style="color:#888888">of their massive communities.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Other options include:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing<o:p></o:p></span></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one<o:p></o:p></span></pre>
<pre><span style="color:#888888">after another).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create<o:p></o:p></span></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging<o:p></o:p></span></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may<o:p></o:p></span></pre>
<pre><span style="color:#888888">be?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Kind Regards,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Flanders<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">--<o:p></o:p></span></pre>
<pre><span style="color:#888888">Blair Bethwaite<o:p></o:p></span></pre>
<pre><span style="color:#888888">Senior HPC Consultant<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Monash eResearch Centre<o:p></o:p></span></pre>
<pre><span style="color:#888888">Monash University<o:p></o:p></span></pre>
<pre><span style="color:#888888">Room G26, 15 Innovation Walk, Clayton Campus<o:p></o:p></span></pre>
<pre><span style="color:#888888">Clayton VIC 3800<o:p></o:p></span></pre>
<pre><span style="color:#888888">Australia<o:p></o:p></span></pre>
<pre><span style="color:#888888">Mobile: 0439-545-002<o:p></o:p></span></pre>
<pre><span style="color:#888888">Office: +61 3-9903-2800<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:#888888">User-committee mailing list<o:p></o:p></span></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><o:p></o:p></span></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=">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:#888888">User-committee mailing list<o:p></o:p></span></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><o:p></o:p></span></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=">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Blair Bethwaite<o:p></o:p></span></pre>
<pre><span style="color:#888888">September 5, 2016 at 5:24 PM<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Hi Flanders,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Great discussion. Prompted me to go remind myself of the role and/or<o:p></o:p></span></pre>
<pre><span style="color:#888888">definition of an OS UC Working Group... I didn't find anything "formal", but<o:p></o:p></span></pre>
<pre><span style="color:#888888">w.o.o/UserCommittee says:<o:p></o:p></span></pre>
<pre><span style="color:#888888">=====<o:p></o:p></span></pre>
<pre><span style="color:#888888">The user committee's role is to represent the needs of the diverse range of<o:p></o:p></span></pre>
<pre><span style="color:#888888">OpenStack users. The user committee is advised by Working Groups, each of<o:p></o:p></span></pre>
<pre><span style="color:#888888">whom represents different user audiences and interests.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The user committee mission is to:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Consolidate user requirements and present these to the management board and<o:p></o:p></span></pre>
<pre><span style="color:#888888">technical committee[1].<o:p></o:p></span></pre>
<pre><span style="color:#888888">Provide guidance for the development teams where user feedback is requested<o:p></o:p></span></pre>
<pre><span style="color:#888888">Track OpenStack deployments and usage, helping to share user stories and<o:p></o:p></span></pre>
<pre><span style="color:#888888">experiences<o:p></o:p></span></pre>
<pre><span style="color:#888888">Work with the user groups worldwide to keep the OpenStack community vibrant<o:p></o:p></span></pre>
<pre><span style="color:#888888">and informed<o:p></o:p></span></pre>
<pre><span style="color:#888888">=====<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">>From the WG activity perspective I would highlight it is very<o:p></o:p></span></pre>
<pre><span style="color:#888888">useful/important to have some direction (as well as support) coming from the<o:p></o:p></span></pre>
<pre><span style="color:#888888">UC - I think our experience with the scientific-wg is roughly that we have a<o:p></o:p></span></pre>
<pre><span style="color:#888888">large interest base and plenty of people who find good value in talking to<o:p></o:p></span></pre>
<pre><span style="color:#888888">and sharing with their peers, but it is quite hard to turn that into<o:p></o:p></span></pre>
<pre><span style="color:#888888">concrete forward momentum or to even mint well articulated goals from within<o:p></o:p></span></pre>
<pre><span style="color:#888888">the group.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">On engagement, IRC is useful for reasons already mentioned in this thread<o:p></o:p></span></pre>
<pre><span style="color:#888888">(and we've been fortunate to have some valuable interactions thanks some<o:p></o:p></span></pre>
<pre><span style="color:#888888">core devs having keyword watches setup on OpenStack channels), but I think<o:p></o:p></span></pre>
<pre><span style="color:#888888">we alienate and/or make things too hard for some potential contributors. And<o:p></o:p></span></pre>
<pre><span style="color:#888888">I don't think it makes a great watercooler discussion tool (e.g. no offline<o:p></o:p></span></pre>
<pre><span style="color:#888888">history etc without setting up a bouncer - and that is fairly opaque even<o:p></o:p></span></pre>
<pre><span style="color:#888888">for a CS major).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Having (myself) done a fairly woeful job of keeping pace with the dev side<o:p></o:p></span></pre>
<pre><span style="color:#888888">of OS progression this cycle I'm also interested in exploring ways of<o:p></o:p></span></pre>
<pre><span style="color:#888888">highlighting activities/work that may be of interest to any particular WG.<o:p></o:p></span></pre>
<pre><span style="color:#888888">The first thing that springs to mind is tagging of blueprints and reviews,<o:p></o:p></span></pre>
<pre><span style="color:#888888">e.g., where a dev or other community member is looking for<o:p></o:p></span></pre>
<pre><span style="color:#888888">input/support/resolution from a specific target user group. This could be a<o:p></o:p></span></pre>
<pre><span style="color:#888888">mechanism we as chairs utilise to surface agenda items, solicit input and<o:p></o:p></span></pre>
<pre><span style="color:#888888">then respond on behalf of the group.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Cheers,<o:p></o:p></span></pre>
<pre><span style="color:#888888">Blair<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">On 30 August 2016 at 10:36, David F Flanders <a href="mailto:flanders@openstack.org"><flanders@openstack.org></a> wrote:<o:p></o:p></span></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,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,<o:p></o:p></span></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly<o:p></o:p></span></pre>
<pre><span style="color:#888888">basis to run a global meeting:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe<o:p></o:p></span></pre>
<pre><span style="color:#888888">members)<o:p></o:p></span></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad<o:p></o:p></span></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda<o:p></o:p></span></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is<o:p></o:p></span></pre>
<pre><span style="color:#888888">occurring along with agenda links<o:p></o:p></span></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)<o:p></o:p></span></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well<o:p></o:p></span></pre>
<pre><span style="color:#888888">taken notes if via voice)<o:p></o:p></span></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting<o:p></o:p></span></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for<o:p></o:p></span></pre>
<pre><span style="color:#888888">consideration, etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888">h.) follow up actions.<o:p></o:p></span></pre>
<pre><span style="color:#888888">i.) recruit new members<o:p></o:p></span></pre>
<pre><span style="color:#888888">j.) plan for summit meetings<o:p></o:p></span></pre>
<pre><span style="color:#888888">k.) etc etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an<o:p></o:p></span></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and<o:p></o:p></span></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some<o:p></o:p></span></pre>
<pre><span style="color:#888888">of their massive communities.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Other options include:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing<o:p></o:p></span></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one<o:p></o:p></span></pre>
<pre><span style="color:#888888">after another).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create<o:p></o:p></span></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging<o:p></o:p></span></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may<o:p></o:p></span></pre>
<pre><span style="color:#888888">be?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Kind Regards,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Flanders<o:p></o:p></span></pre>
</blockquote>
<pre><span style="color:#888888">--<o:p></o:p></span></pre>
<pre><span style="color:#888888">Blair Bethwaite<o:p></o:p></span></pre>
<pre><span style="color:#888888">Senior HPC Consultant<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Monash eResearch Centre<o:p></o:p></span></pre>
<pre><span style="color:#888888">Monash University<o:p></o:p></span></pre>
<pre><span style="color:#888888">Room G26, 15 Innovation Walk, Clayton Campus<o:p></o:p></span></pre>
<pre><span style="color:#888888">Clayton VIC 3800<o:p></o:p></span></pre>
<pre><span style="color:#888888">Australia<o:p></o:p></span></pre>
<pre><span style="color:#888888">Mobile: 0439-545-002<o:p></o:p></span></pre>
<pre><span style="color:#888888">Office: +61 3-9903-2800<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:#888888">User-committee mailing list<o:p></o:p></span></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><o:p></o:p></span></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=">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></span></pre>
<pre><span style="color:#888888">David F Flanders<o:p></o:p></span></pre>
<pre><span style="color:#888888">August 29, 2016 at 7:36 PM<o:p></o:p></span></pre>
<pre><span style="color:#888888">Dear Working Group Co-Chairs and User Committee Chairs,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">The logistical tasks of running a WG meeting is by no means trivial,<o:p></o:p></span></pre>
<pre><span style="color:#888888">here a quick list of things which a co-chairs of a WG do on a weekly<o:p></o:p></span></pre>
<pre><span style="color:#888888">basis to run a global meeting:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">a.) mint calendar invitation to all members (subscribe/unsubscribe members)<o:p></o:p></span></pre>
<pre><span style="color:#888888">b.) call for agenda items via etherpad<o:p></o:p></span></pre>
<pre><span style="color:#888888">c.) update wiki with upcoming meeting and link to etherpad agenda<o:p></o:p></span></pre>
<pre><span style="color:#888888">d.) email user-committee mailing list on when next meeting is<o:p></o:p></span></pre>
<pre><span style="color:#888888">occurring along with agenda links<o:p></o:p></span></pre>
<pre><span style="color:#888888">e.) assure meeting channel is confirmed (irc/phone/etc)<o:p></o:p></span></pre>
<pre><span style="color:#888888">f.) run meeting according to good practices (irc etiquette or well<o:p></o:p></span></pre>
<pre><span style="color:#888888">taken notes if via voice)<o:p></o:p></span></pre>
<pre><span style="color:#888888">g.) post meeting follow up: circulating actions, posting meeting<o:p></o:p></span></pre>
<pre><span style="color:#888888">notes, taking any outstanding queries to the mailing list for<o:p></o:p></span></pre>
<pre><span style="color:#888888">consideration, etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888">h.) follow up actions.<o:p></o:p></span></pre>
<pre><span style="color:#888888">i.) recruit new members<o:p></o:p></span></pre>
<pre><span style="color:#888888">j.) plan for summit meetings<o:p></o:p></span></pre>
<pre><span style="color:#888888">k.) etc etc.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">All of the above are sometimes done twice-over at different times to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help maintain the conversation in different timezones.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">In addition, the groups are still not well attended by as diverse an<o:p></o:p></span></pre>
<pre><span style="color:#888888">audience as OpenStack represents. AsiaPac, Latin America, India and<o:p></o:p></span></pre>
<pre><span style="color:#888888">other massive OpenStack user groups have not yet engaged despite some<o:p></o:p></span></pre>
<pre><span style="color:#888888">of their massive communities.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">One of the recent suggestions has been to converge some of the WGs to<o:p></o:p></span></pre>
<pre><span style="color:#888888">help ease the burden of these logistical tasks.<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Other options include:<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a more systematic approach to when WG occur, i.e. agreeing<o:p></o:p></span></pre>
<pre><span style="color:#888888">a set pattern such s a day per fortnight which each WG happens (one<o:p></o:p></span></pre>
<pre><span style="color:#888888">after another).<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* having a shared IRC channel for all WG activity to help create<o:p></o:p></span></pre>
<pre><span style="color:#888888">more water-cooler conversation between chairs?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">* sharing of logistical duties between WG chairs, etc<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Options abound, though discussion much needed!<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Q: Is there any good practice we can draw from? I've been digging<o:p></o:p></span></pre>
<pre><span style="color:#888888">around my old W3C and IETF notes to see what good practice there may<o:p></o:p></span></pre>
<pre><span style="color:#888888">be?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Discussion/replies greatly appreciated to see if there is any consensus?<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Kind Regards,<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">Flanders<o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color:#888888">User-committee mailing list<o:p></o:p></span></pre>
<pre><span style="color:#888888"><a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><o:p></o:p></span></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=">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><o:p></o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
<pre><span style="color:#888888"><o:p> </o:p></span></pre>
</blockquote>
</div>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>