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: Contributor Summit Topics and Logistics
Date: Tue, 22 Jan 2019 02:50:27 -0500	[thread overview]
Message-ID: <20190122075027.GA29441@sigill.intra.peff.net> (raw)

The Git Merge Contributor Summit is a little over a week away. If you're
interested in coming but haven't signed up, please do! We have a few
spaces available still. Details are in the previous announcement:

  http://public-inbox.org/git/20181206094805.GA1398@sigill.intra.peff.net/

There's no set agenda; we'll decide what to discuss that day. But if
anybody would like to mention topics they are interested in (whether you
want to present on them, or just have an open discussion), please do so
here. A little advance notice can help people prepare more for the
discussions.

Even if you're not coming, please feel free to suggest topics (but bonus
points if you convince somebody who _is_ coming to lead the session).

If you're not coming, you can probably stop reading this message now.
The rest is all logistics.

We have the room available from 9am-5pm. Breakfast will be served from
9am-10am in the main area (i.e., mingling with workshop attendees and
other such ruffians). So I'd suggest to show up around 9am to get
registered and mingle, and then we can start the Very Serious Business
at 10am.

Lunch will be provided at noon, and some snacks in the afternoon.
There's no organized dinner. However, there will be a social/drinks
event for the broader conference at 7pm; I'll provide more details that
day.

For people who want to try to join remotely, I don't think we're going
to have a particularly fancy AV setup. But there should at least be a
big screen (which we typically do not really use for presenting), and I
hope we can provide some connectivity. I'll be visiting the venue the
day before (Jan 30th) in the late afternoon (Brussels time) and I'll try
to do a test run. If anybody wants to volunteer to be the guinea pig on
the other end of the line, I'd welcome it.

The physical setup this year will actually be 4 round tables, instead of
one giant table. I'm hoping this will facilitate breaking off into
sub-groups and having more intimate conversations, and maybe avoid the
"it's hard to hear people at the other end of the table" issues. Or
maybe it will just make it worse as we shout to each other from all four
tables. I can't wait to see!

If you have any other questions or ideas, please share them here (or
email me off-list if appropriate). I look forward to seeing people
there!

-Peff

             reply	other threads:[~2019-01-22  7:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  7:50 Jeff King [this message]
2019-01-22  8:26 ` Contributor Summit Topics and Logistics Jeff King
2019-01-22  9:17   ` GSoC 2019 (was: Contributor Summit Topics and Logistics) Christian Couder
2019-01-31  2:02     ` SZEDER Gábor
2019-01-31  6:11       ` Christian Couder
2019-01-22 18:21   ` Contributor Summit Topics and Logistics Stefan Beller
2019-01-22 20:53     ` Jeff King
2019-01-22 18:23 ` Derrick Stolee
2019-01-24  8:57   ` Ævar Arnfjörð Bjarmason
2019-01-29 18:22     ` Derrick Stolee
2019-01-22 20:30 ` Elijah Newren
2019-01-30 20:57 ` Ævar Arnfjörð Bjarmason
2019-01-30 22:26   ` Jeff Hostetler
2019-01-30 22:51   ` Philip Oakley
2019-01-30 23:13     ` Christian Couder
2019-01-30 23:07 ` Jeff King
2019-02-02 12:33   ` Jakub Narebski
2019-02-04 19:30     ` Elijah Newren
2019-04-23  3:45     ` Jeff King

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=20190122075027.GA29441@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).