git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Derrick Stolee" <stolee@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: Contributor Summit planning
Date: Mon, 13 Aug 2018 15:44:35 -0400	[thread overview]
Message-ID: <20180813194435.GD10013@sigill.intra.peff.net> (raw)
In-Reply-To: <87h8jyrtj6.fsf@evledraar.gmail.com>

On Mon, Aug 13, 2018 at 08:49:33PM +0200, Ævar Arnfjörð Bjarmason wrote:

>  * I think we should tread carefully when it comes to say some form of
>    remote A/V participation open to the Internet.
> 
>    It was fine to have Dscho on a chair, but it would be quite different
>    if this were say streamed on YouTube and everyone felt like they were
>    on stage the whole time, and if offhand comments / jokes etc. were
>    recorded.
> 
>    I'm not categorically against that, it's just something to think
>    carefully about. Maybe if there's demand for it we could dedicate
>    some time slot to that.

Interesting points. I had in mind that the "invite list" for remote
would be the same as for in-person. I also am not categorically against
some kind of wider output for part of event, but I do think the casual
and intimate nature is most of what makes the event useful.

>  * Re the second half of "Not everyone can travel or can afford to do
>    so" from Derrick, there's been travel sponsorships in past years.

Yes, and I think we should continue with that offer. That's mostly been
paid out from project funds in past years, but I suspect we could dig up
sponsorship specific to the event if we had to.

> [...]
>    Or would those companies be OK with trusting that some 20-ish of us
>    can hold our tongues for one day and not ruin the surprise?

Also good points. Obviously it's up to whoever is trying to keep their
secret what they want to do, but my opinion is that it's reasonable to
talk about things the day before. I really enjoyed in one of the early
years (Berlin 2013, I think) when Michael Haggerty gave two talks on
git-imerge: one to the general population that might be interested in
using it, and one to developers that really went into detail on the
theory of how it worked.

Another option I know we've discussed is having the contributor summit
the day _after_ the main conference. That really complicates the
logistics, though, because usually we piggy-back on the main event
space, which we already have available the day before for
main-conference setup and for training. I think it would also conflict
with people wanting to go to FOSDEM on the following day.

But I'll mention it to the folks organizing for this year to see if we
can work something out. Secrets aside, I think it would be fun to have a
session discussing all of the stuff we just heard about the day before. ;)

-Peff

  reply	other threads:[~2018-08-13 19:44 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 16:31 Contributor Summit planning Jeff King
2018-08-13 16:58 ` Derrick Stolee
2018-08-13 17:15   ` Jeff King
2018-08-27 13:22     ` Johannes Schindelin
2018-08-27 13:30       ` Derrick Stolee
2018-08-28 12:22         ` Johannes Schindelin
2018-08-28 19:06         ` Jonathan Nieder
2018-08-28 19:11           ` Jonathan Nieder
2018-08-29 14:38           ` Johannes Schindelin
2018-08-29  4:52       ` Jeff King
2018-08-29 14:44         ` Johannes Schindelin
2018-08-13 17:46 ` Stefan Beller
2018-08-14  4:31   ` Christian Couder
2018-08-14 14:35     ` Jeff King
2018-08-13 18:49 ` Ævar Arnfjörð Bjarmason
2018-08-13 19:44   ` Jeff King [this message]
2018-08-13 20:36   ` Junio C Hamano
2018-08-13 20:41     ` Stefan Beller
2018-08-13 21:06       ` Jeff King
2018-08-13 21:19         ` Stefan Beller
2018-08-13 21:54           ` Jeff King
2018-08-14 17:43             ` Measuring Community Involvement (was Re: Contributor Summit planning) Derrick Stolee
2018-08-14 19:36               ` Jeff King
2018-08-14 19:47                 ` Stefan Beller
2018-08-14 20:06                   ` Jeff King
2018-08-15  7:12                     ` Eric Wong
2018-08-14 20:42                 ` Junio C Hamano
2018-08-27 15:54                   ` Johannes Schindelin
2018-08-15 16:28               ` Duy Nguyen
2018-08-27 15:55                 ` Johannes Schindelin
2018-08-14 14:30         ` Contributor Summit planning Duy Nguyen
2018-08-14 14:47           ` Jeff King
2018-08-14 16:57             ` Stefan Beller
2018-08-14 20:59             ` Junio C Hamano
2018-08-17 15:18       ` Duy Nguyen
2018-08-27 22:49   ` Johannes Schindelin
2018-08-29  5:02     ` Jeff King
2018-08-14  6:52 ` Elijah Newren
2018-08-14 13:25   ` Randall S. Becker
2018-08-14 14:06     ` Ævar Arnfjörð Bjarmason
2018-08-14 14:30       ` Jeff King
2018-08-14 14:28     ` Jeff King
2018-08-27 13:34 ` Johannes Schindelin
2018-08-29  4:55   ` Jeff King
2018-08-29 14:46     ` Johannes Schindelin
2018-08-30  3:20       ` Jeff King
2018-08-30 11:36         ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2018-03-03 10:30 Jeff King
2018-03-03 10:39 ` Jeff King
2018-03-05 14:29   ` Derrick Stolee
2018-03-05 17:01   ` Brandon Williams
2018-03-05 18:29   ` Lars Schneider
2018-03-05 18:53     ` Jonathan Nieder
2018-03-05 22:13       ` Ævar Arnfjörð Bjarmason
2018-03-05 21:57     ` Ævar Arnfjörð Bjarmason
2018-03-05 14:34 ` Ævar Arnfjörð Bjarmason

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

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

  git send-email \
    --in-reply-to=20180813194435.GD10013@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=stolee@gmail.com \
    /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.
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 NNTP newsgroup(s).