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