From: Christian Couder <chriscool@tuxfamily.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
"J.H." <warthog19@eaglescrag.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>,
Sam Vilain <sam.vilain@catalyst.net.nz>,
David Symonds <dsymonds@gmail.com>,
git@vger.kernel.org
Subject: Re: Gittogether event?
Date: Mon, 25 Aug 2008 21:15:09 +0200 [thread overview]
Message-ID: <200808252115.09916.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20080822143407.GE3483@spearce.org>
Le vendredi 22 août 2008, Shawn O. Pearce a écrit :
>
> This smells like a survey to me. ;-)
Yes, and here is my answer. (I had to discuss a little with my wife so took
me some time to come up with it.)
> We should put together something really short, and try to get folks
> to answer it, not just from our developer list, but maybe also our
> user communities. Maybe something like:
>
> 1: Are you interested in attending a Gittogether:
> [ ] Yes [ ] No
Yes, definitely.
> If you answered no, you can give up on the survey now.
>
> 2: Would you travel to Portland, Oregon for the Gittogether:
> [ ] Yes [ ] No
Yes or to San Fransisco. I will probably stay 3 or 4 days even if I don't
attend any other conference/event. Any free accomodation would be greatly
appreciated.
(Flight costs from Paris France are about 550 EUR (825 US$) for Portland
Oregon around the 20th of September and 630-670 EUR (950-1000 US$) for San
Fransisco around the 27th of October. Flights takes between 13 and 23 hours
each as they are not direct.)
> 3: What month/year would be best?
> Option list for next 12 months from Oct 08-Oct 09.
Oct 08 is ok. After that I would prefer between May 09 and Oct 09.
Anyway not Nov 08 or Dec 08.
> 4: What would you hope to see/accomplish while there?
> [ ] Instructor-lead Git training
> [ ] 24 hour hack-a-new-feature contest
> [ ] ... ?
> Enter other ideas: [ <big text box thingy> ]
I'd like small sessions (half a day/night long) that go like this:
- 1 hour long presentation and discussion: someone talks about a topic and
some problems about it, then we discuss what could be done about this topic
- a few hours long hacking: we try to implement solutions for problems
related to the previous discussion.
But I guess anything will do.
> 5: Would you volunteer to help organize it?
Yes. Though I am probably not in the best place to help. But I can start to
gather some information on a web page on the wiki or something.
> Trick question. Email blah@blah to indicate how you can help.
Thanks,
Christian.
next prev parent reply other threads:[~2008-08-25 19:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080820151031.GD3483@spearce.org>
[not found] ` <200808210432.10544.chriscool@tuxfamily.org>
[not found] ` <20080821144537.GM3483@spearce.org>
2008-08-22 3:36 ` Gittogether event? (was: GSoC 2008 final evaluations) Christian Couder
2008-08-22 6:27 ` Gittogether event? Junio C Hamano
2008-08-22 14:34 ` Shawn O. Pearce
[not found] ` <32541b130808220739x632d1590v7894b7dfe94c4de@mail.gmail.com>
2008-08-22 14:44 ` Shawn O. Pearce
2008-08-22 16:00 ` Petr Baudis
2008-08-22 16:06 ` Petr Baudis
2008-08-22 16:14 ` Shawn O. Pearce
2008-08-22 18:58 ` Andreas Ericsson
2008-08-22 21:17 ` Junio C Hamano
2008-08-23 0:31 ` Shawn O. Pearce
2008-08-23 5:26 ` Christian Couder
2008-08-23 5:25 ` J.H.
2008-08-23 19:42 ` Shawn O. Pearce
2008-08-23 6:23 ` Junio C Hamano
2008-08-25 19:15 ` Christian Couder [this message]
2008-08-25 19:23 ` Shawn O. Pearce
2008-08-25 20:38 ` Johannes Schindelin
2008-08-25 21:11 ` Christian Couder
2008-08-26 4:30 ` Sam Vilain
2008-08-26 20:48 ` Christian Couder
2008-08-26 20:59 ` Daniel Barkalow
2008-08-27 23:45 ` Sam Vilain
2008-08-28 4:07 ` Christian Couder
2008-08-23 2:50 ` Gittogether event? (was: GSoC 2008 final evaluations) Greg KH
2008-08-23 5:06 ` Christian Couder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808252115.09916.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sam.vilain@catalyst.net.nz \
--cc=spearce@spearce.org \
--cc=warthog19@eaglescrag.net \
/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.
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 NNTP newsgroup(s).