From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git Merge 2023 updates
Date: Mon, 26 Jun 2023 17:30:54 -0400 [thread overview]
Message-ID: <ZJoDjnr+FkgrDsKA@nand.local> (raw)
I wanted to share a couple of updates on the status of Git Merge:
- GitHub will not be hosting an in-person event for Git Merge this
year.
- Instead, we will focus our efforts on hosting a virtual
Contributor's Summit, the details of which are TBD.
The decision to not host an in-person event was a difficult one to make,
but necessary given the current economic conditions and their effect on
travel budgets for conferences.
When I asked[1] about which location folks preferred for Git Merge, a
number of replies indicated that nobody on their team would be able to
attend unless speaking. I think it's a safe assumption that other
individuals who would be travelling on behalf of their employer are in a
similar situation.
That said, I plan on hosting an virtual Contributor's Summit in
late-September or so for folks who are working on Git to get together.
This year's will likely look a lot different than the Contributor's
Summit we held last year in Chicago, IL. That said, a couple of
requests:
- If you are interested in joining, and aren't sure whether or not you
are able to, please feel free to shoot me a message off-list and
ask.
- If you have suggestions about the format of the day,
video-conferencing related suggestions, or anything else that you
think could improve the Contributor's Summit, please also feel more
than free to let me know.
I regret not being able to see everybody in person this year, but I'm
hopeful that we'll get a chance to make up for it next year :-). Until
then,
Thanks,
Taylor
[1]: https://lore.kernel.org/git/ZEyDcBcGmLznqKzD@nand.local/
reply other threads:[~2023-06-26 21:31 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=ZJoDjnr+FkgrDsKA@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).