git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Cc: Christian Couder <chriscool@tuxfamily.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	David Symonds <dsymonds@gmail.com>,
	"J.H." <warthog19@eaglescrag.net>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Sam Vilain <sam.vilain@catalyst.net.nz>,
	Junio C Hamano <gitster@pobox.com>, Petr Baudis <pasky@suse.cz>
Subject: [ANNOUNCE] GitTogether '08 (Developer/User Summit Oct 27-29)
Date: Mon, 8 Sep 2008 15:11:04 -0700	[thread overview]
Message-ID: <20080908221104.GA14448@spearce.org> (raw)

Google is hosting GitTogether '08, October 27th through 29th,
at its Mountain View, CA headquarters.

This GitTogether immediately follows the Google Summer of Code
mentor summit, so some of our end-user groups may already have
representatives in the area.  We've timed the GitTogether to follow
the summit so we can get some users to attend while they are still
in the area.

Git contributors and users alike are welcome to attend.  Admission is
free (as everything is being donated by Google), but you will need
to arrange for your own travel and lodging.  If you are looking
at flights try the SJC and SFO airports.  SFO usually has cheaper
flights as its a bigger, more active airport.

At this point we are looking to solicit proposals for talks,
round-table discussions, centers of focus for patch hack-a-thons,
etc.  I'm not certain what sort of facilities (in terms of meeting
spaces) we will have available to us yet, and to some extent that
may depend on what our program becomes.  I'm thinking we should
schedule at least one or two day days of the time for unconference
style activities[*1*]

There's also a pretty good cadry of Git users within Google.  If we
can get some interesting Git developers here on-site I'd like to
arrange for some of the talks to be Google Tech Talks, so people
can benefit even if they cannot attend in person.  We may be able
to get such talks up on Google Video once they clear security.

The Git Wiki page is being used for planning:

  http://git.or.cz/gitwiki/GitTogether

and of course, so is this email thread.  ;-)


*1* http://en.wikipedia.org/wiki/FooCamp

-- 
Shawn.

                 reply	other threads:[~2008-09-08 22:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080908221104.GA14448@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=pasky@suse.cz \
    --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).