-
Notifications
You must be signed in to change notification settings - Fork 398
Historic: Sprint: IETF110Sprint
#!html
<p style="background-color:#c0c000;">This page is for a sprint that has already finished.<p>
The sprint that follows this is at IETF110.1Sprint.
This will be a virtual codesprint coordinated over Webex. It will be held on Tue Feb 23 from 1600-2000 UTC.
See this page at timeanddate.com for a translation of that into a few timezones.
Note that this is not the usual Saturday before the IETF timeslot
The expectation is that any given attendee would only be around for a couple of hours. Dropping in and out is not a problem.
Here are the webex coordinates.
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 2.2? Here is an excellent tutorial if not.
-
A laptop 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 IETF110SprintSignUp page.
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://trac.ietf.org/trac/ietfdb/newticket
We have the mailing list "codesprints@ietf.org" 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:codesprint@jabber.ietf.org?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 ** |
|---|---|---|
| Ryan | Merge Person special handling for ReviewerSettings | #3183 |
| Jim | "No documents match your query." isn't really accurate | #3148 |
| 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 here for those not marked sprint.
The Sprint will be run according to the IETFSprintHowto.