From: Carmen Andoh <firstname.lastname@example.org>
Subject: Git Inclusion Summit
Date: Thu, 23 Jul 2020 15:30:27 -0400 [thread overview]
Message-ID: <CA+TwhoKBYwUKmtQTyiocPWJD=KeZQryS+6Q8JKxKgLEy0qJwAw@mail.gmail.com> (raw)
Hello Git community,
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.
The purpose of this inclusion summit is to engage core Git
contributors as active participants in diversity and inclusion
initiatives for the Git project. As mentioned  "to align and
coordinate, to set out goals that we want to agree on." This is part
of a broader goal to make the Git version control system better
support inclusive open source projects. The summit will give
contributors the opportunity to learn about and share perspectives on
inclusive culture, product inclusion, and career development.
This can be run unconference style like previous contributor summits:
we'll use a spreadsheet to choose and vote on topics. This event will
be a success if we walk away with specific recommendations on where
and how Git will make changes to improve the experiences of
underrepresented users in the Git project, and how to make the Git
project better represent the needs of current and potential users.
It was mentioned in  that we should have conversations about equity
and inclusion with more diverse voices present. But we also don’t
want to put a burden on individuals coming to educate us about things
that we should be researching for ourselves. To that end, we are
meeting with Diversity, Equity, Inclusion (DEI) experts for guidance
and will have recommendations to incorporate into the summit. Prior to
the summit, we will send out some resources to look through ahead of
Who all are invited?
Git core contributors on https://lore.kernel.org/git/., anyone
interested in teaching OSS projects about DEI.
If your network includes any groups or individuals who focus on
educating others about DEI, you're welcome to invite them or contact
summit organizers to learn more. We prefer groups and individuals who
are in the business of educating on inclusion, or if they are
volunteers, already explicitly expressed their interest in
volunteering rather than being asked, as we want to be very mindful of
free emotional labor. A bonus for knowledge of inclusion in open
source. We can widen our understanding by asking non-Git contributors
to come share their perspectives for some or all of the summit.
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
Once a reasonable consensus has been reached, we’ll set the date and
time, ask for RSVPs via email, and send a planning spreadsheet to
start proposing topics and crowdsourcing the agenda.
I have questions, who should I contact?
For questions or concerns, please reach out to email@example.com
Interested in helping to plan this event?
Email firstname.lastname@example.org to join
Open Source Programs Office, Google
next reply other threads:[~2020-07-23 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 19:30 Carmen Andoh [this message]
2020-07-23 20:59 ` Git Inclusion Summit Jonathan Nieder
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
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).