Skip to content

Historic: Sprint: PhillySprint

Jump to bottom
Robert Sparks edited this page Apr 26, 2023 · 1 revision

Philadelphia IETF Code Sprint

We'll have a code sprint in Philadelphia, in connexsion with IETF 71, too. Here's Russ' announcement:

Subject: Philadelphia IETF Code Sprint
Date: Fri, 11 Jan 2008 10:23:51 -0500
From: IETF Chair <[email protected]>
Reply-To: [email protected]
To: IETF Announcement list <[email protected]>

Philadelphia IETF Code Sprint

When:  Saturday, 8 March 2008, begining at 9:30 AM

Where: IETF Hotel in Philadelphia 

What:  A bunch of hackers get together to work on code for the IETF web
       site.  Some people may be porting of existing functionality to
       the new framework; some people may be adding exciting new
       functionality.  All code will become part of the open source
       IETF tools.

Who:   Hopefully you can help

Henrik Levkowetz and Bill Fenner were very happy with the results on the
Vancouver IETF Code Sprint.  So, we are doing another code sprint in
Philadelphia.  Again, Henrik, Bill, and Cullen Jennings will be
coordinating the event.  You will hear more from them shortly, beginning
with brainstorming about which things to work on during this event.

Please support the tools development effort,
   Russ

You can sign up on the PhillySprintSignUp page.

Sprint Project Proposals

  • Refined IETF Search: Replace the search done from the search form at the top of http://www.ietf.org with a more refined version: RefinedIetfSearch

  • Event trail: Catch all commits to the database, and emit them in a well-defined (XML? JSON? AVPs?) format through a pub-sub interface such as for instance XMPP, for use by tool authors in general.

  • Continue the website re-design started in Vancouver. (I guess that means I'll do more XHTML/CSS -- Lars.)

  • A common, simplified and capability-extended document search page. This could mean such things as using one search entry field only, and doing the right thing based on the content. Serve links to the document itself first and documents which refer to it if the search term contains !draft-xxxx or rfcNNNN; for free-text search try with authors, titles, abstract, and eventually fall back to a full document content search. This is similar to RefinedIetfSearch, but implemented completely in Django on top of the database, except maybe for the full-text fallback which could be handed out to google.

  • Fixing the set of WG mailing list URLs in the Google co-op search. This has been broken for a while, maybe because of the transition. -- Lars and Jari

  • Additional work on IESG statistics -- Jari

  • Refactoring some of the code in getauthors (which is a horrible hack) and testing to make sure it still works right. -- Jari (Done and tested)

For more ideas, see VancouverSprintBrainstorm and VancouverSprint.

Clone this wiki locally