[openstack-dev] meeting times and rotations etc...
So, I'm a little worried about the complexities of organising free slots given we're basically about to double the # of entrieshave in all our calendars. Maybe we can do something a little simpler: just have the *whole calender* shift phase 180' each week: it won't be perfect, particularly for those projects that currently have a majority of members meeting in the middle of their day (12 midday - 12 midnight), but if there's any decent spread already meeting, there will be a decent spread for the alter week - and an important thing for inclusion is to not be doing votes etc in meetings *anyway* so I think it's ok for the PTL (for instance) to not be at every meeting. Thoughts? -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] meeting times and rotations etc...
Another option would be to use what we already have to our benefit. Instead of trying to provision two meeting rooms (-meeting and -meeting-alt), use the various other IRC channels that we already have for team meetings. This would allow for meetings to be at the same time, but it would free up more time slots to be scheduled, and those time slots can be scheduled more precisely to fit the schedules of those attending. So what about cross-team concerns? We have the weekly meeting, and if that isn't sufficient, then the -meeting and -meeting-alt channels can be scheduled for cross-team needs. --John On Dec 19, 2013, at 1:20 AM, Robert Collins robe...@robertcollins.net wrote: So, I'm a little worried about the complexities of organising free slots given we're basically about to double the # of entrieshave in all our calendars. Maybe we can do something a little simpler: just have the *whole calender* shift phase 180' each week: it won't be perfect, particularly for those projects that currently have a majority of members meeting in the middle of their day (12 midday - 12 midnight), but if there's any decent spread already meeting, there will be a decent spread for the alter week - and an important thing for inclusion is to not be doing votes etc in meetings *anyway* so I think it's ok for the PTL (for instance) to not be at every meeting. Thoughts? -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Message signed with OpenPGP using GPGMail ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] meeting times and rotations etc...
On 19/12/13 01:28 -0800, John Dickinson wrote: Another option would be to use what we already have to our benefit. Instead of trying to provision two meeting rooms (-meeting and -meeting-alt), use the various other IRC channels that we already have for team meetings. This would allow for meetings to be at the same time, but it would free up more time slots to be scheduled, and those time slots can be scheduled more precisely to fit the schedules of those attending. So what about cross-team concerns? We have the weekly meeting, and if that isn't sufficient, then the -meeting and -meeting-alt channels can be scheduled for cross-team needs. +1 I was thinking the exact same thing while reading Robert's email. I guess we should also consider new projects that don't have a channel yet. Just as you mentioned, they could use -meeting or -meeting-alt. Marconi's team has had several 'extra' meetings - mostly for brainstorming about a specific argument - in #openstack-marconi. All this meetings where announced properly and worked just fine. We've done the same for Glance. I'd like to add that, although I prefer keeping the meetings short, there are times where 1h may not be enough and people end up using other team's time or dropping the meeting. Using the project's channel should help with this as well. Cheers, FF --John On Dec 19, 2013, at 1:20 AM, Robert Collins robe...@robertcollins.net wrote: So, I'm a little worried about the complexities of organising free slots given we're basically about to double the # of entrieshave in all our calendars. Maybe we can do something a little simpler: just have the *whole calender* shift phase 180' each week: it won't be perfect, particularly for those projects that currently have a majority of members meeting in the middle of their day (12 midday - 12 midnight), but if there's any decent spread already meeting, there will be a decent spread for the alter week - and an important thing for inclusion is to not be doing votes etc in meetings *anyway* so I think it's ok for the PTL (for instance) to not be at every meeting. Thoughts? -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- @flaper87 Flavio Percoco pgpbi1gy9OB8q.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] meeting times and rotations etc...
Robert Collins wrote: So, I'm a little worried about the complexities of organising free slots given we're basically about to double the # of entrieshave in all our calendars. I don't think that's what we are about to do, as I don't expect every single meeting to implement a rotation. As I said in another thread: Rotating meetings are not a magic bullet: unless your contributors are evenly distributed on the planet, you end up alienating your regular contributors and slowing down the pace of your core team... sometimes for no obvious gain. One option is to keep your regular weekly meeting, but then throw an *additional* meeting in alternate timezone(s) every month to take the pulse of the devs you have there. That would also let you gauge the need for a more regular meeting, or truly alternating meeting times. All that without impacting your regular velocity, and not being too much of a pain. So I would not just shift the whole calendar each week because that assumes that rotating meetings are good for everyone. I don't expect a few meeting rotating times to create that many scheduling headaches (since the Europe/APAC-friendly meeting slots are not used that much currently !). If the number of meeting channels really becomes a problem we could explore John's proposed solution (enabling the meeting bot on topical channels and have some meetings there). Cheers, -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] meeting times and rotations etc...
On 12/19/2013 04:28 AM, John Dickinson wrote: Another option would be to use what we already have to our benefit. Instead of trying to provision two meeting rooms (-meeting and -meeting-alt), use the various other IRC channels that we already have for team meetings. This would allow for meetings to be at the same time, but it would free up more time slots to be scheduled, and those time slots can be scheduled more precisely to fit the schedules of those attending. So what about cross-team concerns? We have the weekly meeting, and if that isn't sufficient, then the -meeting and -meeting-alt channels can be scheduled for cross-team needs. I'm generally -1 to this. I idle in #openstack-meeting and #openstack-meeting-alt, and periodically go look at what's going on. It also means if someone pings me in a meeting, I'm likely to see it. This level of passive monitoring on the meetings is I think useful. If a particular team wants to take their meetings out of the main channels, so be it, but I think the norm should be to continue to use those channels. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
