Setup a codereview hour for non american people
Closed, ResolvedPublic
Actions

Description

Current situation: The Code review hour is at 20:00 UTC (22 CEST), which allows not all people to take part. We have for example the train some hours before, and it is too late for some non american people (or to early). Finding a friendly time window for those people would solve this problem. So please tell us, at which time you are able to take part, so that we can find a good window for the majority, that we can create a second window.

Related Objects

Mentioned In: E478: Code Review Office Hours
E387: Code Review Office Hours
E480: Code Review Office Hours
E479: Code Review Office Hours
E317: Code Review Office Hours
E304: Code Review Office Hours
E318: Code Review Office Hours
E257: Code Review Office Hours
E248: Code Review Office Hours
E206: Code Review Office Hours
E249: Code Review Office Hours
T128371: Set up Code Review office hours
Mentioned Here: E206: Code Review Office Hours
E205: Code Review Office Hours

Event Timeline

Luke081515 created this task.May 26 2016, 11:11 PM

Restricted Application added a subscriber: Zppix. · View Herald TranscriptMay 26 2016, 11:11 PM

Luke081515 triaged this task as Medium priority.May 26 2016, 11:12 PM

Krenair renamed this task from Setup a codereview hour for non amrican people to Setup a codereview hour for non american people.May 26 2016, 11:14 PM

Maybe hold two code review hours a day like SWAT does. So maybe 2-4pm (utc) and 8-10pm utc. Would give many users more chances of joining.

In T136370#2332476, @Paladox wrote:

Maybe hold two code review hours a day like SWAT does. So maybe 2-4pm (utc) and 8-10pm utc. Would give many users more chances of joining.

Luke081515 mentioned this in T128371: Set up Code Review office hours.May 27 2016, 12:00 AM

Yep, I'm for two hours too, but I think one hour is enough? Or should we try two, and take a look, how it works? so your proposal is 14-16 UTC (16-18 CEST)? If people are able to join at this time, a second hour there would make sense. But at which day? I think to we should not set both hours to thursday.

Luke081515 moved this task from To triage to Team radar on the Developer-Advocacy board.May 27 2016, 12:03 AM

Luke081515 moved this task from INBOX to Next on the Release-Engineering-Team board.

Luke081515 moved this task from To Triage to Team radar on the Team-Practices board.

Luke081515 moved this task from Next to In-progress on the Release-Engineering-Team board.

In T136370#2332583, @Luke081515 wrote:

Yep, I'm for two hours too, but I think one hour is enough? Or should we try two, and take a look, how it works? so your proposal is 14-16 UTC (16-18 CEST)? If people are able to join at this time, a second hour there would make sense. But at which day? I think to we should not set both hours to thursday.

We could do it on Tuesday and Thursday so Tuesday 2-4pm and Thursday 8-10pm utc.

But we can do it these times since anyone can come and leave.

In T136370#2332604, @Paladox wrote:

We could do it on Tuesday and Thursday so Tuesday 2-4pm and Thursday 8-10pm utc.
But we can do it these times since anyone can come and leave.

This sounds good to me, though I will probably only be able to attend one day per week.

In T136370#2332733, @mmodell wrote:

This sounds good to me, though I will probably only be able to attend one day per week.

Same. But I'd rather be able to attend consistently than not, which is the case at the moment.

14.00-16.00 UTC is still quite late. During the DST only one hour of it overlaps with my usual working hours. Not to mention the timezones ahead of mine.

Ladsgroup added a subscriber: Ladsgroup.May 27 2016, 11:33 AM

Also, having a code review hour close to the MediaWiki train branching on Tuesdays is perhaps not a good idea with regards to stability.

Any updates on the plans? It's been about one month since code review office hours started.

When I discussed the ideal timetable with Nikerabbit, in regard to
some stability in summer/winter timezones, I woud recommend
13:00-14:00 UTC.