From: Patrick Steinhardt <ps@pks.im>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: Possible venues for Git Merge 2025
Date: Tue, 25 Mar 2025 13:54:51 +0100 [thread overview]
Message-ID: <Z-Knm2WGeMI9a7zt@pks.im> (raw)
In-Reply-To: <Z9ySGbE4sq0JfgKs@tapette.crustytoothpaste.net>
On Thu, Mar 20, 2025 at 10:09:29PM +0000, brian m. carlson wrote:
> On 2025-03-20 at 10:31:36, Patrick Steinhardt wrote:
> > 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.
>
> Yes, I do think that given current circumstances the U.S. is not a good
> place to host events. Perhaps that will change in the future, but I
> don't think that would be a prudent choice right now. I've talked to
> several people who are uncomfortable traveling there, so we'd probably
> get better attendance hosting elsewhere.
>
> I would be fine with Amsterdam, and I might also suggest a major
> Canadian city (such as Toronto, Montreal, or Vancouver) if we preferred
> to do this in North America (since we've traditionally alternated
> continents). I can imagine other locations outside of the U.S. that
> might be fine as well, so I'm willing to keep an open mind if a good
> opportunity comes up.
The only reasons why I proposed Amsterdam are the Open Source Summit and
that I have some ways to help out with organizing the event over there.
I would be equally happy with alternatives like Canada, but didn't
really want to propose alternatives like this myself because I would
have to push the entire burden onto somebody else.
So if it would be a possibility and if people could help out getting
things organized in other countries/continents I'd be happy.
Patrick
next prev parent reply other threads:[~2025-03-25 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 10:31 Possible venues for Git Merge 2025 Patrick Steinhardt
2025-03-20 13:47 ` Taylor Blau
2025-03-20 14:39 ` rsbecker
2025-03-20 22:09 ` brian m. carlson
2025-03-25 12:54 ` Patrick Steinhardt [this message]
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=Z-Knm2WGeMI9a7zt@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
/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).