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

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

From
Thomas Gummerer <t.gummerer@gmail.com>
Date
Sep 30, 2019, 08:07 UTC
Message-ID
<20190930080727.GF11444@cat>
In-Reply-To
<xmqqk19skg24.fsf@gitster-ct.c.googlers.com>
On 09/28, Junio C Hamano wrote:
Show 17 quoted lines
> Thomas Gummerer <t.gummerer@gmail.com> writes:
> 
> >> 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!
> >
> > 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.
> 
> By the way, this is sort of off-topic, but should I add this to
> tinyurl.com/gitCal (or even better, should I add you as another
> editor of the said calendar), so that people have one fewer
> calendars to follow?

Yeah, I think that would be awesome, thanks for offering. One less calendar should definitely make things easier for people (and give the standup some more visibility).

And I'd be happy to take care of adding/updating the events if you add me as editor to the calendar.

Thanks!
Previous: Junio C Hamano
Message 5 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.