<div dir="ltr">Agreed that -meeting3 is ok.<div><br></div><div>BTW my main concern is a process of managing overlaps between projects meetings time, that'll harder and harder with increasing number of meeting rooms.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 15, 2014 at 3:32 PM, Flavio Percoco <span dir="ltr"><<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 15/01/14 11:28 +0100, Thierry Carrez wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sergey Lukjanov wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think that in case of adding additional meeting rooms, we'll need to<br>
avoid disparity between them in names. For example, currently we have a<br>
lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll<br>
have #os-meeting-alt-2 then we'll have even less folks there and it'll<br>
be the same like making meeting in project channel.<br>
<br>
So, probably it'll be better to have meeting rooms named<br>
#openstack-meeting-1(or -a?) and etc. and round robin meetings between<br>
this channels.<br>
</blockquote>
<br>
The trick is... renaming channels is hard, especially when 300 people<br>
lurk in one and have their setups pointing to them. I'm not sure the<br>
value of averaging lurking across meeting rooms outweighs the<br>
inconvenience renaming creates for existing users.<br>
<br>
There are already conflicts as people pick times that appear to be free<br>
but are actually used every other week... so a third room is definitely<br>
wanted. We can go and create #openstack-meeting3 (other suggestions<br>
welcome) and then discuss a consistent naming scheme and/or if renaming<br>
is such a good idea.<br>
</blockquote>
<br>
<br></div>
-meeting3 sounds good to me!<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-- <br>
Thierry Carrez (ttx)<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
@flaper87<br>
Flavio Percoco<br>
</font></span><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><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Sincerely yours,</div><div>Sergey Lukjanov</div><div>Savanna Technical Lead</div><div>Mirantis Inc.</div></div>
</div>