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 Feb 2, 2017, Brussels
Date: Mon, 5 Dec 2016 08:35:19 -0500	[thread overview]
Message-ID: <20161205133519.dsjhaptk6ezl63zr@sigill.intra.peff.net> (raw)

Git Merge 2017 is happening on Feb 3rd; there will be a Contributor's
Summit the day before. The details are largely what I wrote earlier in
[1], but here's a recap:

  When: Thursday, Feb 2, 2017. 10am-3pm.
  Where: The Egg[2], Brussels, Belgium
  What: Git nerds having a round-table discussion
  Who: All contributors to git or related projects in the git ecosystem
       are invited; if you're not sure if you qualify, just ask!

Registration for the conference is open, and you need to register
specifically for the Contributor's Summit to attend. There's a special
code for registering for the Contributor's Summit; email me off-list to
get instructions. It works either when registering for the main
conference, or separately. You don't have to attend the main conference
on Friday to come to the Contributor's Summit, but I encourage you to.

As I mentioned before, the content is up to us. So start thinking of
things you'd like to discuss. We can probably organize topics on the
kernel.org wiki (if anybody really wants to start things going, feel
free to start a wiki page).

Let me know if you have any questions.

-Peff

[1] http://public-inbox.org/git/20161025162829.jcy6fmnmdjual6io@sigill.intra.peff.net/

[2] https://www.google.com/maps/place/The+Egg/@50.8357424,4.321425,15z/data=!4m13!1m7!3m6!1s0x0:0xe028c6680611d1da!2sThe+Egg!3b1!8m2!3d50.8331946!4d4.3270469!3m4!1s0x0:0xe028c6680611d1da!8m2!3d50.8331946!4d4.3270469


                 reply	other threads:[~2016-12-05 13:45 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=20161205133519.dsjhaptk6ezl63zr@sigill.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).