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

Re: Contributor Summit planning

From
Jeff King <peff@peff.net>
Date
Aug 13, 2018, 17:15 UTC
Message-ID
<20180813171535.GA8476@sigill.intra.peff.net>
In-Reply-To
<d5d3fe71-d52b-ac9b-d48d-d288b6569e5a@gmail.com>
On Mon, Aug 13, 2018 at 12:58:54PM -0400, Derrick Stolee wrote:
> 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.

Yeah, I do worry about it splitting the attendance. It could also be a thing we do _this_ year (if we care about having something in North America), and then try to make different plans in a future year.

Show 5 quoted lines
> 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.

One year we had Dscho remote on a laptop sitting on a stool. I'm not sure how great that was for him. ;)

I agree it would be nice to include remote people, but I think it would be very important to have a good A/V setup. Passive involvement is not too hard, but I would love a setup where they could actually participate in discussions. I've seen that work in 5-10 people conferences, but I'm not sure how well even good A/V scales to 20-30.

One other thought on remote folks: IMHO one of the most valuable things about these kinds of events (especially the first ones I attended) is the informal interactions. The hallway talks and meals provide a venue for spontaneous conversation, but they also just help us understand in a visceral way that the people on the other end of our emails are actual humans. Which I think can help smooth subsequent online interactions. I'm not sure how much of that can be gained remotely.

(I don't think that's an argument against remote inclusion, just an opinion that we should continue to encourage in-person interaction).

-Peff
Previous: Derrick StoleeNext: Johannes Schindelin
Message 3 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.