From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org, gittogether@lists.utsl.gen.nz
Subject: Re: GitTogether '09
Date: Wed, 18 Mar 2009 07:35:32 -0700 [thread overview]
Message-ID: <20090318143532.GD23521@spearce.org> (raw)
In-Reply-To: <fabb9a1e0903180254u5569e9f5u5e1aa43fa2d1d178@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Wed, Mar 18, 2009 at 08:05, Christian Couder <chriscool@tuxfamily.org> wrote:
> > I thought that it was only one international airplane ticket last year,
> > except perhaps when there are no US based mentor. And we are not sure that
> > Google or another company in the Bay Area will be able to host us this
> > year. So the cost of hosting the GitTogether might be higher than the cost
> > of a few airplane tickets.
>
> Last year Google provided two international airplane tickets and was
> able to host us, we can at least ask them to host us again this year
> (if that is what we decide on).
Did Google do two international tickets last year for Git? Hmm,
don't go spreading that word around. Very few groups got that
amount of travel money for the mentor summit. Maybe none others.
IMHO, _if_ Git is accepted this year, and _if_ the mentor summit is
held this fall as it has been in the past, Google will most likely
cover only one ticket, especially if we actually also supported a
GitTogether immediately after.
> Shawn, how likely is it that Google will provide hosting for another
> GitTogether this year?
I will ask.
Last year it was difficult on LH. Despite the fact that most of
the attendees probably never even met her, she put a lot of work
into the GitTogether behind the scenes. Without her efforts,
the GitTogether simply would not have happened here.
It was also *immediately* after the biggest event of the year
that she and her team run (GSoC mentor summit), and really close
to two other very big events that they run. They were working
pretty much 7 days a week for over 3 months straight, and were
really looking forward to some time off when I threw GitTogether
'08 into their calendar.
I'm not sure I can ask LH to put her and her team through that again.
I want to continue living. :-)
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.
--
Shawn.
next prev parent reply other threads:[~2009-03-18 14:37 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 [this message]
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
-- 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=20090318143532.GD23521@spearce.org \
--to=spearce@spearce.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gittogether@lists.utsl.gen.nz \
--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 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).