Open Stack

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 <robertc at 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 <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131219/54996eb7/attachment.pgp>