Interesting, almost completely orthogonal to mine

Question

Now that we have a list of potential features, the next step is to prioritize
which features should be implemented in the 0.5 release and in what order. Each feature has a guestimated number of days associated with it. We have about 120 developer days before a release in mid-February. Your job is to pick out which features should be included in the next release (all of your features should only take 120 days to complete) and then, *very importantly*, to prioritize when those features should be implemented. Once we set a concrete release date in February, the release date will be firm, while the number of features we complete will not, so the priority of the features will determine which features will definitely get into the release and which may not.

As our esteemed leader, Jonathan Zittrain will be ultimately responsible for putting together the final list of priorities for the release, but the feedback we get from this discussion will play a very important role in his decision.

For the list of features, see:

http://h2odev.law.harvard.edu/viewcvs/*checkout*/h2o/docs/plan/feature-priorities.csv?rev=1.6

In order of priority From: Jesse Ross

2 Include user id in urls in assignment emails
10 Predefined attributes
15 Custom Attribute functionality
5 optional automatic expulsion on round skip
5 Invite unregistered user to join a project
10 fully featured project search page
5 bulk user load
10 tournament mode
15 polling
2 word count support on response page
3 help system infrastructure
5 help content
3 confirmation of email change
3 random routing with no repeats
5 value based routing
5 attribute based routing
2 bounce back routing
10 manual adjustment of response routing
3 project deletion
1 more basic faqs
1 free text search for users

Interesting, almost completely orthogonal to mine From: Wendy Seltzer

My priorities were based on classroom use, and the features that I had programmed (or failed to program) into past versions of the rotisserie. So to me, more flexibility in asking questions and timing rounds would be most important to making the rotisserie a solid piece of software -- and one on which I could base (part of) student grades. Then pieces like attributes and flexible routing are frills that can enhance that core.

I also didn't list a lot of features geared toward "community," since that's not the primary mode in which I've used the rotisserie.