Hey Mimi, I think your idea of a "top 10" is great - if nothing else it will promote debate/discussion about what should be on the top 10.
Now, are these top 10 for fixing in the Chandler 1.x product line, or items for Chandler 2.x? This is where i get confused, and need some clarity - how much more effort is going to be put into features additions for the 1.x line, vs moving all dev over to the 2.x line? I know that, if i had any extra time, i'd be investigating how to write plugin's for the 2.x stuff, as it seems that is where things are heading... But its still unclear to me what the priorities are for Chander. jos ps. sorry for the extremely slow response times - hard to get enough time to write something with more then 1 or 2 lines... Mimi Yin wrote: > Hi Jos, > > I started collecting a list of "Top Usability Issues" (aka "stuff we > want to get right in re-arch") here: > http://chandlerproject.org/Product/TopUsabilityIssues > > I haven't done a pruning job to make it comprehensible yet. Do you have > any ideas for how we can keep it simple, without losing valuable > suggestions? > > We could maintain a pretty tight Top 10 list and then throw everything > else into a "Nice-to-have" bucket, with the understanding that depending > on user responses, the Top 10 list will change over time. > > There is also the 1.0-Candidates lists, which is really a monster - but > it's pretty comprehensive as far as capturing the bugs people have run > into and feature requests that have been submitted. > > http://chandlerproject.org/Planning/DesktopWorkQueue > http://chandlerproject.org/Planning/WebWorkQueue > > Mimi > -- Jos Yule Digital Hyakugei _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
