Historic: Sprint: IETF107.1Sprint

IETF107.1 Online Code Sprint

The IETF Code Sprint will let you work on those things about the IETF tools, particularly the IETF Datatracker, that you most urgently desire to fix.

Do you have:

A desire to fix Datatracker bugs, implement Datatracker EnhancementIdeas, and/or identify areas of code that lack testing coverage and write tests for those areas?
A working knowledge of python and/or web design?
Understanding of the basic concepts of Django 1.11? Here is an excellent tutorial if not.
A computer ready to be set up (or better, already setup) with a development environment? See SprintCoderSetup for information on setting up your environment, checking out and committing code, etc

If so, please sign up on the IETF107.1SprintSignUp page.

This sprint will be an online code sprint.

The sprint will run from 14:00 UTC to 16:00 UTC on 19 May 2020.

If you're looking for a short task to work on, look for rows marked "easy" in this query of Datatracker tickets. Please consider the higher priority items first.

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

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

During the sprint, please update the two tables below; this helps both with coordination and with getting the code merged, released, and deployed :-)

Please fill in the following table when you've picked a task for the code sprint. It's quite all right to pick and complete multiple tasks :-)

Who	Short Description	Related ticket numbers
Tom Pusateri	Add Remote Instructions to JSON agenda	2955
Jim Fenton	At large IRSG members cannot ballot	2979

Who	Short Description	Related ticket numbers

When your code is ready for merge and release, please use one of the following phrases in your commit message:

If all related changes are contained in one commit: Commit ready for merge
If all your commits to your branch, up to the current, should be merged as one unit: Branch ready for merge

Committing code 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 EnhancementIdeas list. To add to the list, 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.

The Sprint will be run according to the IETFSprintHowto.