git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Christian Couder <chriscool@tuxfamily.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: Sat, 23 Aug 2008 12:42:50 -0700	[thread overview]
Message-ID: <20080823194250.GA876@spearce.org> (raw)
In-Reply-To: <200808230726.03606.chriscool@tuxfamily.org>

Christian Couder <chriscool@tuxfamily.org> wrote:
> 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.

Hmm.  Not only that, but a number of our users come out to the
Mentor Summit.  ~170 open souce projects send folks to that summit,
and a fair percentage of those are now in Git.  Many who travel
far for the summit already plan to stay a few days if they can.

-- 
Shawn.

  parent reply	other threads:[~2008-08-23 19:43 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 [this message]
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=20080823194250.GA876@spearce.org \
    --to=spearce@spearce.org \
    --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=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).