The IETF 89 Code Sprint in London will be working on several tools, with a focus on the new datatracker release.

The Sprint will be run according to the IETFSprintHowto.

If you plan to participate, please sign up on the IETF89SprintSignUp page.

This sprint will take place from 9:30 to 18:00 in meeting rooms 13-17. The coding will end 18:00 on the dot, with dinner and follow-up afterwards.

We have the mailing list "codesprints@ietf.org" to help with coordination and for use during the event. Please make sure you're subscribed before the event starts. More info on the list is available at https://www.ietf.org/mailman/listinfo/codesprints.

There is also a jabber room at codesprint@conference.resiprocate.org.

For information on setting up your environment, code checkout and commit, etc., see the SprintCoderSetup and SprintDatabase pages.

During the sprint, please update the two tables below; this helps both with coordination and with getting the code merged, released, and deployed :-)

See you in London!

• Address whatever is bothering you the most
• Fix as many of the issues captured at EnhancementIdeas as we can.

Please consider the higher priority items first. If you're looking for a short task, look for rows marked "easy". If there's something you hope the sprint will address that's not on that list, please enter it as a new ticket using http://tools.ietf.org/tools/ietfdb/newticket

Please fill in the following table when you've picked a task for the sprint. It's quite all right to pick and complete multiple tasks :-)

Please fill in the following table when you have something which is ready to merge and release, and send a brief message to the sprint's committer to notify him about the new code. Committer for the IETF 89 Sprint is henrik@levkowetz.com.

See (and add to) the list started at EnhancementIdeas -- current method of adding items is to open a new trac ticket.

If you have time to take on larger tasks between sprints, look through the full set of open tickets at http://wiki.tools.ietf.org/tools/ietfdb/report/13 for those not marked sprint.

With the 5.0.0 release we moved to Django 1.6. This new version is in your sprint branch and should be picked up automatically. We are also using Python 2.7 in production, and that version should be used for development.

The last of the shim layer has been removed, and the structure of project has been cleaned up. Files under /doc, in particular, may have moved since you looked at them last. Take a moment to look around at the new structure and ask if you're not finding where things went quickly.

The test suite has been modified to run much more quickly than it has in the past. Please run it before you make any changes to the code in your branch. Then run the often while you're working. Keep an eye out for opportunities to add to the test suite as you go.

• A working knowledge of python and/or web design

• Learn the basic concepts of Django 1.6, e.g., work through the excellent tutorial.

• Bring a laptop with Python 2.7, Subversion and (optionally) Mysql (4.x is ok, 5.x is better) installed, and be ready to check out a branch of the IETF web site from the tools svn server. (Some hints on preparing mac laptops are at MacSetup, hints for Debian 7 at DebianWheezySetup)