My pet peeves

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

My pet peeves From: Wendy Seltzer

,Rotisserie,5,"Add absolute date picker to date fields and to round start/end (so that the user can choose either round durations or specific end dates)"
,UI,1,"Include 'Current H2O Time' somewhere in header."
,Rotisserie,10,"Management of individual rounds - allow all round settings to be customized for each individual round."
,Rotisserie,3,"Additional questions in rotisserie rounds -- allow project leader to add a question to each round"
,Directory,3,"Show all visible posts written by the user on the user profile screen page (and get rid of the contextually driven stuff that's confusng and poorly done). Group posts by project / rotisserie"
,Rotisserie,2,"Include user id in urls in assignment emails -- prevents the user from clicking on the url and not getting the assignment because he is logged in as a different user"
,Directory,1,"Administrator su page -- let a site admin login as any user"
,Rotisserie,15,"Polling, incl. poll setup in rotisserie management screens, poll response on rotisserie response screen, and poll display on rotisserie and thread view pages"
9,"Home Page",1,"Always present ""You have # responses" message in top right of page
,Directory,1,"tweak login page - add check for cookie support in browser and add changing element to 'mismatched username/password' error message"
,Rotisserie,5,"Creation of rotisserie from templates - copy from another rotisserie to start the creation of a new one"
,Rotisserie,5,"Value based routing. This is base support for attribute, poll, and section based routing. Route based on whether a given value is similar or different between users (same user attribute values, difference poll answers, etc.)"
,Rotisserie,2,"Word count support on response page - provide a word count button to help participants manage the length of their posts."
,Directory,5,"More project privacy options: Show questions, but not answers; Show questions and answers, but not participant profiles; show profiles, but not emails"
,App,1,"Change db layer to sort by name if present"
,Directory,1,"Display application message for registrants (currently it's accepted but not displayed anywhere)"
,Rotisserie,10,"Simple post comment system - allow adhoc posting within the current round"
,Rotisserie,3,"Improve dates in alerts. Include absolute due date in assignments (7/12/2002 5:13 intead of just 24 hours). Round to nearest hour when within a couple of minutes (to avoid the 23 hours 59 minutes thing). Convert to whole days when appropriate (1 day 6 hours instead of 30 hours)."
,UI,3,"Help system infrastructure - support for inluding '?' links in the module headers, which link to popup help content"
,Content,5,"Help Content - first stab at help, including at least help on all the forms"
,Rotisserie,3,"Allow project leaders to see current round posts in view rotisserie page (not sure if we really want to do this -- impinges on the freedom of the user to take the entire round duration to craft an answer)"
,Directory,5,"Invite unregistered user to join a project. This is a slightly scaled down version of the 'include an email in the rotisserie recipients list and have that email be automagically invited.' I'm imagining just a form available to project leaders from the project screen that would allow the leader to enter an email and have that link lead to a page that would send the user to a registration page that would automagically sign him up for a project (and throw him to the project page, perhaps) once registered. Requires join project link for guests, above."
,Directory,5,"Bulk project acceptance page -- a single page with all applicants to a project with a 'reject' and an 'accept' column that lets a leader accept/reject users en masse."
,Directory,4,"Project announcements. Includes a form for project leaders to enter them and display of them on the home page and the project profile page."
,Directory,10,"Fully featured project search page - search on any project attribute, including full text of rotisseries"
,Rotisserie,3,"Show real names of participants when permitted on view rotisserie and view thread page"
,Directory,5,"Report to project leader when email to participant is bounced"