Roman: *Since there are two core-subteams located in different time zones I propose making two sessions:* * - One in the morning in Europe. Let's say at 10 GMT* * - One in the morning in the US at a convenient time.*
I like this but it might be confusing to the devs, at least initially. I would vote to moving the initial meeting from 8 to say 8:30 on Thursdays. I say lets talk about split review days in the next meeting? Chris On Wed, Feb 12, 2014 at 2:35 PM, Roman Prykhodchenko < [email protected]> wrote: > Since there are two core-subteams located in different time zones I > propose making two sessions: > - One in the morning in Europe. Let's say at 10 GMT > - One in the morning in the US at a convenient time. > > This approach might be useful for the submitters located in different time > zones. > > > - Roman > > On Feb 13, 2014, at 00:18 , Maksym Lobur <[email protected]> wrote: > > Also, I think 3 hours might be too much, maybe to have 2 sessions of 2 > hours. It might be hard to concentrate on review for 3 hours in a line.. > > Best regards, > Max Lobur, > Python Developer, Mirantis, Inc. > > Mobile: +38 (093) 665 14 28 > Skype: max_lobur > > 38, Lenina ave. Kharkov, Ukraine > www.mirantis.com > www.mirantis.ru > > > On Wed, Feb 12, 2014 at 11:32 PM, Maksym Lobur <[email protected]>wrote: > >> Hi All, >> >> I like the idea! I'm comfortable to reserve about 3 hours for this, >> Thursdays 8am (4pm GMT +0) sounds good. I assume we'll pick and merge as >> much patches as possible during that time, and if the last one doesn't fit >> to the time - we're increasing the time until the patch merged (in >> reasonable limit). Makes sense? >> >> Best regards, >> Max Lobur, >> Python Developer, Mirantis, Inc. >> >> Mobile: +38 (093) 665 14 28 >> Skype: max_lobur >> >> 38, Lenina ave. Kharkov, Ukraine >> www.mirantis.com >> www.mirantis.ru >> >> >> On Wed, Feb 12, 2014 at 11:14 PM, Devananda van der Veen < >> [email protected]> wrote: >> >>> Hi again! >>> >>> I promise this will be a much shorter email than my last one ... :) >>> >>> I'd like to propose that we find regular day/time to have a recurring >>> code jam. Here's what it looks like in my head: >>> - we get at least three core reviewers together >>> - as many non-core folks as show up are welcome, too >>> - we tune out all distractions for a few hours >>> - we pick a patch and all review it >>> >>> If the author is present, we iterate with the author, and review each >>> revision they submit while we're all together. If the author is not present >>> and there are only minor issues, we fix them up in a follow-on patch and >>> land both at once. If neither of those are possible, we -1 it and move on. >>> >>> I think we could make very quick progress in our review queue this way. >>> In particular, I want us to plow through the bug fixes that have been in >>> Fix Proposed status for a while ... >>> >>> What do ya'll think of this idea? Useful or a doomed to fail? >>> >>> What time would work for you? How about Thursdays at 8am PST? >>> >>> >>> Cheers, >>> Devananda >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> [email protected] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
