design goals?

On the eventual Wiki, I'd like to see a page with explicit goals 
about the *project*, not just the design details for Chandler.

For example, does OSAF see a role in experimenting with novel 
approaches?  Is OSAF likely to e.g. try a 3D interface just to see 
what it's like since nobody has ever done one before?  Is OSAF likely 
to experiment with using Bayesian or Group Method of Data Handling 
techniques to automatically classify spam?

Or does OSAF want to skip experimenting and get something useable out 
as quickly as possible?


For example2: what is OSAF's relationship to standards, particularly 
what happens when OSAF runs into a limitation of a standard (e.g. 
Sieve not having hooks for scoring spam)?  Will OSAF junk the 
standard?  Work with the standards group (probably W3C) to extend the 
standard, then use it?  Extend the standard unilaterally?  Extend 
unilaterally and then try to patch up the standard later?  What if 
there is no standard?  Does OSAF plan to create a freely-usable 
standard -- even if doing so means slipping the Chandler schedule?


(Note: I don't care what about the answers to these questions; I 
don't need to know the answer Right Now; I want to eventually hear 
that there *is* an answer publicly viewable.)
-- 
Kaitlin Duck Sherwood
Author of the _Overcome Email Overload_ series, http://www.EmailOverload.com
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Process" mailing list
http://lists.osafoundation.org/mailman/listinfo/process