-
Notifications
You must be signed in to change notification settings - Fork 393
Historic: Sprint: IETF99Sprint
The IETF 99 Code Sprint 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 IETF99SprintSignUp page.
This sprint will take place from 9:30 to 18:00 in meeting room Karlin III.
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/99/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 [email protected].
For information on setting up your environment, code checkout and commit, etc., see the [SprintCoderSetup(https://github.com/ietf-tools/datatracker/wiki/SprintCoderSetup) with Docker] page.
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 Prague!
- 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 ** |
|---|---|---|
| Russ | Update the IPR pages for RFC 8179 | 2309 |
| Dave Allan | Group status not allowed to be empty | 2183 |
| Seth Birkholz | Send mail when a new shepherd is set | 1309 |
| Jean | Materials management should highlight when you are adding materials to a session that has not been scheduled | 2084 |
| RjS | Don't 500 when deleting and then uploading new minutes | 2286 |
|---|---|---|
| RjS | Fix links for editing titles of agendas, etc. | 2317 |
| Peter Yee | Allow ADs to manage meeting materials | 2213 |
| RjS | Include drafts associated with sessions when building session pdfs and tarballs | 2036 |
| Jean | Fixing annoying differences in generated ID-Action emails | 1519 |
| RjS | Better timestamps on newrevisiondocevent when uploading materials | 2039 |
| DIA | Null WG status or ambiguous source of status not allowed, all changes to ietf/group/forms.py | 2183 |
| Ali | Add "last updated" timestamps on meeting materials page | 1644 |
| Ali | Request for better punctuation on state change messages | 1545 |
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 with Python 2.7, Subversion and (optionally) Mysql (5.x) 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 1.7 at DebianWheezySetup)