From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Contributor's Summit Registration, Sept 14, 2020, Chicago
Date: Sun, 17 Jul 2022 16:00:19 -0400 [thread overview]
Message-ID: <YtRqU5rAOsLw5s03@nand.local> (raw)
Hi again,
Following up on my earlier announcement[1], I have some more details for
the Contributor Summit at Git Merge this year:
When: September 14th, 12-5pm CDT (UTC-5)
Where: Convene (131 S Dearborn) Chicago, Illinois, USA
What: Contributor's Summit
Who: All contributors to Git or related projects in the Git ecosystem
are invited; if you're not sure if you qualify, please ask!
Registration is now open, though we haven't posted a link to it on the
site. If you'd like to register early, you can use the following link
below:
https://www.eventbrite.com/e/git-merge-2022-tickets-386396170347
If you are planning on attending the Contributor's Summit, please send
me an email off-list for a special code to use when registering. This
covers both the Contributor's Summit and main registration, so don't
register twice :-).
As with previous years, you'll have the option of attending for free, or
paying the $125 conference fee (all of which goes to Software Freedom
Conservancy). Please indicate your preference when emailing me, since
there is a separate code for each.
If you need financial assistance with covering travel / lodging costs,
please reach out to the Git PLC at <git@sfconservancy.org> as soon as
possible.
A few other pieces of miscellanea:
- We're still working out the exact details of an A/V setup for the
Contributor's Summit, but the plan is (as in years past) to have
some way for folks to be able to join remotely.
- We'll have some sort of experts panel at the main conference. The
exact format is TBD, but if you are interested in being on that
panel, please let me know off-list.
- We have a Google Spreadsheet that is being used to collect and vote
on topics to discuss at the Contributor's Summit[2]. If you'd like a
link to that, please also contact me off-list.
The main conference schedule and agenda should be up sometime this week
at the usual location below:
https://git-merge.com
Thanks,
Taylor
[1]: https://lore.kernel.org/git/YqjEAEPYEJMUx8Wu@nand.local/
[2]: https://lore.kernel.org/git/YtHuuE42bogVLOGn@nand.local/
next reply other threads:[~2022-07-17 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 20:00 Taylor Blau [this message]
2022-07-17 20:01 ` [ANNOUNCE] Contributor's Summit Registration, Sept 14, 2022, Chicago Taylor Blau
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YtRqU5rAOsLw5s03@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).