git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[NOTES 10/11] How can companies respectfully engage contractors to work on Git?

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 6, 2025, 19:20 UTC
Message-ID
<aOQWiOOp2pz6n8Kg@nand.local>
In-Reply-To
<aOQVeVYY6zadPjln@nand.local>
Topic: How can companies respectfully engage contractors to work on Git?
Leader: Emily Shaffer
* Google hired Collabra to work on patches on the list
* Should they be doing something specific to indicate they're pursuing these
	patches on behalf of someone else?
* Taylor: So long as they understand there's no obligation from the project to
	accept the work
* Having a short note in the cover letter to indicate who is sponsoring the work
	(if it's not already obvious). Mention during review if you think there's a
	conflict of interest.
Previous: Taylor BlauNext: Taylor Blau
Message 11 of 12 in “Notes from the Git Contributor's Summit, 2025”
  1. Taylor BlauOct 6, 2025
  2. 01/11 SHA-256 and interoperability workTaylor Blau, Oct 6, 2025
  3. 02/11 First-class conflicts in Git?Taylor Blau, Oct 6, 2025
  4. 03/11 The future of history rewriting - rebase, replay and history (+Change-IDs)Taylor Blau, Oct 6, 2025
  5. 04/11 RustTaylor Blau, Oct 6, 2025
  6. 05/11 Pluggable object databasesTaylor Blau, Oct 6, 2025
  7. 06/11 Repository maintenance long-term goalsTaylor Blau, Oct 6, 2025
  8. 07/11 Change-ID Header in GitTaylor Blau, Oct 6, 2025
  9. 08/11 Resumable fetch / pushTaylor Blau, Oct 6, 2025
  10. 09/11 Git 3.0Taylor Blau, Oct 6, 2025
  11. 10/11 How can companies respectfully engage contractors to work on Git?Taylor Blau, Oct 6, 2025
  12. 11/11 Conservancy 2025 updatesTaylor Blau, Oct 6, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.