|
Size: 1150
Comment:
|
Size: 4311
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Given the recent spate of successful sprints, Google decided it would be a good idea to host a sprint. We've been talking about it since PyCon. Jeremy finally got the ball rolling. | = Google Python Sprint 2007 = |
| Line 3: | Line 3: |
| We plan to hold the sprint Aug 21-24, 2006. This date should be after 2.5 is released (early August). There will be 2 locations: Google's New York City office, and Google's Mountain View, California office. 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. Please add your name below if you are interested. | ''If you plan or hope to attend, please sign up below so we can have your badge ready at the lobby. (Googlers: please sign up so we can plan the space accordingly.)'' |
| Line 5: | Line 5: |
| The goals of the sprint have not yet been defined. We should try to fix any serious 2.5 bugs as well as cleanup the code to prepare for 2.6. Let us know if you have any questions. | * When: August 22-25, 9:30 am - 5:30pm local time * Where: * Mountain View Google Campus - University Theater Bldg 40 * Chicago Google Engineering office * '''Possibly also in the Kirkland (WA) office!''' For more information on the Chicago sprint, see http://mail.python.org/pipermail/chicago/2007-August/002401.html == Goals and Suggested Sprint Areas == The primary focus will be on getting new features into 3.0 before the first alpha. We hope to have a solid, stable and reasonably complete 3.0a1. You can make this happen and have fun doing it! Come join us. Some suggestions: * Python 3000 (for tasks and status, see ["Python3000"]) * Cleanup for 2.6/3.0 transition * Documentation for the transition * Add fixers to the 2to3 tool * Add your ideas here == Attendees Sign Up Here == || Name || Dates || Location || Googler? || || Neal Norwitz || 22-25 || MTV || Yes || || Guido van Rossum || 22-24 || MTV || Yes || || Talin || 22-25 || MTV || Yes || || Collin Winter || 22-25 || MTV || Yes || || Alex Martelli || ????? || MTV || Yes || || Brian Fitzpatrick || ????? || CHI || Yes || || Skip Montanaro || 22-23 || CHI || No || || Peter Fein || ????? || CHI || No || || Hasan Diwan || all days (evenings only) || MTV || NO || == Food == We'll be providing lunch and dinner to our attendees and breakfast will be available from the micro-kitchens. 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 |
| Line 8: | Line 47: |
| Attendees: || Name || Location || Dates || || Jeremy Hylton || NYC || Aug 21-24 || || Neal Norwitz || NYC? || Aug 21-24 || |
== Security - MTV == Badges will be provided to all attendees. Please wear them at all times. |
| Line 13: | Line 50: |
| Suggested sprint areas: * 2.5 bug fixing * Cleanup for 2.6 * New features for 2.6 (PEP may be required) * Add your ideas here |
== More on Location == === Mountain View === 1600 Amphitheatre Parkway, CA 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 you are here for the Python Sprint and you will receive a badge.) === Chicago === Chicago Sales & Engineering Office, 20 West Kinzie St., Chicago, IL 60610 More info: http://www.google.com/corporate/address.html == 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.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" 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, half a dozen 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, nnorwitz@gmail.com. Various [http://freenode.net/ Freenode IRC] channels appear to be unused: #py3k, #pysprint, #sprynt, etc.. I could register one if there was interest, but it's not strictly required. --pfein on irc://irc.freenode.net |
Google Python Sprint 2007
If you plan or hope to attend, please sign up below so we can have your badge ready at the lobby. (Googlers: please sign up so we can plan the space accordingly.)
- When: August 22-25, 9:30 am - 5:30pm local time
- Where:
- Mountain View Google Campus - University Theater Bldg 40
- Chicago Google Engineering office
Possibly also in the Kirkland (WA) office!
For more information on the Chicago sprint, see http://mail.python.org/pipermail/chicago/2007-August/002401.html
Goals and Suggested Sprint Areas
The primary focus will be on getting new features into 3.0 before the first alpha. We hope to have a solid, stable and reasonably complete 3.0a1. You can make this happen and have fun doing it! Come join us.
Some suggestions:
- Python 3000 (for tasks and status, see ["Python3000"])
- Cleanup for 2.6/3.0 transition
- Documentation for the transition
- Add fixers to the 2to3 tool
- Add your ideas here
Attendees Sign Up Here
Name
Dates
Location
Googler?
Neal Norwitz
22-25
MTV
Yes
Guido van Rossum
22-24
MTV
Yes
Talin
22-25
MTV
Yes
Collin Winter
22-25
MTV
Yes
Alex Martelli
?????
MTV
Yes
Brian Fitzpatrick
?????
CHI
Yes
Skip Montanaro
22-23
CHI
No
Peter Fein
?????
CHI
No
Hasan Diwan
all days (evenings only)
MTV
NO
Food
We'll be providing lunch and dinner to our attendees and breakfast will be available from the micro-kitchens. 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, CA 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 you are here for the Python Sprint and you will receive a badge.)
Chicago
Chicago Sales & Engineering Office, 20 West Kinzie St., Chicago, IL 60610
More info: http://www.google.com/corporate/address.html
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.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" 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, half a dozen 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, nnorwitz@gmail.com.
Various [http://freenode.net/ Freenode IRC] channels appear to be unused: #py3k, #pysprint, #sprynt, etc.. I could register one if there was interest, but it's not strictly required. --pfein on irc://irc.freenode.net