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

Re: The GitTogether

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jul 30, 2012, 13:17 UTC
Message-ID
<5016894C.7020907@drmicha.warpmail.net>
In-Reply-To
<50155CD9.6060702@web.de>
Jens Lehmann venit, vidit, dixit 29.07.2012 17:55:
Show 6 quoted lines
> Am 27.07.2012 13:45, schrieb Thomas Rast:
>> Scott Chacon <schacon@gmail.com> writes:
>>
>>> 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

Winter term classes start 10/15. Before 10/15 it will be easier to book university rooms if we need that.

Show 5 quoted lines
>>
>> Yay, Berlin!  I would be glad to join there; I would probably not have
>> the time and resources to travel to SF this year.
> 
> Same here.
Same.

Do we have contacts regarding (un)conference rooms in Berlin already? I might be able to ask around.

Show 27 quoted lines
> 
>>> 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.
>>
>> I was at the 2010 GitTogether in Mountain View.  I really liked the
>> unconference format, and the way Shawn and Junio used it: just using the
>> topic stickers as a sort of todo-list, not actually fixing any schedule
>> in advance.  Oddly enough we also managed to avoid the usual consequence
>> of open-ended discussions: getting stuck endlessly on an absolutely
>> insignificant point.
> 
> Yup, the unconference format with both common and breakout sessions
> worked really well.
> 
>> I think the discussions were very productive.  I would love to do more
>> hacking than we managed in 2010, but I realize that this is not possible
>> if we just meet for 2-3 days.  Perhaps one option would be to plan for
>> 1-2 days of hacking after the discussion rounds, so that the interested
>> people can stay a bit longer?
> 
> I really like that idea and would vote for 3-4 days (maybe including a
> weekend for those of us who have to take a leave from work ;-).
> 
Previous: Jens LehmannNext: Michael J Gruber
Message 5 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.