From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shawn O. Pearce" Subject: Re: Gittogether event? Date: Fri, 22 Aug 2008 07:34:07 -0700 Message-ID: <20080822143407.GE3483@spearce.org> References: <20080820151031.GD3483@spearce.org> <200808210432.10544.chriscool@tuxfamily.org> <20080821144537.GM3483@spearce.org> <200808220536.15746.chriscool@tuxfamily.org> <7v7ia9d0of.fsf@gitster.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "J.H." , Johannes Schindelin , Daniel Barkalow , Sam Vilain , David Symonds , git@vger.kernel.org To: Junio C Hamano , Christian Couder X-From: git-owner@vger.kernel.org Fri Aug 22 16:35:29 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KWXjU-00030y-GV for gcvg-git-2@gmane.org; Fri, 22 Aug 2008 16:35:20 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752795AbYHVOeL convert rfc822-to-quoted-printable (ORCPT ); Fri, 22 Aug 2008 10:34:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752825AbYHVOeK (ORCPT ); Fri, 22 Aug 2008 10:34:10 -0400 Received: from george.spearce.org ([209.20.77.23]:39762 "EHLO george.spearce.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752795AbYHVOeJ (ORCPT ); Fri, 22 Aug 2008 10:34:09 -0400 Received: by george.spearce.org (Postfix, from userid 1001) id 2733438375; Fri, 22 Aug 2008 14:34:07 +0000 (UTC) Content-Disposition: inline In-Reply-To: <7v7ia9d0of.fsf@gitster.siamese.dyndns.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano wrote: > Christian Couder writes: > > Le jeudi 21 ao=C3=BBt 2008, Shawn O. Pearce a =C3=A9crit : > >> Christian Couder wrote: > >> > >> Google has offered to help us organize a Gittogether in Portland > >> if we desire. >=20 > > Here are a few question to start the discussion: > > > > What date would be best? > > Who could come? > > What needs to be done to organize it? > > Who could help organize it? This smells like a survey to me. ;-) 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 If you answered no, you can give up on the survey now. 2: Would you travel to Portland, Oregon for the Gittogether: [ ] Yes [ ] No 3: What month/year would be best? Option list for next 12 months from Oct 08-Oct 09. 4: What would you hope to see/accomplish while there? [ ] Instructor-lead Git training [ ] 24 hour hack-a-new-feature contest [ ] ... ? Enter other ideas: [ ] 5: Would you volunteer to help organize it? =09 Trick question. Email blah@blah to indicate how you can help. =20 > This reminds me... I'll be offline from 24 or 25 of September for tw= o > weeks or so, and need to ask somebody most likely Shawn to keep an ey= e on > the patchflow during that time. Enjoy your time away from the keyboard. I'd be happy to keep a patch queue for you to pick up from when you get back. > 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. --=20 Shawn.