http://spreadsheets.google.com/ccc?key=txJx3_oLeRwrk8SwnoWc88w
Column X On Oct 13, 6:38 am, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hey folks -- > > Like last time 'round, if you'd like to express an opinion about > features for Django 1.2, go and vote: > > http://spreadsheets.google.com/ccc?key=0AtIlKMKDxMBpdGVPVXlTODVLeTBpN... > > I've reorganized the 1.2 feature list > (http://code.djangoproject.com/wiki/Version1.2Features) into a > spreadsheet, and added short codes so we can have a shortcut when we > talk about things. I've put my votes, and comments, into that sheet, > and I'd like to invite you to share yours. > > I'd like to ask committers and anyone else to send me their own rankings. The > easiest way is just to copy the spreadsheet and send it to me when you're > done, but if you're anti-google just email me something I can read with codes, > scores, and any notes. I'll add other folks' rankings to the master page as I > get 'em. > > Committers: please get me your thoughts ASAP. I'd like to have a draft > feature list for 1.2 out by October 20th. > > Please use the standard +1/+0/-0/-1 ranking. In this case the scores > have some additional meaning: > > +1 -- "Yes!" > For "must-have" features. > > A +1 from a committer means that s/he will champion the feature, guide > the implementor (or implement it personally), review the patch, and commit > the feature personally. > > A +1 from a non-committer is an offer to personally work on the feature, > or to help the person working on it by reviewing the patch, testing, etc. > > +0 -- "OK" > > For features that are a "good idea". > > A +0 from a committer means that s/he will not stand in the way of the > feature, but also won't personally invest much effort in it. > > -0 -- "Meh" > > For features that don't seem all that hot. > > A -0 from a committer indicates disapproval, but that s/he won't argue > against the feature if another committer approves it. > > -1 -- "No!" > A strong vote against. > > A -1 from a committer essentially is a veto. No features will be checked > in with a -1 vote from a committer; only if s/he gets talked up to a -0 > or better will the feature happen. > > Using these votes, we'll make lists of "high", "medium", and > "low" priority, and "rejected" features. These lists will be based on the > following criteria, but remember there's a holistic aspect to this process. > We'll use the votes to draft a feature list, but we'll also open up the list > for discussion and make changes accordingly. > > Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
