All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>,
	Christian Couder <chriscool@tuxfamily.org>
Cc: "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: Fri, 22 Aug 2008 07:34:07 -0700	[thread overview]
Message-ID: <20080822143407.GE3483@spearce.org> (raw)
In-Reply-To: <7v7ia9d0of.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <chriscool@tuxfamily.org> writes:
> > Le jeudi 21 août 2008, Shawn O. Pearce a écrit :
> >> Christian Couder <chriscool@tuxfamily.org> wrote:
> >>
> >> Google has offered to help us organize a Gittogether in Portland
> >> if we desire.
> 
> > 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: [  <big text box thingy>    ]

	5: Would you volunteer to help organize it?
	
		Trick question.  Email blah@blah to indicate how you can help.
 
> This reminds me...  I'll be offline from 24 or 25 of September for two
> weeks or so, and need to ask somebody most likely Shawn to keep an eye 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.

-- 
Shawn.

  reply	other threads:[~2008-08-22 14:35 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 [this message]
     [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
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=20080822143407.GE3483@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.