-
Notifications
You must be signed in to change notification settings - Fork 383
Historic: Sprint: IETF83Sprint
The IETF 83 Code Sprint in Paris 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 IETF83SprintSignUp page.
This sprint will take place from 9:30 to 18:00 in room Hall Maillot A. 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 Paris!
- Primary focus: Get aquainted with the new database models
- Secondary: Add new functionality you've wanted to have in the datatracker, using the new database models.
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 |
|---|---|---|
| Suresh | Show writeup for normal users | http://trac.tools.ietf.org/tools/ietfdb/ticket/679 |
| Tony | looking at bibxml generation |
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 83 Sprint is [email protected].
| Who | branch@revision | Changelog message | Notes | Merged | Released |
|---|---|---|---|---|---|
| [email protected] | personal/shane/v4.00rc2@4204 | Adds a link to the datatracker main document page in the new-version notification messages | comment:#802:5 | a1f3f48aa00ddffa9b5bfa37e024c8e6899854be | |
| [email protected] | personal/adam/v4.00rc2@4207 | Ported week view over to use the new meeting data model | dc41de99d0d7726519cfb8d399671f78124edeab | ||
| [email protected] | personal/shane/v4.00rc24205 | Added a link to the datatracker main document page when we announce a new document | comment:#801:3 | c39dff8d7a381274bef47231052cd3974adbb371 | |
| Suresh | personal/suresh/v4.00@4213 | Making doc writeup available as read-only text to regular users who are not shepherd/AD/Secretariat etc. Adding a link for viewing a writeup to the main datatracker page. | comment:#679:7 | 0e3de358344d187b2834d5c8a24f2955ba92c583 | |
| [email protected] | personal/york/v4.00@4214 | Turns datatracker.ietf.net in the site header into a clickable link bringing users back to the top level page. | comment:#816:3 | 6d1ef8d8dd9e020af98e8cac9968d28a593f4cff | |
| rcross | personal/rcross/v4.00@4212 | Add the ability for the secretariat to clear a ballot to the tracker | comment:#673:4 | 4034532ea15e55b0335849d681ecd43cae714906 | |
| [email protected] | personal/york/v4.00@4223 | Added 401.html to provide better user experience for authentication failure. | comment:#817:2 | 4d93301a52056040b91b33485512fc4bf11a3746 | |
| [email protected] | personal/york/v4.00@4224 | Made IETF logo in the header clickable | 257f677efcfa2334f99ed9bc7a0921629c233305 | ||
| [email protected] | personal/adam/v4.00@4226 | Updated agenda.ics to use new data model. Also, tons more efficient. Additionally, the description field now includes links to relevant meeting materials. | 484eb752411d455150902f1a14df4ce5027a80dd |
Other work completed:
| Who | Notes |
|---|---|
| [email protected] | fix xml2rfc experimental page to work again |
| [email protected] | add link to GUI packages to xml2rfc experimental page |
| [email protected] | add option to experimental page to grab xml from a URL |
| [email protected] | add agenda venue maps |
| [email protected] | created the url-shortening code that will sit behind ietf.at |
| [email protected] | Made weekly creation of .mobi and .epub files of RFCs, Documents for each Area, and Documents for each WG. |
| [email protected] | Area review team review tool: Fixed datatracker idnum links to use new style datatracker/doc/ links. |
| [email protected] | Area review team review tool: Implemented http://wiki.tools.ietf.org/tools/art/trac/ticket/9 |
| [email protected] | Area review team review tool: Implemented http://wiki.tools.ietf.org/tools/art/trac/ticket/4 |
| [email protected] | Area review team review tool: Implemented http://wiki.tools.ietf.org/tools/art/trac/ticket/10 |
See (and add to) the list started at EnhancementIdeas -- current method of adding items is to open a new trac ticket.
-
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.