• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!


Worldwide Sprint 2

Page history last edited by Ben Atkin 15 years ago

The jQuery UI team will be holding our second worldwide Sprint, Friday and Saturday, April 17 and 18, 2008. The goal is to complete the bug fixes for 1.7.2 and start ramping up for 1.8 and beyond. Everyone is invited (and encouraged) to participate.



Date & Location: Friday, April 17 and Saturday 18, 2009

As this is a worldwide event, there is no physical location for attendance; just an IRC channel and a wiki page.

The working code can be downloaded at:

svn co http://jquery-ui.googlecode.com/svn/trunk/



What's the Big Idea?

We want to have all the focus and productivity possible directed towards the next jQuery UI release, for two fun-filled days. With your help, we'll finish all critical issues for 1.7.2. Since we're also ramping up on planning for 1.8 and beyond, we're looking for help collecting specifications and designs for our upcoming plugin priorities. We're anxious to have help from new and old team members, and anyone else that has an interest in making jQuery UI great.



How To Contribute

If you don't already have one, you'll need a wiki account on wiki.jqueryui.com and a trac account on dev.jqueryui.com. If you don't have commit/svn access, use trac tickets to attach patches.




To coordinate efficiently, we will be around in IRC for both days. Most of the team members will also use GTalk and twitter (#jqueryui-sprint) for direct communication, so feel free to ping the following people directly:

  • Scott González (scott.gonzalez@gmail.com)
  • Todd Parker (todd@filamentgroup.com)
  • Richard D. Worth (rdworth@gmail.com)

See the participants list below for team members.


Additionally, we will have three meetings - everyone should attend one of the first two if possible, because this is where we'll speak about the goals for the day.


Kick-off Meeting: Friday, April 17th, 9:00 am EDT / 14:00 GMT+1

  • Welcome/ introductions
  • Scope, task prioritization
  • Q&A


Status Meeting: Saturday April 18th, 9:00 am EDT / 14:00 GMT+1

  • Welcome/ introductions
  • Status report from previous day's work
  • Plan our attack for the day: prioritize remaining tasks


Wrap-Up Meeting: April 18th, 6:00 pm EDT / 23:00 GMT+1

  • Final status report
  • Open issues, next steps




  • You'll need a trac account: http://dev.jqueryui.com. This is for filing tickets and patches
  • You'll need a wiki account: http://wiki.jqueryui.com. This is for specifications, and also the sprint page(s), which we'll use to keep status updates, esp. for folks who join for an hour here or there
  • We recommend the use of a paste site, such as http://paste.pocoo.org/ or http://jsbin.com/. Both use jQuery, are very simple and have great syntax-highlighting. This can be good for those times when you want to share something, but it's not something so big/ready you'd attach to a ticket.


Team Organization

We'll break up into teams and focus on a number of areas:

  • We created 4 sprint teams - design, dev, test, docs
  • Lots of people can be on multiple teams, that's cool
  • Please feel free to join any of the four groups - you can also switch groups later on.
  • We want this to be fun and efficient. We're just breaking things up to keep a bit better organized



  • Design Team (facilitator: Todd Parker)
    • Responsible for planning and design work for new high and medium priority plugins on the wiki: https://wiki.jqueryui.com/Worldwide-Sprint-2-Design
  • Dev Team (facilitator: Scott González)
    • Responsible for updating, writing, testing, and ensuring complete specifications for each 1.7 plugin on http://wiki.jqueryui.com/
    • Responsible for fixing critical issues for 1.7.2 and 1.8 - they will mostly use the bug tracker http://dev.jqueryui.com/
    • Also, the dev group will have to fix any further upcoming issues coming from the testing group
  • Test Team (facilitator: Richard D. Worth)
    • Responsible for creating visual and unit tests for each of the plugins and of course for testing the components themselves and reporting possible issues to the bugtracker
    • The goal is to have good unit test coverage (50%?) of all plugins. This is critical so that the dev team can make changes, especially API consistency type changes, across modules, as well as testing on all supported browsers, all the while minimizing and detecting regressions.
  • Docs Team (facilitator: Micheil Smith)


Team Subpages



Add your name below if you plan on participating, along with contact info, and what you want to do (design, development, testing, documentation, bug fixes, anything)



Comments (1)

Dan Wellman said

at 1:31 pm on Apr 17, 2009

Dan Wellman (email: danwellman@hotmail.com twitter:@danwellman gtalk: danwellman) - docs, dev

You don't have permission to comment on this page.