git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Contributor Summit planning
Date: Mon, 13 Aug 2018 12:58:54 -0400	[thread overview]
Message-ID: <d5d3fe71-d52b-ac9b-d48d-d288b6569e5a@gmail.com> (raw)
In-Reply-To: <20180813163108.GA6731@sigill.intra.peff.net>

On 8/13/2018 12:31 PM, Jeff King wrote:
> For the past several years, we've held a Git Contributor Summit as part
> of the Git Merge conference. I'd like to get opinions from the community
> to help plan future installments. Any feedback or opinion is welcome,
> but some obvious things to think about:
>
>    - where, when, and how often?
>
>      Plans are shaping up to have Git Merge 2019 in Brussels right after
>      FOSDEM in February (like it was two years ago), with a contributor
>      summit attached.
>
>      Are there people who would be more likely to attend a contributor
>      summit if it were held elsewhere (e.g., in North America, probably
>      in the Bay Area)? Are people interested in attending a separate
>      contributor summit not attached to the larger Git Merge (and if so,
>      is there any other event it might be worth connecting it with,
>      time-wise)?  Are people interested in going to two summits in a year
>      (e.g., Brussels in February, and then maybe some in North America
>      later in the year), or is that diminishing returns?

I've only been to one contributor summit, but found it extremely useful 
in meeting community members face-to-face. I think the time spent was 
very productive.

I would be up for two meetings a year. I would expect that the variety 
of locations would allow a larger set of contributors to make at least 
one meeting a year. This may come at a cost of a smaller group in each 
summit.

>
>    - format
>
>      For those who haven't attended before, it's basically 25-ish Git
>      (and associated project) developers sitting in a room for a day
>      chatting about the project. Topics go on a whiteboard in the
>      morning, and then we discuss each for 30-60 minutes.
>
>      We could do multiple days (which might give more room for actually
>      working collaboratively instead of just discussing). We could do
>      something more formal (like actual talks). We could do something
>      less formal (like an all-day spaghetti buffet, where conversation
>      happens only between mouthfuls). The sky is the limit. Some of those
>      ideas may be better than others.

The one thing I found missing that could be good is to have a remote 
option. Not everyone can travel or can afford to do so. I wonder if a 
simple Google Hangout could allow more participation from the community, 
even in a passive sense (those still at their day jobs listening in). It 
could even facilitate remote presenters, if applicable.

> I hope this can stimulate a discussion on the list, but of course if
> anybody has private feedback about past events or future planning, feel
> free to email me off-list.

Thanks for starting the discussion early!

-Stolee


  reply	other threads:[~2018-08-13 16:58 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 [this message]
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
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=d5d3fe71-d52b-ac9b-d48d-d288b6569e5a@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).