Well maybe it's really a process or staging thing? As in a 2 stage process.

I guess which is why I tried to rephrase the tenets as end-user tasks as opposed to feature descriptions? What do we want to be able to do with 0.7?

And then we can say, okay well, yes end-user goal X would be great, but that would take us 5 years, but since it's #1 on the list, we better get started now.

OR end-user goal X is at the bottom of the list, but it's really easy to do, so maybe we do it anyway as an easy win.

So to reiterate the list and add to it:

- Look at other people's free-busy information.
- Customize the calendar views.
- Begin to experiment with and iterate on the dashboard for task management.
- Customize the detail view with my own attributes.
- Customize the dashboard with my own set of attributes for tracking tasks, save it as a skin and offer it up to the community to try out.
- Make my data portable (as in on my person, not in a computer)
- Make my data secure
- Be able to undo typing and filing mistakes

This isn't a complete list, so please feel free to fill this out (given the list of tenets Sheila has already outlined).

Mimi


On Nov 30, 2005, at 4:32 PM, Ted Leung wrote:

On Nov 30, 2005, at 3:10 PM, Lisa Dusseault wrote:

That said, generally one tries to decide the desirability of a feature independently of its cost, to a certain extent.  Are simple invitations more important than free-busy if you assume that the cost is the same?

Let's turn that around.  What if free-busy was going to take 5 people two years?   The cost does matter.   The decision isn't just whether we do feature X or not.  It's also what we choose not to do by doing feature X.

Ted

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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

Reply via email to