-
Notifications
You must be signed in to change notification settings - Fork 393
Historic: Sprint: IETF90Sprint
The IETF 90 Code Sprint in Toronto will be working on several tools, with a focus on the new datatracker release.
The Sprint will be run according to the IETFSprintHowto.
If you plan to participate, please sign up on the IETF90SprintSignUp page.
This sprint will take place from 9:30 to 18:00 in meeting room "British Columbia". 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 Toronto!
- Address whatever is bothering you the most
- 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 ** |
|---|---|---|
| Dapeng Liu | Send a note to a questionnaire submitter when their feedback is classified as a questionnaire response | https://trac.tools.ietf.org/tools/ietfdb/ticket/1161 |
| Dapeng Liu | History tab: Show when IPR disclosures were posted. | https://trac.tools.ietf.org/tools/ietfdb/ticket/477 |
| Dapeng Liu | "Adopt in group" function doesn't show IRTF RGs | https://trac.tools.ietf.org/tools/ietfdb/ticket/1082 |
| Peng Fan | Make it easier to find subscription info and archive of a WG mailing list | http://trac.tools.ietf.org/tools/ietfdb/ticket/958 |
| Peng Fan | Solve defects on document page | http://trac.tools.ietf.org/tools/ietfdb/ticket/1112 |
| Peng Fan | Solve defects on document page | http://trac.tools.ietf.org/tools/ietfdb/ticket/1432 |
| Gang Chen | To not annotate groups from the same area, and display another area name the groups belong to | https://trac.tools.ietf.org/tools/ietfdb/ticket/1368 |
| Shane Kerr | days in IETF state has a calculation bug | http://trac.tools.ietf.org/tools/ietfdb/ticket/1312 |
| Lars Eggert | datatracker bootstrap facelift | |
| Hui Deng | add revision number to ballot | https://trac.tools.ietf.org/tools/ietfdb/ticket/911 |
| Cong Liu | Secretariat must get email notification when a charter enters internal or external | |
| Zhen Cao | Notify authors/shepherds when a draft is scheduled on a telechat | https://trac.tools.ietf.org/tools/ietfdb/ticket/978 |
| Qi Sun | ADs have to put a document into the IETF stream before they can change the replaces relationships | http://trac.tools.ietf.org/tools/ietfdb/ticket/1305 |
| Shane Kerr | Untrack this document button on drafts | http://trac.tools.ietf.org/tools/ietfdb/ticket/1381 |
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.
With the 5.0.0 release we moved to Django 1.6. This new version is in your sprint branch and should be picked up automatically. We are also using Python 2.7 in production, and that version should be used for development.
The last of the shim layer has been removed, and the structure of project has been cleaned up. Files under /doc, in particular, may have moved since you looked at them last. Take a moment to look around at the new structure and ask if you're not finding where things went quickly.
The test suite has been modified to run much more quickly than it has in the past. Please run it before you make any changes to the code in your branch. Then run the often while you're working. Keep an eye out for opportunities to add to the test suite as you go.
-
A working knowledge of python and/or web design
-
Learn the basic concepts of Django 1.6, e.g., work through the excellent tutorial.
-
Bring a laptop with Python 2.7, Subversion and (optionally) 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. (Some hints on preparing mac laptops are at MacSetup, hints for Debian 7 at DebianWheezySetup)