-
Notifications
You must be signed in to change notification settings - Fork 396
Historic: Sprint: IETF73Sprint
We'll have a code sprint in Minneapolis the Saturday before IETF 73
You can sign up on the IETF73SprintSignUp page.
Schedule and location information will appear here soon.
-
Integrate Bill Fenner's django-based password self-service system, test it, and stage it for deployment at some point after the meeting.
-
Replace the perl/mysql using scripts run by cron with django based equivalents. Good places to start looking if you want to get familiar with the target early is source:branch/sprint-ietf-73/legacy/scripts/update-web-pages and source:branch/sprint-ietf-73/legacy/scripts/update-web-pages-charters. Add documentation of the scripts first to IETF73SprintLegacyScriptsDocumentation.
-
Build/refine a list of the applications we are running (and what files support those apps), and clean away any scripts that are already converted (those that should be unreachable given the current http configs) to an attic.
-
A working knowledge of python and/or web design
-
Learn the basic concepts of Django 0.96, e.g., work through the excellent tutorial. (Yes, Django 1.0 is out, and we should migrate soon, but it won't be completely trivial - we can discuss the logistics involved during this sprint).
-
Bring a laptop with python (2.4 or 2.5), django 0.96, subversion and 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.
Each sprint participant gets his own branch to work in. The branches are noted on the IETF73SprintSignUp page. You'll do something like this to check it out:
svn co http://svn.tools.ietf.org/svn/tools/ietfdb/sprint/73/yourname