From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Don Goodman-Wilson <firstname.lastname@example.org>
Cc: Taylor Blau <email@example.com>, Junio C Hamano <firstname.lastname@example.org>,
Emily Shaffer <email@example.com>,
"brian m. carlson" <firstname.lastname@example.org>,
Simon Pieters <email@example.com>,
Subject: Re: Virtual Inclusion Summit
Date: Fri, 12 Jun 2020 16:33:05 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2457 bytes --]
On Thu, 11 Jun 2020, Don Goodman-Wilson wrote:
> (First of all, it’s Don, rather than Dan; I think Johannes’s
> auto-correct got the best of him at one point in his email :D )
Yep, sorry for that!
> I think this is a wonderful idea.
> First, I am myself a white cis-het male; my participation in any such
> summit would be predicated on ensuring that we have a diversity of
> voices present, as I think it is foolish to have a conversation about
> inclusivity and equity with only white voices like mine speaking. I
> hope and expect that we are planning for that.
> Given the concerns about being recorded, perhaps my experience running
> Maintainerati events might be helpful. Maintainerati (if you hadn’t
> heard of it) is a series of events that gather open source maintainers
> into unconference-style conversations about the challenges they face,
> and finding solutions to those problems. The events are operated under
> Chattham House rules, ensuring the anonymity of participants who wish
> to remain so. Even so, the goal of the events is to not only document
> the conversations that happened, but to create a set of documents that
> allow the conversation to continue long after the event is over, as
> well as providing a blueprint for concrete action. It is not difficult
> to set up the necessary conditions to make this work, although we will
> need dedicated note-takers willing to undergo about 30 minutes of
> training. I would be happy to put in the effort to make this kind of
> thing happen, if this sounds helpful.
Thank you for the offer and describing your experience.
I might be completely wrong, but in this instance, I have the impression
that for the topic of changing the default main branch name, a Chattham
House rules meeting might not even be _all_ that crucial. Let me explain
The primary purpose of this meeting, from my point of view, is to align
and coordinate, to set out goals that we want to agree on. Where "we" is
"the core Git contributors".
And from what I see, I am happy to report that I see a lot of alignment
already. There was no "nah, why bother?" response, which made me very
Every active contributor seems to agree that this is worth doing, and
since I am doing the bulk work (with a lot of help from your side, thank
you so much!), there is not even the question "but who will do it?".
next prev parent reply other threads:[~2020-06-12 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 22:27 Virtual Inclusion Summit (was: Re: Rename offensive terminology (master)) Emily Shaffer
2020-06-10 22:48 ` Virtual Inclusion Summit Junio C Hamano
2020-06-11 1:10 ` Taylor Blau
2020-06-11 2:13 ` Junio C Hamano
2020-06-11 2:35 ` Taylor Blau
2020-06-11 8:58 ` Don Goodman-Wilson
2020-06-12 14:22 ` Derrick Stolee
2020-06-12 14:33 ` Johannes Schindelin [this message]
2020-06-11 15:25 ` Junio C Hamano
2020-06-12 14:38 ` Johannes Schindelin
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:
* 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.
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).