From: Thomas Gummerer <t.gummerer@gmail.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: Git List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: Bi-Weekly Standup - Time/timezone in calendar?
Date: Wed, 25 Sep 2019 15:32:47 +0100 [thread overview]
Message-ID: <20190925143247.GD11444@cat> (raw)
In-Reply-To: <a56e5ebe-53ba-5f20-5606-b4b17dc660b5@iee.email>
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!
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.
> Philip
>
>
> [1] https://calendar.google.com/calendar/embed?src=nk8ph2kh4p5tgfcctb8i7dm6d4%40group.calendar.google.com
>
next prev parent reply other threads:[~2019-09-25 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:31 Bi-Weekly Standup - Time/timezone in calendar? Philip Oakley
2019-09-25 14:32 ` Thomas Gummerer [this message]
2019-09-25 15:30 ` Philip Oakley
2019-09-28 7:58 ` Junio C Hamano
2019-09-30 8:07 ` Thomas Gummerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190925143247.GD11444@cat \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=philipoakley@iee.email \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).