From: "Shawn O. Pearce" <spearce@spearce.org>
To: Scott Chacon <schacon@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org, gittogether@lists.utsl.gen.nz
Subject: Re: GitTogether '09
Date: Wed, 18 Mar 2009 09:11:18 -0700 [thread overview]
Message-ID: <20090318161118.GG23521@spearce.org> (raw)
In-Reply-To: <d411cc4a0903180905x1cb2a1c2j87922300dbf77e7b@mail.gmail.com>
Scott Chacon <schacon@gmail.com> wrote:
> On Wed, Mar 18, 2009 at 7:35 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> > There is also the most popular issue of budgets. ??GitTogether '08
> > wasn't free for us. ??Its cheaper than anything we would get from a
> > conference venue/hotel outside the Googleplex, but it still was a
> > non-trivial sum. ??We simply may not have the funds for it this year.
>
> Let me know if I can help out at all. If Google doesn't want to host
> it, but everyone still wants to string together the GSOC summit and
> this, I'm sure GitHub can find a nice venue for us and get some food
> and whatnot. Or, if we can simply 'sponsor' it or something - give
> the Goog money to host it for us, however that might work. We want to
> help this happen again this year, so keep me in the loop and we can
> make sure it gets handled somehow.
Hey Scott, thanks. FWIW, Google doesn't co-sponsor events. So if we
do host it, we'll cover everything like we did last year, but maybe
GitHub can sponsor an off-site dinner again, like it did last year.
But perhaps this year you guys could select the venue for that. :-)
Anyway, today is not the best day to go asking for budget and time
from LH (big GSoC announcement today). Give me a week or two to
figure out if Google can host us here or in Portland. FWIW, last
year Portland around the Linux Plumbers conference was tossed out
as an option, but it was too close calendar wise to be possible
for planning purposes.
--
Shawn.
next prev parent reply other threads:[~2009-03-18 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:16 Google Summer of Code 2009 - Organization Application Shawn O. Pearce
2009-03-10 12:42 ` Jakub Narebski
2009-03-10 14:24 ` Shawn O. Pearce
2009-03-18 5:51 ` GitTogether '09 Christian Couder
2009-03-18 6:46 ` Sverre Rabbelier
2009-03-18 7:05 ` Christian Couder
2009-03-18 9:54 ` Sverre Rabbelier
2009-03-18 14:35 ` Shawn O. Pearce
2009-03-18 14:53 ` Johannes Schindelin
2009-03-18 15:55 ` Shawn O. Pearce
2009-03-22 22:00 ` [Gittogether] " Sam Vilain
2009-03-22 22:01 ` Sam Vilain
2009-03-18 16:05 ` Scott Chacon
2009-03-18 16:11 ` Shawn O. Pearce [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-28 18:53 gittogether '09 Brandon Casey
2009-08-28 19:17 ` Shawn O. Pearce
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=20090318161118.GG23521@spearce.org \
--to=spearce@spearce.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gittogether@lists.utsl.gen.nz \
--cc=schacon@gmail.com \
--cc=srabbelier@gmail.com \
/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.