Revision 65 as of 2007-08-06 18:39:14

Clear message

Google Python Sprint 2007

We are sprinting Aug 22-25, 2007 at Google's Mountain View, California headquarters (MTV). Google's Open Source Program Office is doing much of the internal coordination with Jeremy Hylton and Neal Norwitz handling more of the technical side. We hope many Googlers and non-Googlers will participate.

Goals and Suggested Sprint Areas

Some suggestions:

Attendees

Food

We'll be providing lunch and dinner to our attendees and breakfast will be available from the microkitchens. Our guests will dine with us in our cafes for their meals.

Housing - MTV

You can book a room at The Residence Inn Palo Alto/Mountain View; ask for Google's corporate rate. If you're looking to save funds, you might consider booking a penthouse room at the property and doubling up with another attendee. http://marriott.com/property/propertypage.mi?marshaCode=SFOMV

Security - MTV Badges will be provided to all attendees. Please wear them at all times.

More on Location

Mountain View 1600 Amphitheatre Parkway, 94043 University Theatre - 2nd Flr, Building 40

Directions: [WWW] http://www.google.com/corporate/address.html#directions Guests are welcome to arrive any time after 9:30 AM.

(Non-Googlers: please go to the Building 40 reception and let the receptionist know ou are here for the Python Sprint and you will receive a badge.

Come Prepared!

Please come prepared so we won't have to waste time helping everybody with their setup. Bring a laptop (preferably running Linux or OSX; we have limited svn setup experience for other systems, esp. Windows). Make sure svn is installed: http://subversion.tigris.org/ -- Check [http://prolificprogrammer.com/~hdiwan/blog/2006/08/02/home_subversion_repository_1.html Hasans Blog Entry on subversion ] for help with other systems.

For Python 2.5/2.6, check out the head branch; see http://www.python.org/dev/faq/#subversion-svn (use the instructions for anonymous checkout unless you already have developer privileges).

For py3k, check out the "py3k-struni" branch. Also read PEPs 3000-3999.

In either case, make sure you have at least built and tested it once so you are familiar with the process. It's something like "./configure; make; make test" in the appropriate directory. (For Py3k, 25 or so tests typically fail -- a goal of the sprint will be to fix these.)

Questions

Are you guys on IRC, Google Talk, or something like that? Answer: no IRC AFAIK; some individuals can be IM'ed in gmail chat, e.g. gvanrossum@gmail.com.

No other locations? Last time there was an NYC location and had he known about it Fitz would have probably put together a Chicago location... -- SkipMontanaro

Unable to edit the page? See the FrontPage for instructions.