git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Contributor Summit planning

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 27, 2018, 13:34 UTC
Message-ID
<nycvar.QRO.7.76.6.1808271523180.73@tvgsbejvaqbjf.bet>
In-Reply-To
<20180813163108.GA6731@sigill.intra.peff.net>
Hi Peff,
On Mon, 13 Aug 2018, Jeff King wrote:
Show 19 quoted lines
> 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 cannot speak for "the people", but for myself: Brussels is an ideal location *for me*. I would probably be unable to physically go to a second, in-person meeting in the same year, but I would of course love to attend remotely.

Show 13 quoted lines
>   - 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.
I found the unconference-style, one day meeting to be most productive.

As to more formal? I don't know... talks seem to be fun and all, but they require a lot of preparation. Something championed in our standups are "chalk talks", i.e. somebody presenting in a bit more detail what they are working on, in particular explaining the context (think: Stolee enlightening the audience about finer points of computational graph theory) *without* preparing for it specifically. That makes for fun presentations, if a bit more chaotic than a real "conference talk". This format obviously lends itself to Google Hangouts.

As to multiple days: Of course it would be nice to have a kind of a "hack day", but I wonder how productive this would be in the context of Git, where interests very so widely.

Rather than have a "hack day", I would actually prefer to work with other contributors in a way that we have not done before, but which I had the pleasure of "test ballooning" with Pratik: using Visual Studio Code Live Share. This allows multiple users to work on the same code base, in the same worktree, seeing what each other is doing. It requires a separate communication channel to talk; Pratik & I used IRC, but I think Google Hangout (or Skype or WhatsApp or <insert-your-favorite-chat-here>) would have worked a bit better. It's kind of pair programming, but with some of the limitations removed.

I guess I went off on a tangent here...

Ciao, Dscho

Previous: Jeff KingNext: Jeff King
Message 43 of 47 in “Contributor Summit planning”
  1. Jeff KingAug 13, 2018
  2. Derrick StoleeAug 13, 2018
  3. Jeff KingAug 13, 2018
  4. Johannes SchindelinAug 27, 2018
  5. Derrick StoleeAug 27, 2018
  6. Johannes SchindelinAug 28, 2018
  7. Jonathan NiederAug 28, 2018
  8. Jonathan NiederAug 28, 2018
  9. Johannes SchindelinAug 29, 2018
  10. Jeff KingAug 29, 2018
  11. Johannes SchindelinAug 29, 2018
  12. Stefan BellerAug 13, 2018
  13. Christian CouderAug 14, 2018
  14. Jeff KingAug 14, 2018
  15. Ævar Arnfjörð BjarmasonAug 13, 2018
  16. Jeff KingAug 13, 2018
  17. Junio C HamanoAug 13, 2018
  18. Stefan BellerAug 13, 2018
  19. Jeff KingAug 13, 2018
  20. Stefan BellerAug 13, 2018
  21. Jeff KingAug 13, 2018
  22. Measuring Community Involvement (was Re: Contributor Summit planning)Derrick Stolee, Aug 14, 2018
  23. Jeff KingAug 14, 2018
  24. Stefan BellerAug 14, 2018
  25. Jeff KingAug 14, 2018
  26. Eric WongAug 15, 2018
  27. Junio C HamanoAug 14, 2018
  28. Johannes SchindelinAug 27, 2018
  29. Duy NguyenAug 15, 2018
  30. Johannes SchindelinAug 27, 2018
  31. Duy NguyenAug 14, 2018
  32. Jeff KingAug 14, 2018
  33. Stefan BellerAug 14, 2018
  34. Junio C HamanoAug 14, 2018
  35. Duy NguyenAug 17, 2018
  36. Johannes SchindelinAug 27, 2018
  37. Jeff KingAug 29, 2018
  38. Elijah NewrenAug 14, 2018
  39. Randall S. BeckerAug 14, 2018
  40. Ævar Arnfjörð BjarmasonAug 14, 2018
  41. Jeff KingAug 14, 2018
  42. Jeff KingAug 14, 2018
  43. Johannes SchindelinAug 27, 2018
  44. Jeff KingAug 29, 2018
  45. Johannes SchindelinAug 29, 2018
  46. Jeff KingAug 30, 2018
  47. Johannes SchindelinAug 30, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.