-
Notifications
You must be signed in to change notification settings - Fork 393
Historic: Sprint: IETF104Sprint
The IETF 104 Code Sprint on 23 March in Prague 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 IETF104SprintSignUp page.
This sprint will take place from 9:30 to 18:00 with the location TBD.
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/104/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 ** |
|---|---|---|
| Jean | Color coded ballot positions | https://trac.tools.ietf.org/tools/ietfdb/ticket/886 |
| Ryan | Break scheduling bug | https://trac.tools.ietf.org/tools/ietfdb/ticket/2699 |
| --- | --- | --- |
| Russ | Add downref list to telechat package | |
| Russ | Tests for downref list in telechat package | |
| Russ | Allow Secretariat to handle downrefs when they approve a document | |
| Jean | Improve the usability of the Replaces entry field | https://trac.tools.ietf.org/tools/ietfdb/ticket/1375 |
| Who | Short Description | **Related ticket numbers ** |
|---|---|---|
| Russ | Add downref list to Secretariat telechat pages | |
| Russ | Tests for downref list in telechat package | |
| Russ | Allow Secretariat to handle downrefs when they approve a document | |
| Jean | Improve the usability of the Replaces entry field | https://trac.tools.ietf.org/tools/ietfdb/ticket/1375 |
| Kivinen | Reviewer list changes to allow team secretary to configure how many days and how many items to show. | |
| Magnus | Implemented additional columns and sorting on Review Team reviewers page | https://tools.ietf.org/tools/ietfdb/ticket/2656 |
| Jim | Move old nomcom announcements into the database | https://trac.tools.ietf.org/tools/ietfdb/ticket/2686 |
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 | |
|---|---|---|
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.