From: Taylor Blau <me@ttaylorr•com>
To: git@vger•kernel.org
Subject: [NOTES 11/11] Conservancy 2025 updates
Date: Mon, 6 Oct 2025 15:20:56 -0400 [thread overview]
Message-ID: <aOQWmFAZ05vZCp/M@nand.local> (raw)
In-Reply-To: <aOQVeVYY6zadPjln@nand.local>
Topic: Conservancy 2025 updates
Leader: Taylor Blau
* More trademark requests than typical this year
* Asked Perforce to stop using a very similar logo to the git logo
* Git holds a fairly restrictive trademark policy, but often doesn't enforce it.
Some risk the trademark office could flag that.
* Git project has a significant amount of money that could be spent ($100k?).
* Emily: Could sponsor git-related projects (ex: gitoxide)
* Outreachy costs money per-intern
* Not guaranteed that GitHub or GitLab would always be able to sponsor all
the interns the Git project desires. Could use $ for this. Also depends on
the future of Outreachy.
* Git ambassador program, with stipends?
* Needs someone with interest and skills to organize
prev parent reply other threads:[~2025-10-06 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 19:16 Notes from the Git Contributor's Summit, 2025 Taylor Blau
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 ` Taylor Blau [this message]
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=aOQWmFAZ05vZCp/M@nand.local \
--to=me@ttaylorr$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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