From: Taylor Blau <ttaylorr@openai.com>
To: git@vger.kernel.org
Subject: [NOTES 04/07] Outreachy sponsorship
Date: Tue, 6 Oct 2026 11:06:27 -0700 [thread overview]
Message-ID: <summit-2026.94e33e9ddf234334.04@ttaylorr.com> (raw)
In-Reply-To: <summit-2026.94e33e9ddf234334.00@ttaylorr.com>
Topic: Outreachy sponsorship
* Chris: We want three interns, at $10k per intern. Are any companies
interested in helping? The session starts in early December. GitLab or
GitHub sponsored this in the past, but as of last year neither wanted
to, so Git has had to pay.
* Patrick: Talk to GitLab's contributor success person.
* Elijah: We need to identify the right person to ask.
* Emily: I can ask Google's OSPO whether there is interest, though I am
not expecting much.
Git Merge 2027:
* [There was some interest in holding Git Merge in Canada, given the
political climate.]
* [Announcing the location early would help Outreachy and GSoC interns
who want to attend.]
next prev parent reply other threads:[~2026-10-06 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 18:05 Notes from the Git Contributor's Summit, 2026 Taylor Blau
2026-10-06 18:06 ` [NOTES 01/07] Security mailing list and security process Taylor Blau
2026-10-06 18:06 ` [NOTES 02/07] Git 3.0 Taylor Blau
2026-10-06 18:06 ` [NOTES 03/07] Documentation Taylor Blau
2026-10-07 4:49 ` Todd Zullinger
2026-10-07 17:38 ` Junio C Hamano
2026-10-06 18:06 ` Taylor Blau [this message]
2026-10-06 18:06 ` [NOTES 05/07] What can we do next with pluggable ODB? Taylor Blau
2026-10-06 18:06 ` [NOTES 06/07] AI contribution policy Taylor Blau
2026-10-06 18:06 ` [NOTES 07/07] Protocol v2 for pushes 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=summit-2026.94e33e9ddf234334.04@ttaylorr.com \
--to=ttaylorr@openai.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