All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Taylor Blau'" <me@ttaylorr.com>, "'Patrick Steinhardt'" <ps@pks.im>
Cc: <git@vger.kernel.org>
Subject: RE: Possible venues for Git Merge 2025
Date: Thu, 20 Mar 2025 10:39:35 -0400	[thread overview]
Message-ID: <043401db99a5$ea048560$be0d9020$@nexbridge.com> (raw)
In-Reply-To: <Z9wcY/55BoMsaEnt@nand.local>

On March 20, 2025 9:47 AM, Taylor Blau wrote:
>On Thu, Mar 20, 2025 at 11:31:36AM +0100, Patrick Steinhardt wrote:
>> 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.
>
>Sorry for the miscommunication on our part! Let me clarify some of the details
>around where things are with Git Merge planning:n
>
>I have been looking into various option for Git Merge this year to celebrate the
>project's 20th anniversary. After exploring a number of options, GitHub has secured
>the budget and space availability to host Git Merge at GitHub HQ in San Francisco
>over a couple of weekdays in September!
>
>We haven't finalized exactly what those two days are yet, hence why I haven't sent
>an announcement yet to the list. As soon as we finalize what those dates are, I'll
>send an announcement with the details (including the dates ;-)).
>
>Please expect that from me soon, and I am very much looking forward to seeing as
>many people in San Francisco to celebrate as can make it!

While I would love to be at Git Merge, travel to the US is currently restricted and I will
not be able to attend meetings at a US venue. Amsterdam would be a more acceptable
location for the foreseeable future. I hope that will change by September, but it is not
up to me.

--Randall


  reply	other threads:[~2025-03-20 14:39 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 [this message]
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='043401db99a5$ea048560$be0d9020$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=ps@pks.im \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.