<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Good day everyone,</p>
<p><br>
</p>
<p><br>
</p>
<p>Certainly this would be a great opportunity to have this conversation during the Barcelona Summit</p>
<p><br>
</p>
<p><br>
</p>
<p>A great point to start the conversation would be to touch base on:</p>
<p><br>
</p>
<p>1. How can different WG create the synergy to push each other's activities. </p>
<p><br>
</p>
<p>2. What is the best schema to create teams within each WG</p>
<p><br>
</p>
<p>3. Define an efficient way open communication between WG's teams</p>
<p><br>
</p>
<p><a href="https://wiki.openstack.org/wiki/CloudAppHack-WG" class="OWAAutoLink" id="LPlnk69396">https://wiki.openstack.org/wiki/CloudAppHack-WG</a><br>
<br>
</p>
<p><br>
</p>
<div id="Signature">
<div><span style="font-size:12pt">Best regards,</span></div>
<div><span style="font-size:12pt"><br>
</span></div>
<div><span style="font-size:12pt">Gonzalo De La Torre</span></div>
<div><span style="font-size:12pt"><span style="font-family: Calibri, Arial, Helvetica, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 16px;">Co-President of CloudAppHack-WG</span><br>
</span></div>
<div><span style="font-size:12pt">US: +1 (210) 837-0335</span></div>
<div><span style="font-size:12pt">Skype</span><span style="font-size:12pt">: gonzalo-de-la-torre</span></div>
<div><span style="font-size:12pt">Twitter: </span>@OpenStack_Guy</div>
<div>Google Hangouts: latioz@gmail.com</div>
<div><span style="font-size:12pt">LinkedIn: </span><a href="https://www.linkedin.com/in/gonzaloutsa" target="_blank" style="font-size:12pt" id="LPNoLP">https://www.linkedin.com/in/gonzaloutsa</a></div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> user-committee-request@lists.openstack.org <user-committee-request@lists.openstack.org><br>
<b>Sent:</b> Thursday, September 1, 2016 7:00 AM<br>
<b>To:</b> user-committee@lists.openstack.org<br>
<b>Subject:</b> User-committee Digest, Vol 44, Issue 1</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send User-committee mailing list submissions to<br>
user-committee@lists.openstack.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><br>
or, via email, send a message with subject or body 'help' to<br>
user-committee-request@lists.openstack.org<br>
<br>
You can reach the person managing the list at<br>
user-committee-owner@lists.openstack.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of User-committee digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Efficiency of WGs? (Shamail)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 30 Aug 2016 21:45:53 -0400<br>
From: Shamail <itzshamail@gmail.com><br>
To: "Barrett, Carol L" <carol.l.barrett@intel.com><br>
Cc: Gonzalo De La Torre <gonzalo_delatorre@live.com>, user-committee<br>
<user-committee@lists.openstack.org>, Edgar Magana<br>
<edgar.magana@workday.com>, Stephen Telfer <stig@telfer.org>, David F<br>
Flanders <flanders@openstack.org><br>
Subject: Re: [User-committee] Efficiency of WGs?<br>
Message-ID: <6CC1541A-99D7-486C-9C73-8CD561AF6E8B@gmail.com><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
I agree with all the recommended practices mentioned thus far and I'd be up for a session in Barcelona as well. We could continue discussing tips and also discuss common objectives between working groups with similar focus areas.
<br>
<br>
On the topic of WG meetings, I actually prefer to keep them in the standard OpenStack meeting rooms if possible so that the broader community can jump in when the topic is appropriate (I've had a few times where someone chimed in because their IRC nick was
mentioned while they were idling). <br>
<br>
Side note: I am one of the people who is guilty of just pasting links to the agenda rather than the agenda in meeting notices... I will change that behavior going forward. :)<br>
<br>
Thanks,<br>
Shamail <br>
<br>
> On Aug 30, 2016, at 5:58 PM, Barrett, Carol L <carol.l.barrett@intel.com> wrote:<br>
> <br>
> Good discussion - really appreciate hearing how others are approaching facilitating WG deliverables.<br>
> <br>
> I have a couple of things to add:<br>
> - Establish Goals for each cycle: This can be done at a summit working session or ahead of it. It's important to have group buy-in and ownership.
<br>
> - Define deliverables: For each Goal define 1-3 deliverables. A deliverable must have an owner or it doesn't count. This provides a framework for the teams work over the cycle.<br>
> - Recruiting new members is challenging, but necessary! I'd be interest In hearing who is being successful in this today and what they are doing.<br>
> - Consider having midcycles: This can be with your team or with multiple teams. It keeps people together and making progress. Try to use the midcycle to make progress on deliverables.<br>
> - I think it's good to have 2 co-chairs for a WG. This helps to keep the team moving forward on a regular cadence when your day-job or life gets in the way of attending a meeting.<br>
> - I would like to have the opportunity to meet with the other co-chairs at the Summits and share methodology, plans for the development cycle and get help in addressing challenges. Can we do this in Barcelona?<br>
> <br>
> Carol<br>
> <br>
> -----Original Message-----<br>
> From: Edgar Magana [<a href="mailto:edgar.magana@workday.com">mailto:edgar.magana@workday.com</a>]
<br>
> Sent: Monday, August 29, 2016 7:33 PM<br>
> To: David F Flanders <flanders@openstack.org>; user-committee <user-committee@lists.openstack.org><br>
> Cc: Shamail Tahir <itzshamail@gmail.com>; Montenegro, Patricia <patricia.montenegro@intel.com>; Barrett, Carol L <carol.l.barrett@intel.com>; Michael Jenkins <md.jenkins@icloud.com>; Gonzalo De La Torre <gonzalo_delatorre@live.com>; Michael Krotscheck <krotscheck@gmail.com>;
Stephen Telfer <stig@telfer.org>; Blair Bethwaite <blair.bethwaite@monash.edu><br>
> Subject: Re: Efficiency of WGs?<br>
> <br>
> Flanders,<br>
> <br>
> I really appreciate you have putting this together. It looks good to me but I would like to include that chair and co-chairs should have an active communication with the User Committee (UC) via IRC or email.<br>
> I noticed you have mentioned already posting to the user-committee mailing list but I want to very clear that UC is around to help the WGs to became successful, exactly the same way the TC supports the PTLs.<br>
> <br>
> Edgar<br>
> <br>
> On 8/29/16, 5:36 PM, "David F Flanders" <flanders@openstack.org> 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 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>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
User-committee mailing list<br>
User-committee@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><br>
<br>
<br>
End of User-committee Digest, Vol 44, Issue 1<br>
*********************************************<br>
</div>
</span></font></div>
</div>
</body>
</html>