Differences between revisions 11 and 47 (spanning 36 versions)
⇤ ← Revision 11 as of 2005-01-18 18:47:52 →
Size: 2830
Editor: AndrewKuchling
Comment: Add material from old page
← Revision 47 as of 2008-11-15 14:00:54 → ⇥
Size: 5122
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#acl All:read
The sprint rooms are 301 and 307 on the third floor of the Marvin Center, and sprints will run from 8am to 6pm (roughly) each day from Saturday March 19 through Tuesday March 22. Further information, including a link to directions, under ''Logistics'' below.
Line 9: Line 12:
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 checkout to work with. 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.
Line 11: Line 14:
[http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html ZopeMag's miniGuide to Zope Sprinting] [[http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html|ZopeMag's miniGuide to Zope Sprinting]]
Line 26: Line 29:
(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?) (Do we use a private LAN in the sprint room or have Internet access to a Subversion server? How is chaos avoided?)
Line 28: Line 31:
= Saturday, March 19 = = Schedule =

== Saturday, March 19 ==

   CanDo (Plone/PostgreSQL Application 9am - 6pm, Coach: Alan Elkner )
Line 32: Line 39:
   Zope3Sprint    Zope3Sprint (time: 9am - 6pm, Coach: Garrett Smith)
Line 40: Line 47:
= Sunday, March 20 =    PyPySprint (10am - whenever, Coordinator: Jacob Hallén)

   EmailSprint ('''withdrawn''')

   Mailman3Sprint (Coach: Barry Warsaw)

   DistutilsSprint (Coach: Fred Drake)

   TwistedSprint

   WsgiKitSprint (maybe...?)

== Sunday, March 20 ==

   CanDo (Plone/PostgreSQL Application 9am - 6pm, Coach: Alan Elkner )
Line 44: Line 65:
   Zope3Sprint    Zope3Sprint (time: tba, Coach: Garrett Smith)
Line 52: Line 73:
= Monday, March 21 =    PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
Line 54: Line 75:
   CanDo (9am - 4pm, Coach: AlanElkner )    EmailSprint ('''withdrawn''')
Line 56: Line 77:
   Zope3Sprint    Mailman3Sprint (Coach: Barry Warsaw)

   DistutilsSprint (Coach: Fred Drake)

   TwistedSprint

   WsgiKitSprint (maybe...?)

   UnununiumSprint

== Monday, March 21 ==

   CanDo (Plone/PostgreSQL Application 9am - 6pm, Coach: Alan Elkner )

   Zope3Sprint (time: tba, Coach: Garrett Smith)
Line 64: Line 99:
= Tuesday, March 22 =    PyPySprint (10am - whenever, Coordinator: Jacob Hallén)
  
   MatplotlibSprint (Coach: John Hunter)
Line 66: Line 103:
   CanDo (9am - 4pm, Coach: AlanElkner )    EmailSprint ('''withdrawn''')
Line 68: Line 105:
   Zope3Sprint    Mailman3Sprint (Coach: Barry Warsaw)

   DistutilsSprint

   ChandlerSprint2005 (Coach: Ted Leung)

   TwistedSprint

   WsgiKitSprint (Coach: Ian Bicking)

== Tuesday, March 22 ==

   CanDo (Plone/PostgreSQL Application 9am - 6pm, Coach: Alan Elkner )

   Zope3Sprint (time: tba, Coach: Garrett Smith)
Line 76: Line 127:
   PyPySprint (10am - whenever, Coordinator: Jacob Hallén)

   EmailSprint ('''withdrawn''')

   Mailman3Sprint (Coach: Barry Warsaw)

   DistutilsSprint

   ChandlerSprint2005 (Coach: Ted Leung)

   TwistedSprint

   WsgiKitSprint (Coach: Ian Bicking)

   AdaptersAndInterfacesSprint (Coach: Bruce Eckel)

= Possible Sprint Topics =

JythonSprint?
SWTSprint?

== Python Core ==

* rewrite setup.py

* rewrite site.py
  I'd like to see something like {{{site.addsitedir()}}} made into a public API so that additional directories of ''.pth'' files can be processed in a consistent manner without having to re-implement that machinery. -- FredDrake

* handle bugs / patches
Line 78: Line 160:
 Location: TBD.  Location: GWU on the third floor of the Marvin Conference Center: http://cafritz.gwu.edu/Directions
Line 80: Line 162:
 Time: TBD.  Rooms: probably 301, 307, and, on Monday and Tuesday, 310.

 Time: Starting 8 am Saturday
Line 86: Line 170:
 Bring: Your laptop and a wireless card.  Bring: Your laptop and a wireless card (though a wired network infrastructure will also be available).
Line 88: Line 172:
 IRC: #pycon on irc.freenode.net
Line 91: Line 176:
The [http://www.python.org/psf  Python Software Foundation ]
is sponsoring the sprints for PyConDC2004.
Please consider making a [http://www.python.org/psf/donations.html donation] 		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]]

The sprint rooms are 301 and 307 on the third floor of the Marvin Center, and sprints will run from 8am to 6pm (roughly) each day from Saturday March 19 through Tuesday March 22. Further information, including a link to directions, under Logistics below.

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.

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.

(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

Sunday, March 20

Monday, March 21

Tuesday, March 22

Possible Sprint Topics

JythonSprint? SWTSprint?

Python Core

* rewrite setup.py

* rewrite site.py

  • I'd like to see something like site.addsitedir() made into a public API so that additional directories of .pth files can be processed in a consistent manner without having to re-implement that machinery. -- FredDrake

* handle bugs / patches

Logistics

  • Location: GWU on the third floor of the Marvin Conference Center: http://cafritz.gwu.edu/Directions Rooms: probably 301, 307, and, on Monday and Tuesday, 310. Time: Starting 8 am Saturday Date: Saturday March 19 through Tuesday March 22 inclusive. Cost to attend: Free! Bring: Your laptop and a wireless card (though a wired network infrastructure will also be available). IRC: #pycon on irc.freenode.net

Who makes this possible?

The Python Software Foundation is sponsoring the sprints for PyConDC2005. Please consider making a donation to support this vital community activity!

CategoryPyCon2005

PyConDC2005/Sprints (last edited 2008-11-15 14:00:54 by localhost)

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