-
Notifications
You must be signed in to change notification settings - Fork 392
Historic: Sprint: IETF103Sprint
The IETF 103 Code Sprint on 3 November in Bangkok will, as always, let you work on fixing those things about the datatracker which you most urgently desire to do something about.
The Sprint will be run according to the IETFSprintHowto.
If you plan to participate, please sign up on the IETF103SprintSignUp page.
This sprint will take place from 9:30 to 18:00 in meeting room Apartment 1.
The coding will end 18:00 on the dot, with dinner afterwards. The meeting rooms map will help you find the way here: https://datatracker.ietf.org/meeting/103/floor-plan
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 xmpp:[email protected]?join
For information on setting up your environment, code checkout and commit, etc., see the SprintCoderSetup page.
During the sprint, please update the two tables below; this helps both with coordination and with getting the code merged, released, and deployed :-)
- Address whatever is bothering you the most
- Identify an area of code which lacks testing coverage, and write tests
- 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 :-)
| Who | Short Description | **Related ticket numbers ** |
|---|
| Who | Short Description | **Related ticket numbers ** |
|---|---|---|
| Robert Sparks | Let review teams opt in to poking a responsible AD when unhappy reviews are submitted | 2544 |
| Robert Sparks | Let a reviewer indicate that an AD should give this review early attention | 2553 |
| Jean Mahoney | "Ballot issued" emails use future tense for events in the past | 2482 |
| Robert Sparks | Issues with returning to Bof from Bof Concluded | 2597 |
| Robert Sparks | Avoid issues with the Document Admin modelform | 2524 |
| Jean Mahoney | The title value for the session requests page is referencing a bad variable | 2608 |
| Jean Mahoney | Main /person view says incorrect things if there's more than one person with the same name | 2616 |
| Jean Mahoney | Broken link on interim request page | 2564 |
| Robert Sparks | Clearly show cancelled sessions on the week-view part of the agenda page | 2619 |
| Robert Sparks | Email the RFC Editor if RFC Editor notes change after a draft was approved | 2440 |
| Tero Kivinen | The review assignment should also show the already assigned review requests | 2131 |
| Peter Yee | Minor article disagreement in NomCom feedback text | 2621 |
| Tero Kivinen | Added easier to detect error message when search returns 0 results. | 2126 |
When you are ready to commit code which is ready form merge and release,
please use the phrase Commit ready for merge in your commit message, if
all related changes are contained in one commit, or Branch ready for merge
if all your commits to your branch, up to the current, should be merged as
one unit. This is described more extensively in CodeRepository#Requestingamergetotrunk
For sprint work on other things than the datatracker, please fill in the following table:
| Who | Notes | |
|---|---|---|
| Jari Arkko | For the personal RFC/draft lists produced by authorstats, order the lists by RFC number. Works now, tested and in operation! |
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.
-
A working knowledge of python and/or web design
-
Learn the basic concepts of Django 1.10, e.g., work through the excellent tutorial.
-
Bring a laptop ready to be set up with (or better, already setup with) a development environment. See SprintCoderSetup.