create new tag
, view all tags

Best Time For Release Meetings

Due to the poor attendance at release meetings we need to revisit the biweekly release meeting schedule.

I am OK with any Monday - Thursday from 18:00 CEST (16:00 GMT) or 18:00 CET (17:00 GMT when not daylight saving time). I cannot chat from work and I am home at 18:00.

I would like the meeting to be over by midnight latest and this means start at 22:00 latest.

I want to avoid Friday and Saturday nights. They are pleasure and not work.

I am OK with any time on Sundays from 11 AM CET to 22:00 CET

I am OK they every 2nd meeting is on another timeslot.

I suggest one Sunday, then one Monday-Thursday, then one Sunday etc

Which weekday is best for you?

What time?

Who is OK to do Sundays?

What time?

Note CEST is Central European Summer Time. CET is Central European Time (Winter). CET is GMT+1. CEST is GMT+2. BST is British Summer Time, GMT+1

Name Best weekday Best start time on weekday incl timezone Sunday OK? Best start time on Sundays
KennethLavrsen Monday - Thursday 18:00 - 22:00 (CEST/CET) Yes 11:00 - 22:00 (CEST/CET)
MarkusUeberall Monday - Friday 19:00 - 22:00 (CEST/CET) Yes 09:00 - 12:00, 15:00 - 22:00 (CEST/CET)
CrawfordCurrie Any 07:00-21:00 Ish, prefer to keep them free 07:00 - 21:00 BST/GMT
MichaelDaum Tuesday, Thursday, Friday 9:00 - 21:00 (CEST/CET) No -
OliverKrueger Any but Tuesday 10.00-22.00 (CE(S)T) Yes 10.00-22.00 (CE(S)T)
SvenDowideit not the same day in a row 10.00-24.00 (Sydney) unlikely unless short & targeted 20.00-24:00 (Sydney)
KoenMartens alternate on some fixed schedule 10.00 - 22.00 ce(s)t rather not -
RafaelAlvarez Any time except Monday and Thursday between 19:00 GMT and 20:00 GMT 20:30 GMT yes 16:00GMT until 2:00GMT on Monday
ArthurClemens Any but Mondays 19:00 GMT yes 16:00GMT until 2:00GMT on Monday
GilmarSantosJr Any but Friday 21:30 - 23:00 GMT rather not, but seldom yes (it will depend on my interest on the subject) Any time between 18:00 - 00:00 GMT

-- Contributors: KennethLavrsen - 17 Sep 2008


As i pointed out in the email that appears to have caused this topic, I think its inappropriate to have a set time - we have over a years evidence that it doesn't work particularly well.

So I propose we try something different - such as when someone thinks a meeting is actually warranted, they can send out an email proposing a time and agenda.

-- SvenDowideit - 17 Sep 2008

I prefer to have regular meetings and predictable time so I can plan my life around it. And I think most people feel this way. At least this is how things normally work in business life and in the political life.

One hour meeting every 2 weeks is not a big burden.

Please everyone incl Sven - add your preferred time for the meeting.

-- KennethLavrsen - 17 Sep 2008

Gentlemen, please find a way to settle this amicably. I have unilaterally deleted the language I found offensive in both your remarks above.

I understand why a regular time works for some people, and I also appreciate the chance to meet up and chat with other project members at a predictable time. But I don't agree with the idea that attendance is in some way compulsory in order to be engaged with the decision-making process. There are many reasons why I can't attend all the regular meetings, however hard I try, and I would really value an alternative approach to focusing all the decision-making in meetings, as Sven suggests.

I would personally prefer that the release meeting, when it happens, is run strictly according to a pre-planned and pre-announced agenda. I have often found that we have been in the position of explaining material that should have been prepped by attendees beforehand, or reviewing bugs that have already been adequately reviewed online. A regular meeting schedule should not be an excuse for laziness and ignoring the online forums. However there are times when a live meeting is necessary, especially in the run up to a release, and when there are hard choices to make.

A predefined time helps avoid the painful necessity of constantly having to find a time when people can attend, and makes it easier for people to plan that timeslot into their schedules.

So, I suggest that you proceed with fixing a meeting schedule - and Sven, your input to that is appreciated, as your remoteness makes it especially hard for you - but also do away with this "we must have a meeting even if we have nothing to discuss" mindset. The release manager(s) should take responsibility for calling release meetings as and when there are decisions to be made.

-- CrawfordCurrie - 17 Sep 2008

I personally prefer a more of less fixed time, but can live with an invitation-based schedule, if the invitation is a few days ahead.

-- OliverKrueger - 17 Sep 2008

Perhaps we can settle with the fixed schedule, but send the invite 4 days ahead so people who want/must to attend cannot can notify it with enough time in advance to move the date.

-- RafaelAlvarez - 17 Sep 2008

My plan is to

Find a time pattern with alternating times so that all has a chance to be at at least half the meetings.

Create the agenda items for many meetings ahead.

Making it a rule that if noone has added anything on the agenda before the meeting starts then there is no meeting.

-- KennethLavrsen - 17 Sep 2008

I put my availability range (not only the start time). Although its an estimative. I'll try hard to attend if the subject interests me and/or if I think I have relevant contributions to give.

-- GilmarSantosJr - 17 Sep 2008

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r13 - 2008-09-17 - GilmarSantosJr
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.