From: Michael J Gruber <git@drmicha.warpmail.net>
To: unlisted-recipients:; (no To-header on input)
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Thomas Rast <trast@student.ethz.ch>,
Scott Chacon <schacon@gmail.com>, git list <git@vger.kernel.org>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Shawn Pearce <spearce@spearce.org>
Subject: Re: The GitTogether
Date: Thu, 09 Aug 2012 18:38:22 +0200 [thread overview]
Message-ID: <5023E77E.4020604@drmicha.warpmail.net> (raw)
In-Reply-To: <5016894C.7020907@drmicha.warpmail.net>
Michael J Gruber venit, vidit, dixit 30.07.2012 15:17:
> Jens Lehmann venit, vidit, dixit 29.07.2012 17:55:
>> 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.
>
>>>
>>> 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.
>
>>
>>>> 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 ;-).
While the unconference format is successful, may I suggest a
track/topic: Especially if there's GitHub support and participation this
would be a good opportunity to discuss some GitHub specific issues in
person rather than via the list or support tickets. Two come to my mind:
1) GitHub for Git developers: I certainly don't suggest a change in
workflow for git.git, but you often hear Git developers say "we can't do
this or that on GitHub", and I think GitHub (and other projects using
GitHub) could benefit from the specific point of view and input of Git
developers to improve workflow support on GitHub.
2) git-scm.com: The old Git website and wiki certainly did not quite
meet GitHub's demands (e.g. reliability, looks), and git-scm.com
certainly does not quite meet the/all Git developers demands (e.g. list
discussion based decisions and actions, separation between the "free
project" and "business related content). In person it may be easier to
find a way forward which benefits all parts of the large and undefined
"Git community".
Cheers,
Michael
next prev parent reply other threads:[~2012-08-09 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 22:28 The GitTogether Scott Chacon
2012-07-27 6:12 ` Heiko Voigt
2012-07-27 11:45 ` Thomas Rast
2012-07-29 15:55 ` Jens Lehmann
2012-07-30 13:17 ` Michael J Gruber
2012-08-09 16:38 ` Michael J Gruber [this message]
2012-08-10 14:42 ` Patrick Renaud
2012-08-10 16:30 ` Junio C Hamano
2012-09-19 13:43 ` Michael Haggerty
2012-09-20 18:53 ` Sebastian Schuberth
2012-09-21 9:20 ` Christian Couder
2012-09-21 14:05 ` Shawn Pearce
2012-09-21 14:18 ` Jeff King
2012-09-21 15:23 ` Christian Couder
2012-09-21 16:43 ` Patrick Renaud
2012-09-21 16:45 ` Scott Chacon
2012-09-21 16:55 ` Patrick Renaud
2012-09-21 16:57 ` Luca Milanesio
2012-09-21 14:19 ` Scott Chacon
2012-09-21 14:33 ` Sebastian Schuberth
2012-09-22 10:12 ` Michael J Gruber
2012-09-22 10:45 ` Sebastian Schuberth
2012-09-22 18:09 ` Enrico Weigelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5023E77E.4020604@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
--cc=spearce@spearce.org \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).