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

The GitTogether

From
Scott Chacon <schacon@gmail.com>
Date
Jul 26, 2012, 22:28 UTC
Message-ID
<CAP2yMaJzJyw=9DqJzUXkkQjz_jcqB4pH=FfHFRiftC9=yC7dvg@mail.gmail.com>

For the last few years, there has been a gathering of Gitty people in Mountain View directly following the GSoC Mentor Summit that is referred to as a GitTogether:

https://git.wiki.kernel.org/index.php/GitTogether

A few of us have been talking about what we would like to do this year and thinking about the gatherings the past few years and how we could get the most out of it.

I would like to see two different gatherings this year - one that would be user-centric to gather people that use Git together with some of the developers and talk about Git from a user's perspective. The other event I would like to see would be a gathering of many of the core Git developers in a sort of hacker summit.

GitHub would like to volunteer to organize and pay for these events this year. I would like to hold the developer-centric one in Berlin in early October (a few weeks before the Mentor Summit this time) and the user one in January or February of next year.

The general idea of the developer one in October would be to get 30-40 people who work directly on Git core, JGit and libgit2 (or closely related projects) together to discuss core issues, new features, etc. GitHub can help with travel and lodging for participants who need it, but attendance would be limited to people actually working on Git the most. Similar to some of the earlier GitTogethers.

The user conference early next year would be held in San Francisco or nearby and would be a chance for people using Git to share how they're using it, what they would like to see, etc. I would expect to host far more people at this - closer to 100, something like the last GitTogether.

I'm working on putting together websites for the two events for registration, schedule and to gather topics that should be discussed. I am planning on having the talks recorded and put online as well. I wanted to get some general feedback from the ML about what they think about this plan before I finalized everything though.

For those of you who *have* been to a GitTogether, what did you find useful and/or useless about it? What did you get out of it and would like to see again? For those of you who have never been, what do you think would be useful? I was thinking for both of them to have a combination of short prepared talks, lightning/unconference style talks and general discussion / breakout sessions.

Finally, is there any feedback on the times and places - especially the Berlin one. If nobody can agree on a better specific time, I'll push forward with early October in Berlin, but if there is a concensus around a different time, I'm fine moving it.

Scott
Next: Heiko Voigt
Message 1 of 23 in “The GitTogether”
  1. Scott ChaconJul 26, 2012
  2. Heiko VoigtJul 27, 2012
  3. Thomas RastJul 27, 2012
  4. Jens LehmannJul 29, 2012
  5. Michael J GruberJul 30, 2012
  6. Michael J GruberAug 9, 2012
  7. Patrick RenaudAug 10, 2012
  8. Junio C HamanoAug 10, 2012
  9. Michael HaggertySep 19, 2012
  10. Sebastian SchuberthSep 20, 2012
  11. Christian CouderSep 21, 2012
  12. Shawn PearceSep 21, 2012
  13. Jeff KingSep 21, 2012
  14. Christian CouderSep 21, 2012
  15. Patrick RenaudSep 21, 2012
  16. Scott ChaconSep 21, 2012
  17. Patrick RenaudSep 21, 2012
  18. Luca MilanesioSep 21, 2012
  19. Scott ChaconSep 21, 2012
  20. Sebastian SchuberthSep 21, 2012
  21. Michael J GruberSep 22, 2012
  22. Sebastian SchuberthSep 22, 2012
  23. Enrico WeigeltSep 22, 2012

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.