git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git Merge Contributor's Summit, March 5, 2020, Los Angeles
Date: Fri, 13 Dec 2019 00:00:38 -0500	[thread overview]
Message-ID: <20191213050038.GA75792@coredump.intra.peff.net> (raw)

Git Merge 2020 is happening on March 4th. There will be a Contributor's
Summit the day after (not before, as in years past!). Here are the
details:

  When: Thursday, March 5th. 10am-5pm.
  Where: TBD, Los Angeles, California, USA
  What: Round-table discussion about Git
  Who: All contributors to Git or related projects in the Git ecosystem
       are invited; if you're not sure if you qualify, please ask!

This email is just to announce the date so people can start planning.
You'll need to register eventually, but I don't have details of that
procedure yet. I expect it will be similar to past years. In particular,
if you're coming to the contrib summit, DON'T register for the main
conference yet, as the registration will probably cover both. You don't
need to email me for a code yet; I'll send more details when I have
them.

Note that this is a little different from past years, in that the
contributor summit will be (by popular demand) the day _after_ the main
conference, rather than before. Hopefully this should give us the
opportunity to dissect some of the main conference talks.

The plan is to have an A/V setup sufficiently good for people to join
remotely. I'll provide details for how to do that when we get closer to
the event.

If you'd like to come but need financial assistance with travel costs,
please reach out to the Git PLC at git@sfconservancy.org. We'll collect
requests and try to make decisions and notify people by mid-January,
which would hopefully still leave time for making 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.

-Peff

                 reply	other threads:[~2019-12-13  5:00 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

  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=20191213050038.GA75792@coredump.intra.peff.net \
    --to=peff@peff.net \
    --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).