Brian K. Wrote:
"""Now that we have reached Preview, it is my opinion that the focus should
be squarely on improving and augmenting the user level feature set
based on adopter feedback.
"""
I agree with Brian that these two topics are _very important_ now that the
Preview milestone has been reached.
Improving the features and the users base are in a certain sense the two
sides of the same coin, since users must see a continuous and stable
improvement in order to adopt Chandler at this very early stage.
I understand that everyone here should "create his/her do-want list" at this
point.
Mine, would be:
1. Concentrate on:
- reliability (and ease of code maintenance)
- performance
2. put in place some new features such as
- Contacts
- Monthly View
- Printing/reporting
- Rich Text Editing
- Localization
- User Interface Cleanup (especially input)
- Better triage capabilities
- Some other Dashboard (perhaps)
I am very careful not to infer any schedule from this do-want list.
Mimi said: """I think we all want Chandler-the-code to be easy to maintain.
*And* we all want to have users for Chandler-the-product so that
Chandler-the-code will be worth maintaining.""".
I think, as a mere consequence of that, that we may also need to address
some "typical" use case in order to show the users "hey, Joe Average,
Chandler does this and that and does it 'very best way' " and give
developers some very good reason to buy-in about Chandler.
Sincerely,
Piero Giuseppe Goletto
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
