git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bi-Weekly Standup - Time/timezone in calendar?

From
Philip Oakley <philipoakley@iee.email>
Date
Sep 25, 2019, 15:30 UTC
Message-ID
<dfa01a78-c45e-4466-5232-6aae389082ca@iee.email>
In-Reply-To
<20190925143247.GD11444@cat>
On 25/09/2019 15:32, Thomas Gummerer wrote:
Show 37 quoted lines
> On 09/25, Philip Oakley wrote:
>> Hi,
>>
>> At the Virtual Git Contributors Summit we discussed (#13) the bi-weekly
>> standup meetings (mentioned in the Git Rev News edition 55 under
>> 'News/Various').
>>
>> The Git Events calendar [1] that's linked from the Rev News doesn't actually
>> say what time zone to use for the stand-up start time, so at first glance
>> one can get confused by summer time and national time zone differences.
>>
>> Currently it's saying (when clicked on, via 'more details')
>>
>> Git Standup
>> Monday, September 30⋅6:00 – 7:00pm
>> Every 2 weeks on Monday
>>
>> I thought it was to be 1700 UTC, which currently is 1800 BST her in UK, and
>> 1900 CST in Europe.
> That's my recollection as well, and what the calendar should say.
> Thanks for flagging this!
>
>> If I hover over the event (have to restart the calendar), I (depending on
>> view) do get an indicator in the lower left status bar that
>> "Events shown in time zone: Coordinated Universal Time". but with a 5pm
>> indication in the calendar sheet.
>>
>> Is this google calendar trying to be too clever, or should "1700 UTC" be
>> included in the event details? I don't use Google calendar except for
>> occasional reference.
> Yeah, I think the embed view of the Google Calendar is trying to be
> too clever here.  I did set the event up to be at 17:00 UTC, and I'm
> not sure why it showed up otherwise for you.
>
> I have now updated the event with a few more details, including that
> it is happening at 17:00 UTC, and added that information to the title
> as well.  Hope that helps!

Looks a lot better, especially if one clicks and selects the 'more details' option (which changes to local TZ)

Show 9 quoted lines
> Also replying to your last question in https://github.com/git/git.github.io/issues/394#issuecomment-535030810:
>
>> Also given Dscho's comment at the summit about late evenings, are we
>> changing the time for those dark winter nights soon to come (N
>> Hemisphere)?
> I don't know.  I'd be happy to keep it at 17:00 UTC, but that might be
> a bit early for folks living on the west coast.  I don't have a strong
> opinion on this, but I'm happy to update the calendar (or not
> depending on what we decide) once the decision is made.

Once everyone changed from daylight saving, then changing to local clock is likely (unless we have a few southern hemisphere dst folks going the other way! James Ramsay?)

Show 5 quoted lines
>> Philip
>>
>>
>> [1] https://calendar.google.com/calendar/embed?src=nk8ph2kh4p5tgfcctb8i7dm6d4%40group.calendar.google.com
>>
Previous: Thomas GummererNext: Junio C Hamano
Message 3 of 5 in “Bi-Weekly Standup - Time/timezone in calendar?”
  1. Philip OakleySep 25, 2019
  2. Thomas GummererSep 25, 2019
  3. Philip OakleySep 25, 2019
  4. Junio C HamanoSep 28, 2019
  5. Thomas GummererSep 30, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.