[Design] [Sum] April 10 - 16

Sheila Mooney sheila at osafoundation.org
Wed Apr 19 23:02:30 PDT 2006


Design:

Tim O'Callaghan posted his idea about using an IMAP server as a  
Chandler storage backend instead of WebDAV
http://lists.osafoundation.org/pipermail/design/2006-April/004511.html

Mitch posted on using RSS in Cosmo for event change notification.  
Basically Chandler users could subscribe to an RSS feed of recent  
event changes and new changes would show up as unread items. We could  
track some level of granularity like additions, modifications and  
deletions. Mimi also suggested the name of the editor as well. BCM  
thinks that much of what we have in place for Cosmo already will  
satisfy most of the requirements.
http://lists.osafoundation.org/pipermail/design/2006-April/004516.html

Philippe posted on the issues surrounding the ability to restore free- 
busy after a Chandler user has deleted their repository. Currently  
the free-busy share appears in the restore list but we don't really  
want this added to the sidebar, it should get hooked up under the  
covers. Philippe discovered a bug where an empty collection gets  
added to the sidebar when you try and restore this. Technically it's  
a share but it behaves a bit differently. The PPD team will tackle  
this and have a proposal in place for alpha 3.
http://lists.osafoundation.org/pipermail/design/2006-April/004534.html

Mimi posted a thread to the list, exploring the use cases for adding  
private annotations to read-only items. Overall, it seems like there  
were quite a few uses cases for this covering calendar events, email  
and tasks.
http://lists.osafoundation.org/pipermail/design/2006-April/004553.html

Mimi posted a summary of all the discussion to date on the sidebar  
icons and various visual treatments for the checkboxes etc.
http://lists.osafoundation.org/pipermail/design/2006-April/004559.html

Mimi wrote up a summary of the design discussions on the preview  
area. Currently the preview area is fixed in the calendar app area  
but changes as the user moves via the mini calendar in the other app  
areas. In response to some dogfood feedback we are looking at  
solutions to make this less confusing.
http://lists.osafoundation.org/pipermail/design/2006-April/004567.html

Dogfood:

Further discussion continued on the lozenge shape. Mimi posted some  
alternative designs for discussion. There was further discussion  
directed at whether we were trying to convey too much meta data in  
the lozenge. Priscilla and Mimi are going to iterate further on a  
proposal.
http://lists.osafoundation.org/pipermail/design/2006-April/004561.html

Scooby

None

Cosmo

Christopher Tengi submitted a post on the use of tickets, listing out  
some of the management issues you run into if you are keeping track  
of a bunch of different tickets. He suggested a notation field for  
each ticket so users can keep track of finer grain access rights. He  
also brought up some good points about future access control (we have  
already talked about some of this) and limiting the people who can  
use a ticket - so it doesn't fall into the wrong hands.
http://lists.osafoundation.org/pipermail/design/2006-April/004520.html

Other:

There was some discussion about the new Google calendar, features etc.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060419/09142a69/attachment.html


More information about the Design mailing list