From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: Notes from the Git Contributor's Summit, 2025
Date: Mon, 6 Oct 2025 15:16:09 -0400 [thread overview]
Message-ID: <aOQVeVYY6zadPjln@nand.local> (raw)
It was great to see folks both virtually and in person last week at the
Contributor's Summit!
After travelling back home and catching up on things that I missed while
at Git Merge, I had a chance to polish up the notes we took during the
Contributor's Summit to share with the list.
The notes are available (as read-only) in Google Docs, too, for folks
who prefer to view them there are the following link:
https://docs.google.com/document/d/1arvvXP8DrF3F8PCKQOmGvYh5jUg8P9Clx9m-FgDD4EI
At the Contributor's Summit, we discussed the following topics (with
topic leaders in parentheses):
- SHA-256 and interoperability work (brian m. carlson)
- First-class conflicts in Git? (Martin von Zweigbergk)
- The future of history rewriting - rebase, replay and history
(+Change-IDs) (Phillip Wood / Scott Chacon)
- Rust (Patrick Steinhardt)
- Pluggable object databases (Patrick Steinhardt)
- Repository maintenance long-term goals (Taylor Blau)
- Change-ID Header in Git (Philip Metzger)
- Resumable fetch / push (Scott Chacon)
- Git 3.0 (Patrick Steinhardt)
- How can companies respectfully engage contractors to work on Git?
(Emily Shaffer)
- Conservancy 2025 updates (Taylor Blau)
The list of all topics proposed (and the number of votes they received)
are here:
https://docs.google.com/spreadsheets/d/1mSyAvvpYTIuR7JIm7J0H0IQQEUt5y8zq8Bo53nl8yCY
I'll send the broken-out notes for each topic in a response to this
message for posterity, and so folks can continue the discussion on the
list.
Like in previous years, if you have any feedback on how the
Contributor's Summit went, please feel free to share it with me here, or
off-list.
I look forward to seeing everyone at future Contributor's Summit events
in the future!
Thanks,
Taylor
next reply other threads:[~2025-10-06 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 19:16 Taylor Blau [this message]
2025-10-06 19:18 ` [NOTES 01/11] SHA-256 and interoperability work Taylor Blau
2025-10-06 19:18 ` [NOTES 02/11] First-class conflicts in Git? Taylor Blau
2025-10-06 19:18 ` [NOTES 03/11] The future of history rewriting - rebase, replay and history (+Change-IDs) Taylor Blau
2025-10-06 19:18 ` [NOTES 04/11] Rust Taylor Blau
2025-10-06 19:19 ` [NOTES 05/11] Pluggable object databases Taylor Blau
2025-10-06 19:19 ` [NOTES 06/11] Repository maintenance long-term goals Taylor Blau
2025-10-06 19:19 ` [NOTES 07/11] Change-ID Header in Git Taylor Blau
2025-10-06 19:20 ` [NOTES 08/11] Resumable fetch / push Taylor Blau
2025-10-06 19:20 ` [NOTES 09/11] Git 3.0 Taylor Blau
2025-10-06 19:20 ` [NOTES 10/11] How can companies respectfully engage contractors to work on Git? Taylor Blau
2025-10-06 19:20 ` [NOTES 11/11] Conservancy 2025 updates Taylor Blau
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=aOQVeVYY6zadPjln@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
/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).