[Design] 0.7 tenets - revisited

[Sheila Mooney]

All,

Thanks to everyone that has been contributing to the discussions on  
the design list over the past week, I know there have been quite a  
few mails to keep up with. Based on the discussions on the list and  
within the design team, we have revised the list of tenets and wanted  
to send out an updated proposal. At a high-level, not that much has  
changed, really. The tenets in the initial list were very broad and  
our plan was to frame them more clearly and in terms of specific end- 
user goals.

The modified proposal....

* Plausible Scheduling
    - some lightweight free-busy and invitation solution to support  
experimental scheduling workflows (Mimi just sent out a more detailed  
email on this)
    - this accomplishes a couple of goals - some work on email and  
incremental progress on furthering our calendar
* Some tenet around plausible dashboard and/or task management
    - we don't have enough clarity for a specific tenet proposal  
right now
    - this tenets has 2 parts - the basic table work and fixing a  
bunch of the current stamping and table bugs (included improved  
markup bar).
    - the second piece (dashboard/tasks features) will be nailed down  
in the next 2-3 weeks
* Support people outside OSAF "beta testing" the release - support  
the current "dogfooders" and address some issues to make what's in  
0.6 work better
    - release packaging
    - schema evolution
    - bug fixing - calendar, non-calendar, sharing
    - performance
    - Cosmo bug fixing, stability and scalability
* Dev Platform
    - similarly to the dashboard tenet we haven't nailed this down  
specifically
    - we have some ideas around api cleanup but need to frame this  
better

A couple of additional notes....

There seems to be quite a bit of agreement in favor of moving towards  
short releases and the planning team has discussed various scenarios  
that would accomplish this. Overall, we felt it would not be  
productive to split this along tenet lines (ie: "support people  
outside osaf" first then the rest of the work) since the reality of  
resourcing and dev dependencies may mean we have pieces of all the  
tenets completed for let's say release A. Our plan is to start most  
of the work (roughly) at the same time and look for ways to stage  
this into 2 releases that are coherent. We will be thinking about  
this in more detail as the specs are written and we work with  
developers to define specific tasks. For this reason, it's tough at  
this point to articulate a specific "vision" for each of these  
releases. Once we start digging into the details, we feel this will  
start to emerge.

We have also heard from many individuals the PDA sync is pretty high  
on their list of priorities. Lisa has sent out an email to discuss a  
strategy in more detail which is why I have omitted this from any of  
the 0.7 goals listed here.

Comments/feedback welcome.

Sheila


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20051207/d73e7c0c/attachment.htm