Hi Libvirt team, A number of opensource projects have weekly meetings between their community of contributors to facilitate their day-to-day working and particularly to resolve roadblocks that people are having. I feel that libvirt is large enough, with contributors from many different organizations, that a meeting could be beneficial to our operation. This could serve a number of purposes - Remind us of patches that have been posted and accidentally forgotten by reviewers - Resolve hard debates that are not making adequate progress on the mailing list(s) - Track progress of major ongoing pieces of work with many collaborators - Forum for those new to the community to introduce themselves & their ideas before starting work - Discuss release critical bugs during freeze periods - Place for downstream users of libvirt (eg openstack/ovirt/etc) to interact with libvirt team. - Place for projects we use (eg KVM, Xen) to interact with libvirt team. I like to keep the overhead of this low, so I'd suggest we try todo it on IRC, since that has been fairly effective for OpenStack teams. If people think this is worth while I'd suggest an arbitrary time of 1500 UTC using the #virt-meeting IRC channel on irc.oftc.net, to last an absolute max of 1 hour. Currently this time point works out as

08:00 San Francisco 11:00 Boston 15:00 UTC 16:00 London 17:00 Berlin 20:30 Mumbai 23:00 Bejing 24:00 Tokyo http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&a...

Daniel P. Berrange wrote: > On Fri, May 16, 2014 at 01:53:50PM -0400, Daniel P. Berrange wrote: > >> Hi Libvirt team, >> >> A number of opensource projects have weekly meetings between their community >> of contributors to facilitate their day-to-day working and particularly >> to resolve roadblocks that people are having. >> >> I feel that libvirt is large enough, with contributors from many different >> organizations, that a meeting could be beneficial to our operation. This >> could serve a number of purposes >> >> - Remind us of patches that have been posted and accidentally forgotten >> by reviewers >> >> - Resolve hard debates that are not making adequate progress on the >> mailing list(s) >> >> - Track progress of major ongoing pieces of work with many collaborators >> >> - Forum for those new to the community to introduce themselves & their >> ideas before starting work >> >> - Discuss release critical bugs during freeze periods >> >> - Place for downstream users of libvirt (eg openstack/ovirt/etc) to >> interact with libvirt team. >> >> - Place for projects we use (eg KVM, Xen) to interact with libvirt >> team. >> >> I like to keep the overhead of this low, so I'd suggest we try todo it >> on IRC, since that has been fairly effective for OpenStack teams. >> >> If people think this is worth while I'd suggest an arbitrary time of >> 1500 UTC using the #virt-meeting IRC channel on irc.oftc.net, to last an >> absolute max of 1 hour. Currently this time point works out as >> > > Opps, missd the day - I was meaning to suggest > > *1500 UTC on thursdays* > Thanks Daniel. I think this is a great idea, and unlike the similar proposal you made for a nova libvirt sub-team meeting, I'm available during this time slot. Well, with the exception of this week. Were you planning the first meeting this Thursday, as in May 22nd?

Hi Libvirt team, A number of opensource projects have weekly meetings between their community of contributors to facilitate their day-to-day working and particularly to resolve roadblocks that people are having. I feel that libvirt is large enough, with contributors from many different organizations, that a meeting could be beneficial to our operation. This could serve a number of purposes - Remind us of patches that have been posted and accidentally forgotten by reviewers - Resolve hard debates that are not making adequate progress on the mailing list(s) - Track progress of major ongoing pieces of work with many collaborators - Forum for those new to the community to introduce themselves & their ideas before starting work - Discuss release critical bugs during freeze periods - Place for downstream users of libvirt (eg openstack/ovirt/etc) to interact with libvirt team. - Place for projects we use (eg KVM, Xen) to interact with libvirt team. I like to keep the overhead of this low, so I'd suggest we try todo it on IRC, since that has been fairly effective for OpenStack teams. If people think this is worth while I'd suggest an arbitrary time of 1500 UTC using the #virt-meeting IRC channel on irc.oftc.net, to last an absolute max of 1 hour. Currently this time point works out as 08:00 San Francisco 11:00 Boston 15:00 UTC 16:00 London 17:00 Berlin 20:30 Mumbai 23:00 Bejing 24:00 Tokyo http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&a...

Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

On 05/16/2014 11:53 AM, Daniel P. Berrange wrote: > > If people think this is worth while I'd suggest an arbitrary time of > 1500 UTC using the #virt-meeting IRC channel on irc.oftc.net, to last an > absolute max of 1 hour. Currently this time point works out as Is this tied to true UTC (no daylight savings, so everyone living in a timezone with daylight savings has to adjust their local start time twice a year) or to a particular timezone (where some people always have the same local time, while other unlucky folks might have to adjust their own start time as many as 4 times a year because of differences between daylight savings cutoff points)?

I'm definitely in favor of the idea. However, in my personal situation, starting an hour earlier (1400 UTC) would fit a bit better for Thursday meetings. That's because I generally try to attend Austin Group teleconferences [the standards body in charge of POSIX] which are also Thursdays currently at 1500 UTC (but tied to US daylight savings rules); and my close involvement with POSIX has come in handy for libvirt more than once. I've got more flexibility if we pick a different day of the week.