From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Scott Chacon <schacon@gmail.com>, Patrick Steinhardt <ps@pks.im>,
Emily Shaffer <nasamuffin@google.com>
Subject: [ANNOUNCE] Git Merge 2026, (September 17-18, in Lisbon)
Date: Tue, 21 Apr 2026 12:35:24 -0400 [thread overview]
Message-ID: <aeenTA8efhY6hNvt@nand.local> (raw)
Git Merge 2026 is happening in-person on September 17-18th, 2026, in
beautiful Lisbon, Portugal!
GitButler and GitHub are co-hosting the event, which will take place on
the 17-18th, with the main conference taking place on the first day. The
second day will be reserved for the Contributor's Summit and a series of
unconference-style breakout sessions.
In addition, Google will be hosting a JJ-specific event on the 16th
which will be focused on the JJ project and its ecosystem. More details
from them to follow shortly.
There will be a social event on one of the evenings (TBD), which is
graciously hosted by our friends at GitLab.
Here are the details for the main conference:
When: September 17-18th, 2026
Where: Suspenso, Lisbon, Portugal (https://suspenso.pt/)
What: Talks on the 17th, everything else on the 18th
This email is just to announce the date so people can start putting
together travel arrangements and to start thinking about topics for
talks and discussions for the unconference sessions. A couple of notes:
* There are a number of hotels nearby the venue, and we don't have a
room block set up at this time, so feel free to make your own
arrangements.
* Registration for the event is still being set up, but it should be
available shortly. I'll send an update to this thread once I have
more details.
As always, if you'd like to come but need financial assistance with
travel, please reach out to the Git PLC at <git@sfconservancy.org>.
We'll collect requests and try to make decisions and notify people with
enough time before the event to make travel arrangements.
Other than that, please be thinking about (and feel free to discuss in
this thread) topics you'd like to discuss, or any general thoughts on
the format, venue setup, etc.
Thanks,
Scott Chacon (GitButler)
Taylor Blau (GitHub)
reply other threads:[~2026-04-21 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aeenTA8efhY6hNvt@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.com \
--cc=ps@pks.im \
--cc=schacon@gmail.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