Open Stack

On Thu, Dec 4, 2014 at 11:40 AM, marios <marios at redhat.com> wrote:

> On 04/12/14 11:40, James Polley wrote:
> > Just taking a look at http://doodle.com/27ffgkdm5gxzr654 again - we've
> > had 10 people respond so far. The winning time so far is Monday 2100UTC
> > - 7 "yes" and one "If I have to".
>
> for me it currently shows 1200 UTC as the preferred time.
>

You're the 11th responder :) And yes, 1200/1400/1500 are now all leading
 with 8/0/3.

>
> So to be clear, we are voting here for the alternate meeting. The
> 'original' meeting is at 1900UTC. If in fact 2100UTC ends up being the
> most popular, what would be the point of an alternating meeting that is
> only 2 hours apart in time?
>

To me the point would be to get more people able to come along to the
meeting. But if the difference *was* that small, I'd be wanting to ask if
changing the format or content of the meeting could convince more people to
join the 1900UTC meeting - I think that having just one meeting for the
whole team would be preferable, if we could manage it.

But at present, it looks like if we want to maximise attendance, we should
be focusing on European early afternoon. That unfortunately means that it's
going to be very hard for those of us in Australia/New Zealand/China/Japan
to make it - 1400UTC is 1am Sydney, 10pm Beijing. It's 7:30pm New Delhi,
which might be doable, but I don't know of anyone working there who would
regularly attend.

>
>
>
> >
> > ... but the 2 people who can't make that time work in UTC or CET.
> > Finding a time that includes those people rules out people who work in
> > Eastern Australia and New Zealand. Purely in terms of getting the
> > biggest numbers in, Monday 2100UTC seems like the most workable time so
> far.
> >
>
>
>
> > On Tue, Dec 2, 2014 at 4:25 PM, Derek Higgins <derekh at redhat.com
> > <mailto:derekh at redhat.com>> wrote:
> >
> >     On 02/12/14 15:12, Giulio Fidente wrote:
> >     > On 12/02/2014 03:45 PM, Derek Higgins wrote:
> >     >> On 02/12/14 14:10, James Polley wrote:
> >     >>> Months ago, I pushed for us to alternate meeting times to
> >     something that
> >     >>> was friendlier to me, so we started doing alternate weeks at
> >     0700UTC.
> >     >>> That worked well for me, but wasn't working so well for a few
> >     people in
> >     >>> Europe, so we decided to give 0800UTC a try. Then DST changes
> >     happened,
> >     >>> and wiki pages got out of sync, and there was confusion about
> >     what time
> >     >>> the meeting is at..
> >     >>>
> >     >>> The alternate meeting hasn't been very well attended for the
> last ~3
> >     >>> meetings. Partly I think that's due to summit and travel plans,
> >     but it
> >     >>> seems like the 0800UTC time doesn't work very well for quite a
> few
> >     >>> people.
> >     >>>
> >     >>> So, instead of trying things at random, I've
> >     >>> created
> >     https://etherpad.openstack.org/p/tripleo-alternate-meeting-time
> >     >>> as a starting point for figuring out what meeting time might
> >     work well
> >     >>> for the most people. Obviously the world is round, and people
> have
> >     >>> different schedules, and we're never going to get a meeting time
> >     that
> >     >>> works well for everyone - but it'd be nice to try to maximise
> >     attendance
> >     >>> (and minimise inconvenience) as much as we can.
> >     >>>
> >     >>> If you regularly attend, or would like to attend, the meeting,
> >     please
> >     >>> take a moment to look at the etherpad to register your vote for
> >     which
> >     >>> time works best for you. There's even a section for you to cast
> your
> >     >>> vote if the UTC1900 meeting (aka the "main" or "US-Friendly"
> >     meeting)
> >     >>> works better for you!
> >     >>
> >     >>
> >     >> Can I suggest an alternative data gathering method, I've put each
> >     hour
> >     >> in a week in a poll, for each slot you have 3 options
> >     >
> >     > I think it is great, but would be even better if we could trim it
> to
> >     > just a *single* day and once we agreed on the timeframe, we decide
> on
> >     > the day as that probably won't count much so long as it is a
> weekday I
> >     > suppose
> >
> >     I think leaving the whole week in there is better, some people may
> have
> >     different schedules on different weekdays, me for example ;-)
> >
> >
> >     _______________________________________________
> >     OpenStack-dev mailing list
> >     OpenStack-dev at lists.openstack.org
> >     <mailto:OpenStack-dev at lists.openstack.org>
> >     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141204/1c8925c3/attachment.html>