From: Stefan Beller <sbeller@google.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>
Subject: Re: Contributor Summit planning
Date: Mon, 13 Aug 2018 10:46:10 -0700 [thread overview]
Message-ID: <CAGZ79kYMV0DCd89Pw3v4d48GyQN9iQzt=XZ9=aGswHFHWhas3g@mail.gmail.com> (raw)
In-Reply-To: <20180813163108.GA6731@sigill.intra.peff.net>
On Mon, Aug 13, 2018 at 9:31 AM Jeff King <peff@peff.net> 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?
We have been kicking around the thought of reviving the GitTogethers
like back in the olden days (I only know them from hearsay), in
Mountain View or Sunnyvale at the Google Campus, but we have not yet
spent enough thought to make it so.
I think twice a year is fine for the community and has not reached the
point of diminishing returns.
As most contributors are from North America (estimated), I would not
mind a conference somewhere here.
I'd be looking forward to Brussels next February!
> - 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.
Personally I think the way is fine; we could collect topics in advance on
the list to have a head start, but the whiteboard is totally fine, IMHO.
Stefan
next prev parent reply other threads:[~2018-08-13 17:46 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 [this message]
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='CAGZ79kYMV0DCd89Pw3v4d48GyQN9iQzt=XZ9=aGswHFHWhas3g@mail.gmail.com' \
--to=sbeller@google.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).