<div dir="ltr">Hangouts worked well at the nova mid-cycle meetup. Just make sure you have your network situation sorted out before hand. Bandwidth and firewalls are what comes to mind immediately.<div><br></div><div>-Mike</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 9:34 AM, Tom Creighton <span dir="ltr"><<a href="mailto:tom.creighton@rackspace.com" target="_blank">tom.creighton@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When the Designate team had their mini-summit, they had an open Google Hangout for remote participants. We could even have an open conference bridge if you are not partial to video conferencing. With the issue of inclusion solved, let’s focus on a date that is good for the team!<br>
<br>
Cheers,<br>
<br>
Tom Creighton<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Mar 10, 2014, at 4:10 PM, Edgar Magana <<a href="mailto:emagana@plumgrid.com">emagana@plumgrid.com</a>> wrote:<br>
<br>
> Eugene,<br>
><br>
> A have a few arguments why I believe this is not 100% inclusive<br>
> • Is the foundation involved on this process? How? What is the budget? Who is the responsible from the foundation side?<br>
> • If somebody made already travel arraignments, it won't be possible to make changes at not cost.<br>
> • Staying extra days in a different city could impact anyone's budget<br>
> • As a OpenStack developer. I want to understand why the summit is not enough for deciding the next steps for each project. If that is the case, I would prefer to make changes on the organization of the summit instead of creating mini-summits all around!<br>
> I could continue but I think these are good enough.<br>
><br>
> I could agree with your point about previous summits being distractive for developers, this is why this time the OpenStack foundation is trying very hard to allocate specific days for the conference and specific days for the summit.<br>
> The point that I am totally agree with you is that we SHOULD NOT have session about work that will be done no matter what! Those are just a waste of good time that could be invested in very interesting discussions about topics that are still not clear.<br>
> I would recommend that you express this opinion to Mark. He is the right guy to decide which sessions will bring interesting discussions and which ones will be just a declaration of intents.<br>
><br>
> Thanks,<br>
><br>
> Edgar<br>
><br>
> From: Eugene Nikanorov <<a href="mailto:enikanorov@mirantis.com">enikanorov@mirantis.com</a>><br>
> Reply-To: OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Date: Monday, March 10, 2014 10:32 AM<br>
> To: OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?<br>
><br>
> Hi Edgar,<br>
><br>
> I'm neutral to the suggestion of mini summit at this point.<br>
> Why do you think it will exclude developers?<br>
> If we keep it 1-3 days prior to OS Summit in Atlanta (e.g. in the same city) that would allow anyone who joins OS Summit to save on extra travelling.<br>
> OS Summit itself is too distractive to have really productive discussions, unless your missing the sessions and spend time discussing.<br>
> For instance design sessions basically only good for declaration of intents, but not for real discussion of a complex topic at meaningful detail level.<br>
><br>
> What would be your suggestions to make this more inclusive?<br>
> I think the time and place is the key here - hence Atlanta and few days prior OS summit.<br>
><br>
> Thanks,<br>
> Eugene.<br>
><br>
><br>
><br>
> On Mon, Mar 10, 2014 at 10:59 PM, Edgar Magana <<a href="mailto:emagana@plumgrid.com">emagana@plumgrid.com</a>> wrote:<br>
>> Team,<br>
>><br>
>> I found that having a mini-summit with a very short notice means excluding<br>
>> a lot of developers of such an interesting topic for Neutron.<br>
>> The OpenStack summit is the opportunity for all developers to come<br>
>> together and discuss the next steps, there are many developers that CAN<br>
>> NOT afford another trip for a "special" summit. I am personally against<br>
>> that and I do support Mark's proposal of having all the conversation over<br>
>> IRC and mailing list.<br>
>><br>
>> Please, do not start excluding people that won't be able to attend another<br>
>> face-to-face meeting besides the summit. I believe that these are the<br>
>> little things that make an open source community weak if we do not control<br>
>> it.<br>
>><br>
>> Thanks,<br>
>><br>
>> Edgar<br>
>><br>
>><br>
>> On 3/6/14 9:51 PM, "Mark McClain" <<a href="mailto:mmcclain@yahoo-inc.com">mmcclain@yahoo-inc.com</a>> wrote:<br>
>><br>
>> ><br>
>> >On Mar 6, 2014, at 4:31 PM, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
>> ><br>
>> >> On Thu, 2014-03-06 at 21:14 +0000, Youcef Laribi wrote:<br>
>> >>> +1<br>
>> >>><br>
>> >>> I think if we can have it before the Juno summit, we can take<br>
>> >>> concrete, well thought-out proposals to the community at the summit.<br>
>> >><br>
>> >> Unless something has changed starting at the Hong Kong design summit<br>
>> >> (which unfortunately I was not able to attend), the design summits have<br>
>> >> always been a place to gather to *discuss* and *debate* proposed<br>
>> >> blueprints and design specs. It has never been about a gathering to<br>
>> >> rubber-stamp proposals that have already been hashed out in private<br>
>> >> somewhere else.<br>
>> ><br>
>> >You are correct that is the goal of the design summit. While I do think<br>
>> >it is wise to discuss the next steps with LBaaS at this point in time, I<br>
>> >am not a proponent of in person mini-design summits. Many contributors<br>
>> >to LBaaS are distributed all over the global, and scheduling a mini<br>
>> >summit with short notice will exclude valuable contributors to the team.<br>
>> >Iąd prefer to see an open process with discussions on the mailing list<br>
>> >and specially scheduled IRC meetings to discuss the ideas.<br>
>> ><br>
>> >mark<br>
>> ><br>
>> ><br>
>> >_______________________________________________<br>
>> >OpenStack-dev mailing list<br>
>> ><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> ><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> _______________________________________________ OpenStack-dev mailing list <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>