From: Carmen Andoh <email@example.com>
To: Junio C Hamano <firstname.lastname@example.org>
Cc: Jonathan Nieder <email@example.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Taylor Blau <firstname.lastname@example.org>,
"brian m. carlson" <email@example.com>,
Simon Pieters <firstname.lastname@example.org>
Subject: Re: Git Inclusion Summit
Date: Fri, 24 Jul 2020 08:55:05 -0400 [thread overview]
Message-ID: <CA+TwhoLmR7vi0R6R-Wac7bvFoy+XQzX_OhGb090fzo=7REo4Hg@mail.gmail.com> (raw)
First test of inclusion: be inclusive of time zones.
I've updated the whenisgood  to accept a broader time range. From
6am to 9pm Pacific to be more doable for people in EMEA and APAC. To
those who have already responded with time preferences, can you submit
another response with the new times? Jonathan's suggestion of having
multiple half days at different times could be a good compromise (one
day you wake up early, another day you stay up late).
On Thu, Jul 23, 2020 at 6:26 PM Junio C Hamano <email@example.com> wrote:
> Jonathan Nieder <firstname.lastname@example.org> writes:
> > Carmen Andoh wrote:
> >> There's been some conversation about holding a virtual contributor
> >> summit focused on inclusion . I've volunteered to work with
> >> Jonathan Nieder’s team on organizing this event.
> > Welcome!
> Yup, welcome and thanks for helping.
> > Thoughts about how to get reasonable coverage for people in different
> > time zones? It's subtle, but the whenisgood link appears to assume
> > U.S. pacific time --- I'd be willing to start a little earlier or end
> > a little later if it makes participation from other time zones easier.
> FWIW, we've timed coordinated security releases at late afternoon
> European, which translates to early afternoon Eastern and late
> morning Pacific time. It was a bit inconvenient when I was in east
> Asia where it is past midnight but it was OK as it was convenient
> for everybody else.
> The intended population may be somewhat different for this event,
> but I suspect that the difference is not all that much. Or am I
> not being inclusive enough for our Asian friends by assuming so?
next prev parent reply other threads:[~2020-07-24 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 19:30 Git Inclusion Summit Carmen Andoh
2020-07-23 20:59 ` Jonathan Nieder
2020-07-23 22:26 ` Junio C Hamano
2020-07-24 12:55 ` Carmen Andoh [this message]
2020-07-26 4:02 ` Eric Wong
2020-07-27 15:10 ` Taylor Blau
2020-07-28 10:07 ` Eric Wong
2020-07-28 16:25 ` Taylor Blau
2020-07-28 17:15 ` Kaartic Sivaraam
2020-07-29 17:00 ` 24 hours to respond with date/duration preferences for inclusion summit Carmen Andoh
2020-07-29 18:25 ` Junio C Hamano
2020-07-29 19:29 ` Carmen Andoh
2020-07-28 16:44 ` Git Inclusion Summit Jeff King
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).