Skip to content

Historic: Sprint: IETF87Sprint

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

IETF87 Code Sprint

The IETF 87 Code Sprint in Berlin will focus on enhancements to the new tracker.

The Sprint will be run according to the IETFSprintHowto.

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

This sprint will take place from 9:30 to 18:00 in room Kopenick 1/2. 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 Berlin!

This sprint's plan

Some areas that could use attention:

  • Statistics tools improvements
  • ...

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
Jari Stats bug fixes Work on some of the bugs reported on document statistics tools
RjS Display older IPR declarations better #1071
Adam Improve search over new document types #838
Russ Someone else had already done the work #986
Suresh Error in last call processing code #884
Suresh Chair annotation timeline incorrect #1046
Markus draft- and wg email list generation in Python #713

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

Who branch@revision Changelog message Notes Merged Released
adam personal/adam/v4.60@5898 Fixed bug #838 4.61
suresh personal/suresh/v4.60@5897 Fixed bug #884 4.61
suresh personal/suresh/v4.60@5899 Fixed bug #1046 4.61
RjS personal/RjS/v4.60@5900 Partially addressed #1071 addresses last call contents, but not search results yet - these are deployable separately 4.61
adam personal/adam/v4.60@5901 Fixed bug #916 4.61
adam personal/adam/v4.60@5903 Fixed bug #448 added tooltip capability to document tabs 4.61
Markus personal/markus/v4.60@5904 Implemented #713 not sure if it's complete solution yet, but seems close enough (now two sprints worth of fiddling with it, fingers crossed) 4.61

Other work completed:

Who Notes
[email protected] Closed tickets 44, 45, 46, 47, 48, 49, 50 in the review tool. http://trac.tools.ietf.org/tools/art/trac/report
Tony agenda venue online map, bib reference extraction tool

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

Clone this wiki locally