list mirror (unofficial, one of many)
 help / color / Atom feed
From: Jeff King <>
Subject: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels
Date: Fri, 9 Nov 2018 05:42:02 -0500
Message-ID: <> (raw)

Git Merge 2019 is happening on February 1st. There will be a
Contributor's Summit the day before. Here are the details:

  When: Thursday, January 31, 2019. 10am-5pm.
  Where: The Egg[1], Brussels, Belgium
  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 the invite codes
yet.  Registration should be similar to past years. In particular, if
you're coming to the contrib summit, DON'T register for the main
conference yet. I think the codes I get will cover both (and as with
previous years, contrib summit attendees will have the option of a
complimentary pass to the main conference, or can pay €99 that goes to
Software Freedom Conservancy).

The content / agenda is whatever we choose. There's some more discussion
on format in this thread from August:

though it sounds like people are mostly on board with what we've done in
past years. I'm looking into getting better A/V for remote attendance,
but I'm not sure yet what will be possible.

Any thoughts or discussion on format, content, etc are welcome. The only
thing set so far is the time and place. :)


[1] This is the same venue as 2017:

             reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 10:42 Jeff King [this message]
2018-11-09 10:44 ` Luca Milanesio
2018-11-09 10:48   ` Jeff King
2018-11-14 12:31     ` Luke Diamand
2018-11-14 12:53       ` Jeff King
2019-02-20 12:48 ` Git Merge Conference Recordings [was: Re: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels] Thomas Braun
2019-02-20 13:03   ` Ævar Arnfjörð Bjarmason
2019-02-21  4:59     ` Jeff King
2019-02-21  8:22       ` Jeff King
2019-02-21 21:27         ` Thomas Braun
2019-03-16 15:31         ` Christian Couder

Reply instructions:

You may reply publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox