<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div style="direction: inherit;"><br></div><div><br>On Dec 4, 2016, at 9:47 PM, Tony Breeds <<a href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>On Fri, Dec 02, 2016 at 11:35:05AM +0100, Thierry Carrez wrote:</span><br><blockquote type="cite"><span>Hi everyone,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>There has been a bit of tension lately around creating IRC meetings.</span><br></blockquote><blockquote type="cite"><span>I've been busy[1] cleaning up unused slots and defragmenting biweekly</span><br></blockquote><blockquote type="cite"><span>ones to open up possibilities, but truth is, even with those changes</span><br></blockquote><blockquote type="cite"><span>approved, there will still be a number of time slots that are full:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Tuesday 14utc -- only biweekly available</span><br></blockquote><blockquote type="cite"><span>Tuesday 16utc -- full</span><br></blockquote><blockquote type="cite"><span>Wednesday 15utc -- only biweekly available</span><br></blockquote><blockquote type="cite"><span>Wednesday 16utc -- full</span><br></blockquote><blockquote type="cite"><span>Thursday 14utc -- only biweekly available</span><br></blockquote><blockquote type="cite"><span>Thursday 17utc -- only biweekly available</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>[1] <a href="https://review.openstack.org/#/q/topic:dec2016-cleanup">https://review.openstack.org/#/q/topic:dec2016-cleanup</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Historically, we maintained a limited number of meeting rooms in order</span><br></blockquote><blockquote type="cite"><span>to encourage teams to spread around and limit conflicts. This worked for</span><br></blockquote><blockquote type="cite"><span>a time, but those days I feel like team members don't have that much</span><br></blockquote><blockquote type="cite"><span>flexibility in picking a time that works for everyone. If the miracle</span><br></blockquote><blockquote type="cite"><span>slot that works for everyone is not available on the calendar, they tend</span><br></blockquote><blockquote type="cite"><span>to move the meeting elsewhere (private IRC channel, Slack, Hangouts)</span><br></blockquote><blockquote type="cite"><span>rather than change time to use a less-busy slot.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>So I'm now wondering how much that artificial scarcity policy is hurting</span><br></blockquote><blockquote type="cite"><span>us more than it helps us. I'm still convinced it's very valuable to have</span><br></blockquote><blockquote type="cite"><span>a number of "meetings rooms" that you can lurk in and be available for</span><br></blockquote><blockquote type="cite"><span>pings, without having to join hundreds of channels where meetings might</span><br></blockquote><blockquote type="cite"><span>happen. But I'm not sure anymore that maintaining an artificial scarcity</span><br></blockquote><blockquote type="cite"><span>is helpful in limiting conflicts, and I can definitely see that it</span><br></blockquote><blockquote type="cite"><span>pushes some meetings away from the meeting channels, defeating their</span><br></blockquote><blockquote type="cite"><span>main purpose.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>TL;DR:</span><br></blockquote><span></span><br><span>Shouldn't this have been the headline ;P</span><br><span></span><br><blockquote type="cite"><span>- is it time for us to add #openstack-meeting-5 ?</span><br></blockquote><span></span><br><span>13:38 <tonyb> info #openstack-meeting-5</span><br><span>13:38 -ChanServ(ChanServ@services.)- Information on #openstack-meeting-5:</span><br><span>13:38 -ChanServ(ChanServ@services.)- Founder : Magni, openstackinfra</span><br><span>13:38 -ChanServ(ChanServ@services.)- Successor : freenode-staff</span><br><span>13:38 -ChanServ(ChanServ@services.)- Registered : Nov 27 20:02:51 2015 (1y 1w 1d ago)</span><br><span>13:38 -ChanServ(ChanServ@services.)- Mode lock : +ntc-slk</span><br><span>13:38 -ChanServ(ChanServ@services.)- Flags : GUARD</span><br><span>13:38 -ChanServ(ChanServ@services.)- *** End of Info ***</span><br><span></span><br><span>So if we're going to go down that path it's just a matter of the appropriate</span><br><span>changes in openstack-infra/{system,project}-config</span><br></div></blockquote><div style="direction: inherit;"><br></div><div style="direction: inherit;">I would be for adding at least 1-2 general meeting rooms.</div><blockquote type="cite"><div><span></span><br><blockquote type="cite"><span>- should we more proactively add meeting channels in the future ?</span><br></blockquote><span></span><br><span>In an attempt to get send the worlds most "on the fence" reply. I really like</span><br><span>the current structure, and I think it works well for the parts of the community that</span><br><span>touch lots of projects. Having said that in my not very scientific opionion</span><br><span>that's a very small amount of the community. I think that most contributors</span><br><span>would benefit from moving the meetings into $project specific rooms as Amrith,</span><br><span>Matt and (kinda sorta) Daniel suggested.</span><br></div></blockquote><div style="direction: inherit;"><br></div><div style="direction: inherit;">Do we know how many of the project level rooms currently have bots? I know I ran into an issue that one of the bots was at its maximum (128 rooms) and, therefore, I concerned about the infrastructure necessary to support too many new rooms if there is a new wave of changes to add bots.</div><blockquote type="cite"><div><span></span><br><span>Yours Tony.</span><br></div></blockquote><blockquote type="cite"><div><span>__________________________________________________________________________</span><br><span>OpenStack Development Mailing List (not for usage questions)</span><br><span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></blockquote></body></html>