Skip to content

Historic: Sprint: IETF82Sprint

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

IETF82 Code Sprint

The IETF 82 Code Sprint in Taipei 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 IETF82SprintSignUp page.

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

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

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

Who branch@revision Changelog message Notes Merged Released
RjS personal/rjs/v3.63@3599 Changed the AD status page to group documents by current state. Also fixed one .txt file that wasn't turning autoescape off d51adcf2b3b3afee89c41db734784c3330a58305
RjS personal/rjs/v3.63@3601 Marked ex-ADs with square brackets 11002891fd25df4f2686596c702ae8c5131b192e
Lars personal/lars/v3.63@3602 Fix typo.
Lars personal/lars/v3.63@3603 Automatically set the recipients of RFC5742 review emails sent by the IESG based on the RFC Stream. Fixes #744.
RjS personal/rjs/v3.63@3612 Set the stream when editing/adding a document fixes #743

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