git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.H." <warthog19@eaglescrag.net>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <gitster@pobox.com>,
	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: Fri, 22 Aug 2008 22:25:31 -0700	[thread overview]
Message-ID: <1219469131.2642.75.camel@localhost.localdomain> (raw)
In-Reply-To: <200808230726.03606.chriscool@tuxfamily.org>

I know I haven't chimed in yet - As for the mentor summit itself I
wouldn't mind attending, but if there are others who would like to go I
won't begrudge them attending.  That also said I live in the Bay area,
and while I think I'll change apartments at some point, if people want
to crash at my place I've got an air mattress and futon people are more
than welcome to occupy.

- John


On Sat, 2008-08-23 at 07:26 +0200, Christian Couder wrote:
> Le samedi 23 août 2008, Shawn O. Pearce a écrit :
> > Junio C Hamano <gitster@pobox.com> wrote:
> > > "Shawn O. Pearce" <spearce@spearce.org> writes:
> > > > Junio C Hamano <gitster@pobox.com> wrote:
> > > > ...
> > > >
> > > >> If Git-together happens outside of that, I could join.
> > > >
> > > > I think it would be after that.  I doubt we could put it together
> > > > with <30 days of notice.  Most people who would want to attend need
> > > > to book travel arrangements.  While its possible with 30 days notice
> > > > you can typically get better rates if you have more lead time.
> > >
> > > Ah, I somehow got a wrong impression about this event from the initial
> > > posting, and certainly didn't imagine you were planning a
> > > mini-conference like one, but a much more informal and smaller "while
> > > some of us are in the west coast during/near GSoC mentor thing, how
> > > about getting together for fun" kind of settings.
> >
> > Well, we could do that too.  But I think we'd want to maybe do that
> > closer to Mountain View, where the actual summit is taking place,
> > to cut down on the amount of travelling that the out-of-town folks
> > have to do.
> >
> > E.g. you could come up this year, and we'll have maybe 3 or 4 of
> > our mentors here for the summit.  We could even do a mini-one day
> > thing at the Google campus.  I could probably get Google to give us a
> > small conference room or tech talk room for half a day or something.
> 
> I think it needs to be at least 2 days long for people coming from Europe or 
> farther, otherwise it might not be worth it for them to come. Or it needs 
> to happen during, after or before another interesting conference.
> 
> The Google Mentor Summit is in Mountain View:
> 
> - October 25(Sat)-26(Sun)
> (http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_timeline)
> 
> Maybe we can have the GitTogether also in Montain View just after that: 
> 
> - October 27(Mon)-28(Tue)
> 
> so that the 3 mentors that come to the mentor summit just have to stay to 2 
> more days there.
> 
> > I don't really know what our community is interested in doing.
> > So I'm just tossing out ideas and seeing what sticks.  If we don't
> > do anything, that's fine too.
> 
> Or maybe we can just plan something for next year.
> 
> Thanks,
> Christian.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-08-23  5:27 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. [this message]
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
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=1219469131.2642.75.camel@localhost.localdomain \
    --to=warthog19@eaglescrag.net \
    --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=sam.vilain@catalyst.net.nz \
    --cc=spearce@spearce.org \
    /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).