I'm concerned about feature creep. Is offline mode now growing into
feature creep?
We have more features we'd like to do than we have time for in preview.
It is *very* important that we say no to some of these features. It is
going to be painful to say no, but these features add up and if we are
not focused we're going to miss our goal.
We need to focus on:
- Performance
- Finishing dashboard features
(including some email that supports these features)
- Sharing format/EIM (performance, support of cosmo integration, etc.)
Being able to test without network operations (Bug 6553) was important
and I'm glad Brian committed the changes to suppoort that. It would be a
mistake to have that grow into a feature we don't have time to really
design and support.
I just want to be clear that we are not signing up for adding "go
offline" to the high priority list for chandler and all of the testing
and support that might entail. We can leave it in the test menu, but
thats it.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
