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

Contributor Summit planning

From
Jeff King <peff@peff.net>
Date
Aug 13, 2018, 16:31 UTC
Message-ID
<20180813163108.GA6731@sigill.intra.peff.net>

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?
  - 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 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.

-Peff
Next: Derrick Stolee
Message 1 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.