From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git Merge 2025, September 29-30, San Francisco, CA
Date: Wed, 30 Apr 2025 17:48:41 -0400 [thread overview]
Message-ID: <aBKauXrGU8cMVXVI@nand.local> (raw)
In-Reply-To: <Z+L3Mt58n18KUNzs@nand.local>
On Tue, Mar 25, 2025 at 02:34:26PM -0400, Taylor Blau wrote:
> Git Merge 2025 is happening on September 29-30th in San Francisco, CA!
> The Contributor's Summit will be on the 30th. Here are the details for
> the main conference:
>
> When: September 29th and 30th
> Where: GitHub HQ, 88 Colin P Kelly Jr. St., San Francisco, CA 94107
> What: Main conference on the 29th, breakouts and Contributor's Summit
> on the 30th.
Since announcing[1] that Git Merge will take place this year in San
Francisco, CA, I have gotten feedback publicly and privately that there
are challenges for those who would have to travel into the US in order
to attend.
I (and my colleagues at GitHub responsible for producing Git Merge) want
to make sure that folks who can't attend Git Merge in-person due to
travel concerns are still able to participate.
To that end, here are a few updates on this year's Git Merge:
- We're **welcoming remote speakers and attendees**. If you are
interested in speaking, but weren't planning on doing so due to
travel constraints, please consider submitting a talk proposal to
present virtually!
- The **Contributor's Summit will continue to take place on the second
day** (September 30th), and will have two-way A/V equipment set up
so remote attendees can participate.
A few more logistics:
- Tickets to attend remotely are $0. If you have already purchased an
in-person ticket and wish to refund it to attend virtually, just let
me know.
- Likewise, if you have submitted a talk proposal but wish to give it
virtually instead, please let me know there as well.
If you are travelling in-person need financial assistance to do so,
notes that we will **stop accepting requests for financial assistance on
May 15, 2025 end of day PDT**. This is so that those who have open
requests can get a decision sooner rather than later in order to start
the visa application process. If you are planning on requesting
financial assistance, and haven't yet done so, please consider doing so
ASAP.
I am sad to not be able to see everyone in person, but my hope is that
by offering options to attend and participate remotely, that Git Merge
will be more accessible to those not comfortable traveling into the US
than previously.
If you have any concerns or questions that you wish to handle privately,
please feel free to contact me off-list.
See you there (virtually or otherwise)!
Thanks,
Taylor
prev parent reply other threads:[~2025-04-30 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 18:34 [ANNOUNCE] Git Merge 2025, September 29-30, San Francisco, CA Taylor Blau
2025-03-25 21:56 ` brian m. carlson
2025-04-30 21:48 ` 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=aBKauXrGU8cMVXVI@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).