Thanks for starting this conversation on the list Sheila.
My take on the goal or 'point' of 1.0 is to address 2 blockers to
adoption:
1. Remove the 'Oh, this is just a Preview release? I don't want to
beta-test half-finished software' barrier for users who hear about us
and are interest, but reluctant to sign-up for troubleshooting. How
would we know that we had attained this goal? We're comfortable
removing the Tools menu and make it a plug-in instead.
2. Remove any remaining barriers that would prevent OSAF staff and
current Chandler users from recommending Chandler to non-PIM
enthusiast friends, co-workers and acquaintances. People who need
better productivity tools, but don't necessarily go looking for them
on their own.
What does this mean in terms of features and functionality?
1. We don't have to fix all the bugs, just the bugs that people run
into early and often.
2. Any 'functionality' that we don't already have should probably
just be cut. Realistically, we're not going to be able to 'improve /
expand' how useful Chandler can be to people in the next 2 months, at
least not without perhaps introducing other problems. Instead, let's
focus on polishing what we already support.
I have a next action to review the bug lists for both projects and
will report back with more specific ideas :)
Mimi
On Dec 3, 2007, at 3:29 PM, Sheila Mooney wrote:
+ What are the tenets for 1.0?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
