Skip to content

Historic: Sprint: IETF80Sprint

Robert Sparks edited this page Apr 26, 2023 · 1 revision

IETF80 Code Sprint

The IETF 80 Code Sprint in Prague will focus on enhancements to the current tracker, and on starting to use parts of the new database scheme. The Sprint will be run in the same way as the successful IETF77Sprint and IETF78Sprint where we completed and released a good number of individual enhancements.

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

This sprint will take place from 9:30 to 18:00 in the 'Chez Louis Salon' on Mezzanine Level A (map). The coding will end 18:00 on the dot, with dinner and follow-up afterwards.

We have the mailing list "[email protected]" 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 [email protected].

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 Prague!

This sprint's plan

  • Primary focus: Add new functionality you've wanted to have in the datatracker.
  • Secondary: Do test coding against the available tables in the new database model.

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 :-)

Who Short Description Link to EnhancementIdeas item
Adam Roach ical link from agenda page http://trac.tools.ietf.org/tools/ietfdb/ticket/601
Peter Musgrave IPR column consistency http://trac.tools.ietf.org/tools/ietfdb/ticket/552
Peter Musgrave Don't show Last Call if N/A http://trac.tools.ietf.org/tools/ietfdb/ticket/550
Lars Eggert additional work needed on #537 #537

Completed code ready for merge and release

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 80 Sprint is [email protected].

Who branch@revision Changelog message Release status Notes
Robert Sparks sprint/80/rjs@2939 make DEFER easier to find Fixes #627
Peter Musgrave sprint/80/peter@2945 IPR column for IESG agenda Fixes #552
Robert Sparks sprint/80/rjs@2947 Cleaning up display of DISCUSSes from ex-ADs Fixes #608
Robert Sparks sprint/80/rjs@2949 Provide a view of docs in IETF LC Fixes #630
Peter Musgrave sprint/80/peter@2965 Don't show last call Fixes #550
Peter Musgrave sprint/80/peter@2968 Fix typo Fixes #566

Wishlist (for this sprint or future sprints)

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

Prerequisites

  • A working knowledge of python and/or web design

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

  • Review the new database schema and models (see http://merlot.tools.ietf.org/src/db/new/redesign)

  • Bring a laptop with Python (2.5/2.6), Subversion and 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.

Clone this wiki locally