From: Sam Vilain <sam.vilain@catalyst.net.nz>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>,
"J.H." <warthog19@eaglescrag.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>,
David Symonds <dsymonds@gmail.com>,
git@vger.kernel.org
Subject: Re: Gittogether event?
Date: Tue, 26 Aug 2008 16:30:47 +1200 [thread overview]
Message-ID: <1219725047.11792.81.camel@maia.lan> (raw)
In-Reply-To: <20080822143407.GE3483@spearce.org>
Figure I may as well answer this, given it's addressed to me :)
On Fri, 2008-08-22 at 07:34 -0700, Shawn O. Pearce wrote:
> 1: Are you interested in attending a Gittogether:
> [ ] Yes [ ] No
Yes, but happy to participate in technical events via telemetry.
> 2: Would you travel to Portland, Oregon for the Gittogether:
> [ ] Yes [ ] No
Sure, but only if several people thought it would be worth blowing US
$1400 of community funds on my ticket ... that's what it costs to get
across the Pacific!
> 3: What month/year would be best?
> Option list for next 12 months from Oct 08-Oct 09.
The summit time is actually quite good for me.
> 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> ]
The main reason I'd be interested in joining would be to talk to people
about the gittorrent project, or any other similar "cloud computing"
over git ideas. There was a bit of difference of opinions, and some
divergence of ideas that was possibly avoidable. It would be good to
"crack out" the concepts with a group of people "in person". I'm pretty
sure there's already a videoconference setup at Catalyst, or if not
there could be one jimmied up easily enough. So that might be a nice
cheap thing to do - I can give a 30 minute overview of the technology,
and hopefully participate in group discussion for another 30 minutes (or
as long as people are interested in the discussion really).
Of course I'd equally like to meet people... that's all good and
fun :-). And I've got connections in Portland as well. I just think
it's probably not the best use of community funds.
> 5: Would you volunteer to help organize it?
I'd volunteer for anything, but you'd better turn it down I'd be
hopeless ;-).
Sam
next prev parent reply other threads:[~2008-08-26 4:50 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
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 [this message]
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=1219725047.11792.81.camel@maia.lan \
--to=sam.vilain@catalyst.net.nz \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).