From: Jonathan Nieder <firstname.lastname@example.org> To: Carmen Andoh <email@example.com> Cc: firstname.lastname@example.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>, Taylor Blau <email@example.com>, Junio C Hamano <firstname.lastname@example.org>, "brian m. carlson" <email@example.com>, Simon Pieters <firstname.lastname@example.org> Subject: Re: Git Inclusion Summit Date: Thu, 23 Jul 2020 13:59:28 -0700 [thread overview] Message-ID: <20200723205928.GB3579560@google.com> (raw) In-Reply-To: <CA+TwhoKBYwUKmtQTyiocPWJD=KeZQryS+6Q8JKxKgLEy0qJwAw@mail.gmail.com> (cc-ing some people from the previous discussion) Hi, 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! [...] > This can be run unconference style like previous contributor summits: > we'll use a spreadsheet to choose and vote on topics. That worked well in , so sounds good to me. [...] > Who all are invited? > > Git core contributors on https://lore.kernel.org/git/., anyone > interested in teaching OSS projects about DEI. [...] > When? > Anytime between mid August - mid September. To get consensus on > preferred dates , including summit duration and times, please vote > at the whenisgood link below by Thursday, July 30th. Please specify in > comments if you prefer a .5 day, 1 day, 1.5 days or other for the > event duration. The 2019 Git contributors summit was two half-days, which seemed to work well. That made it easier to get some time zone overlap between Europe and the United States. More time than that in a day on video and people would start to get tired. 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. Thanks, Jonathan >  https://lore.kernel.org/git/20200610222719.GE148632@google.com >  https://lore.kernel.org/git/nycvar.QRO.email@example.com/ >  http://whenisgood.net/9z2diyy  https://lore.kernel.org/git/nycvar.QRO.firstname.lastname@example.org/
next prev parent reply other threads:[~2020-07-23 20:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-23 19:30 Carmen Andoh 2020-07-23 20:59 ` Jonathan Nieder [this message] 2020-07-23 22:26 ` Junio C Hamano 2020-07-24 12:55 ` Carmen Andoh 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
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 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 \ --in-reply-to=20200723205928.GB3579560@google.com \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Git Inclusion Summit' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).