From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Taylor Blau <me@ttaylorr.com>
Subject: Possible venues for Git Merge 2025
Date: Thu, 20 Mar 2025 11:31:36 +0100 [thread overview]
Message-ID: <Z9vuiCnKcMRRXHOR@pks.im> (raw)
Hi,
given that this year is the 20th anniversary of the Git project it would
be great to host another Git Merge so that the wider community can come
together and celebrate. Taylor and I have been chatting about this
opportunity a bit to figure out what we're going to do this year.
We have been discussing two different options:
- Hosting in the US in San Francisco at the GitHub HQ.
- Hosting in the EU in Amsterdam colocated with the Open Source
Summit Europe.
Typically, the location is alternating on a yearly basis between the US
and the EU. So given that last year it was hosted in Berlin it would be
the US' turn. But given the recent political climate in the US I'm
afraid that many people would not feel comfortable traveling there right
now. So in the spirit of being inclusive I think we should at least
consider whether we may want to break the typical alternating cycle and
host in the EU again.
I have been reaching out to the Linux Foundation, and initial feedback
has been positive that colocating would be possible. I do not yet have
any details though, so we'd know for sure in the first half of April
whether this is an option in the first place.
Until then I wanted to get a bit of feedback from the community so that
we can assess better whether my fear is unfounded or not, and what the
majority's preference would be.
Patrick
next reply other threads:[~2025-03-20 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 10:31 Patrick Steinhardt [this message]
2025-03-20 13:47 ` Possible venues for Git Merge 2025 Taylor Blau
2025-03-20 14:39 ` rsbecker
2025-03-20 22:09 ` brian m. carlson
2025-03-25 12:54 ` Patrick Steinhardt
2025-03-25 15:19 ` rsbecker
2025-03-25 22:58 ` brian m. carlson
2025-03-27 9:18 ` Johannes Schindelin
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=Z9vuiCnKcMRRXHOR@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
/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).