|
Size: 605
Comment:
|
Size: 3945
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Add planned sprints to this page. Feel free to create new wiki pages for planning your sprint in detail. | Please add planned sprints to this page. Feel free to create new wiki pages for planning your sprint in detail. |
| Line 3: | Line 3: |
| = Saturday, March 19 = | = Introduction = == What is a sprint? == A sprint is a focused development session, in which developers pair in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers work in pairs using XP's pair programming approach. The sprint approach works best when the first few hours are spent getting oriented -- presenting a tutorial for the development material, laying out the stories to tackle for the day, getting everyone a CVS or SVN checkout to work with. [http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html ZopeMag's miniGuide to Zope Sprinting] is a good introductory article; just mentally remove every "Zope" from the article to make it generic. == Why sprint at PyCon? == The sprints are intended to benefit various projects, and to encourage more people to take part in development. They will also be a good place to see ExtremeProgramming or other AgileMethods in action, and to work closely with experienced Python developers. PyCon will always have a core Python sprint. Other topics will come and go each year. If you wish to participate in a sprint, please contact the sprint organizers in advance! Sprint topics are listed below. (Can we get a link to a common reference page describing how Sprints work, for those whom this is their first sprint? Does each person bring a laptop? Do we use a private LAN in the sprint room or have Internet access to a Subversion server? How is chaos avoided?) = Schedule = == Saturday, March 19 == |
| Line 7: | Line 34: |
| Zope3Sprint | Zope3Sprint (Coach: Garrett Smith) |
| Line 9: | Line 36: |
| ZODBSprint | ZodbSprint |
| Line 11: | Line 38: |
| = Sunday, March 20 = | Zope3AppSprint PyCoreAstSprint PyPySprint (10am - whenever, Coordinator: Jacob Hallén) EmailSprint (Coach: Barry Warsaw) MailmanThreeSprint (Coach: Barry Warsaw) DistutilsSprint (Coach: Fred Drake) == Sunday, March 20 == |
| Line 15: | Line 54: |
| Zope3Sprint | Zope3Sprint (Coach: Garrett Smith) |
| Line 17: | Line 56: |
| ZODBSprint | ZodbSprint |
| Line 19: | Line 58: |
| = Monday, March 21 = | Zope3AppSprint PyCoreAstSprint PyPySprint (10am - whenever, Coordinator: Jacob Hallén) EmailSprint (Coach: Barry Warsaw) MailmanThreeSprint (Coach: Barry Warsaw) DistutilsSprint (Coach: Fred Drake) == Monday, March 21 == |
| Line 23: | Line 74: |
| Zope3Sprint | Zope3Sprint (Coach: Garrett Smith) |
| Line 25: | Line 76: |
| ZODBSprint | ZodbSprint |
| Line 27: | Line 78: |
| = Tuesday, March 22 = | Zope3AppSprint PyCoreAstSprint PyPySprint (10am - whenever, Coordinator: Jacob Hallén) EmailSprint (Coach: Barry Warsaw) MailmanThreeSprint (Coach: Barry Warsaw) DistutilsSprint (Coach: Fred Drake) ChandlerSprint2005 (Coach: Ted Leung) == Tuesday, March 22 == |
| Line 31: | Line 96: |
| Zope3Sprint | Zope3Sprint (Coach: Garrett Smith) |
| Line 33: | Line 98: |
| ZODBSprint | ZodbSprint Zope3AppSprint PyCoreAstSprint PyPySprint (10am - whenever, Coordinator: Jacob Hallén) EmailSprint (Coach: Barry Warsaw) MailmanThreeSprint (Coach: Barry Warsaw) DistutilsSprint (Coach: Fred Drake) ChandlerSprint2005 (Coach: Ted Leung) = Possible Sprint Topics = == Python Core == * rewrite setup.py * rewrite site.py * handle bugs / patches = Logistics = Location: GWU (rooms TBD). Time: TBD. Date: Saturday March 19 through Tuesday March 22 inclusive. Cost to attend: Free! Bring: Your laptop and a wireless card. = Who makes this possible? = The [http://www.python.org/psf Python Software Foundation ] is sponsoring the sprints for PyConDC2005. Please consider making a [http://www.python.org/psf/donations.html donation] to support this vital community activity! |
Please add planned sprints to this page. Feel free to create new wiki pages for planning your sprint in detail.
Introduction
What is a sprint?
A sprint is a focused development session, in which developers pair in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers work in pairs using XP's pair programming approach.
The sprint approach works best when the first few hours are spent getting oriented -- presenting a tutorial for the development material, laying out the stories to tackle for the day, getting everyone a CVS or SVN checkout to work with.
[http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html ZopeMag's miniGuide to Zope Sprinting] is a good introductory article; just mentally remove every "Zope" from the article to make it generic.
Why sprint at PyCon?
The sprints are intended to benefit various projects, and to encourage more people to take part in development. They will also be a good place to see ExtremeProgramming or other AgileMethods in action, and to work closely with experienced Python developers.
PyCon will always have a core Python sprint. Other topics will come and go each year.
If you wish to participate in a sprint, please contact the sprint organizers in advance! Sprint topics are listed below.
(Can we get a link to a common reference page describing how Sprints work, for those whom this is their first sprint? Does each person bring a laptop? Do we use a private LAN in the sprint room or have Internet access to a Subversion server? How is chaos avoided?)
Schedule
Saturday, March 19
BetterZope2BlobSupportSprint (11am - 6pm, Coach: ChrisMcDonough )
Zope3Sprint (Coach: Garrett Smith)
PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
EmailSprint (Coach: Barry Warsaw)
MailmanThreeSprint (Coach: Barry Warsaw)
DistutilsSprint (Coach: Fred Drake)
Sunday, March 20
BetterZope2BlobSupportSprint (11am - 6pm, Coach: ChrisMcDonough )
Zope3Sprint (Coach: Garrett Smith)
PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
EmailSprint (Coach: Barry Warsaw)
MailmanThreeSprint (Coach: Barry Warsaw)
DistutilsSprint (Coach: Fred Drake)
Monday, March 21
CanDo (9am - 4pm, Coach: AlanElkner )
Zope3Sprint (Coach: Garrett Smith)
PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
EmailSprint (Coach: Barry Warsaw)
MailmanThreeSprint (Coach: Barry Warsaw)
DistutilsSprint (Coach: Fred Drake)
ChandlerSprint2005 (Coach: Ted Leung)
Tuesday, March 22
CanDo (9am - 4pm, Coach: AlanElkner )
Zope3Sprint (Coach: Garrett Smith)
PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
EmailSprint (Coach: Barry Warsaw)
MailmanThreeSprint (Coach: Barry Warsaw)
DistutilsSprint (Coach: Fred Drake)
ChandlerSprint2005 (Coach: Ted Leung)
Possible Sprint Topics
Python Core
* rewrite setup.py
* rewrite site.py
* handle bugs / patches
Logistics
- Location: GWU (rooms TBD). Time: TBD. Date: Saturday March 19 through Tuesday March 22 inclusive. Cost to attend: Free! Bring: Your laptop and a wireless card.
Who makes this possible?
The [http://www.python.org/psf Python Software Foundation ] is sponsoring the sprints for PyConDC2005. Please consider making a [http://www.python.org/psf/donations.html donation] to support this vital community activity!