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

Bi-Weekly Standup - Time/timezone in calendar?

From
Philip Oakley <philipoakley@iee.email>
Date
Sep 25, 2019, 13:31 UTC
Message-ID
<a56e5ebe-53ba-5f20-5606-b4b17dc660b5@iee.email>
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.

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.

Philip

[1] https://calendar.google.com/calendar/embed?src=nk8ph2kh4p5tgfcctb8i7dm6d4%40group.calendar.google.com

Next: Thomas Gummerer
Message 1 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.