[Design] [Sum] Jul 10-16

[Sheila Mooney]

Ok, last week's design summary is a bit of a doozy. I will be  
summarizing the following threads separately since they are lengthy  
and will benefit from having their own thread.
+ Email - bridging the gap
+ How basic can we stand for email
+ Minimum email feature set we can put up with for early Chandler  
release
+ Anonymous access to read-write calendars
+ Alpha4 sharing discussions

New Design Discussions:

Sheila posted a thread on giving users anonymous read-write access to  
calendars in Scooby, summarizing an issue that came out of a design  
session. The problem centers around wanting to give casual  
collaborators the ability to view and edit calendars in Scooby  
without forcing them to sign up for an account. There were a number  
of concerns about security and the expectations for how web apps work  
in general. This discussion resulted in many lengthy replies and will  
be summarized in a separate thread.
http://lists.osafoundation.org/pipermail/design/2006-July/004958.html

Mimi sent out a proposal for the web client mail to link workflow. In  
brief, if a scooby user adds an event to a calendar, they will be  
able to click on an "email this" link to send a notification of their  
change. In this case, the user's default mail client is launched and  
a new message is automatically created pre-populating the subject  
line and adding the event details to the body of the email. A nice to  
have feature would be some tag in the notification so these emails  
could be received in the Chandler desktop.
http://lists.osafoundation.org/pipermail/design/2006-July/004966.html

Based on something that came up in the "anonymous access" responses,  
Mimi started a new thread about reconciling sharing privileges with  
the Edit/Update workflow. Mimi pointed out an issue that a user may  
have read-only access to a collection but also receive one of those  
items explicitly because the sharer stamps it as a communication and  
sends it to the sharee. In this case, even if the user only had read- 
only privileges to that collection, we have to give them the ability  
to edit this item they receive explicitly in order to support our  
collaboration workflows. Mimi asked if we could grant access  
privileges on individual items in this case.
http://lists.osafoundation.org/pipermail/design/2006-July/004974.html

+ Morgen posted some questions to the Scooby team about the Alpha4  
sharing spec.
	+ How is Scooby able to see what collections user's have subscribed  
to in Chandler. These might be shares on our hosted service or some  
other remote server ie: .Mac?
	+ Do the calendars have to be uploaded to Cosmo and how are we going  
to be able to keep these in sync?
Morgen also suggested we have an "export personal settings" feature  
where you can export share info and account settings to the local  
disk. This way when you wipe out your repository you can restore  
these settings easily.
+ Mimi replied that ultimately whatever you see in Chandler you  
should be able to see in Scooby. She thought that for Beta it would  
be reasonable to narrow the focus to just what's on the Cosmo server.
+ Mikeal replied that if Chandler users are subscribed to remote  
calendars from multiple CALDAV servers it would be nice if Cosmo  
could just store subscription info and remote events wouldn't have to  
be synched through Chandler to Scooby. This would make it easier to  
support other calendar subscription modules in the future.
+ BCM agreed with Mikeal's suggestions
+ Sheila responded to Morgen's email spawning 2 threads since there  
are 2 separate issues.
	+ What should we restore and how when we delete the Chandler  
repository.
	+ How does Scooby know about what Chandler is subscribed to.
http://lists.osafoundation.org/pipermail/design/2006-July/004981.html

Katie forwarded a discussion in bugzilla to the list. Heikki created  
an event clicked on the collection in the sidebar and then hit edit- 
 >delete. The event was deleted and he expected the collection to be  
deleted. Is this a bug? The issue is whether or not a single click in  
the sidebar moves the focus.
+ Grant questioned how collections would be deleted if this isn't a bug.
+ Jeffrey replied that his preference would be to not have the  
sidebar get focus and have a separate menu item for deleting the  
collection.
+ John replied that clicking once in the sidebar doesn't move the  
focus from the calendar - visually supported by the color of the focus
+ Heikki replied with a whole series of questions highlighting all  
the various inconsistencies in the ui relating to focus in the sidebar.
+ Mimi responded again that our motivation for now having focus in  
the sidebar is because there are only select use cases where you want  
to have the focus there.
+ I am going to ask Mimi to summarize this thread with the proposal  
and a list of all the inconsistencies (Heikki pointed out) that we  
should be filing as bugs.
http://lists.osafoundation.org/pipermail/design/2006-July/004988.html

Sheila posted a new thread about exploring ways to bridge the gap  
between Chandler and other email clients. We want some feedback on  
the technical feasibility for a range of alternatives that allow  
Chandler to coexist with other clients.
+ This thread will be summarized in detail in a separate email.
http://lists.osafoundation.org/pipermail/design/2006-July/005020.html

Katie started a new thread on "how basic can we stand for email". She  
threw out the question of what are the smallest subset of features  
that people absolutely need in order to use Chandler given all the  
other benefits.
+ As with some of the other lengthy threads, I would like to  
summarize this one separately.
http://lists.osafoundation.org/pipermail/design/2006-July/005028.html

Ernesto posted on "Graphically editing contact's multi-value fields".  
Ernesto is working on the Address Book project and had some questions  
specifically about a requirement - allow gui-editable multi-value  
fields. He also mocked up some visuals.
+ Mimi replied with a proposals/design for the contacts management  
scenarios we should try and support.
http://lists.osafoundation.org/pipermail/design/2006-July/005029.html

Mitch has the Alpha3 RC up and running and sent an email asking if  
it's possible to see the date and time for last background sync.
+ Morgen replied that the info is available and the design team needs  
to figure out the proper ui for this.
+ In the interim there is a rudimentary test->sharing->add sharing  
activity log to the sidebar menu item that you can view in week mode  
to see when a sync happened.
http://lists.osafoundation.org/pipermail/design/2006-July/005039.html

Katie sent a new thread titled "What is the minimum feature set we  
can put up with in an early release of Chandler?" to keep the  
"bridging the gap" discussion on track.
+ This will be summarized separately
http://lists.osafoundation.org/pipermail/design/2006-July/005046.html

Continued Threads:

The thread continued around how events are auto-triaged in the  
dashboard. Mimi further summarized what appears in the date column
+ If the item is not and event and has no tickler we display the most  
recent date (create, modified, updated etc)
+ If the item is a non-event and has a tickler date, it goes into the  
NOW section when the tickler goes off and displays the tickler date  
in the date column.
+ For events with custom tickler dates you always display the next  
important date. This is either the event date or the tickler date  
depending on which ones comes first and whether it's past or not.
+ Ted replied with a use case for when a custom tickler would fire  
after the event date - reminder after a meeting to post the notes.
http://lists.osafoundation.org/pipermail/design/2006-July/004952.html

Discussion continued on the "adjustable sidebar" thread, namely if  
having tooltips is useful and how hierarchies fit into the sidebar.
http://lists.osafoundation.org/pipermail/design/2006-July/004955.html

Sheila replied to the "manage share dialog" discussion. The debate is  
really about whether or not it's useful to have the sharing account  
pulldown because you can't actually do anything with that field. It  
also could be labeled more appropriately. Sheila responded that for  
people how share collections to multiple servers, this is useful  
information to have displayed. Mimi replied that if we had the  
ability to use this pulldown to re-publish a share to a different  
server and change the label, it would be worth keeping it in this  
dialog.
http://lists.osafoundation.org/pipermail/design/2006-July/004965.html

Jeffrey replied to the "multiple windows support" thread. He pointed  
out that experimental multiple windows might be easy but a polished  
version per PPD requirements might be more difficult. He is reluctant  
to spend a lot of time on this unless PPD feels it's critical for the  
roadmap.
+ Mimi pointed out that having multiple windows really supports  
composing and editing functions which are not the primary workflows  
we are supporting for Beta.
http://lists.osafoundation.org/pipermail/design/2006-July/004984.html

Jeffrey replied to an old thread about dashboard overlays. You will  
no longer overlay out of the box collections with the checkbox.  
Jeffrey wanted to clarify the behavior when you have checked the [x]  
Home collection then click on the Dashboard. Mimi replied that the  
[x] would grey out but still appear checked.
http://lists.osafoundation.org/pipermail/design/2006-July/004986.html

Jeffrey responded to an old thread on Delete key behavior. He  
proposed...
	+ Delete key for remove
	+ Cmd-D for move to trash
http://lists.osafoundation.org/pipermail/design/2006-July/004998.html

Other Stuff:

Priscilla sent out her Chandler dogfooding notes for June.
http://lists.osafoundation.org/pipermail/design/2006-July/004950.html

Sheila sent out the PPD weekly status update.
http://lists.osafoundation.org/pipermail/design/2006-July/004959.html

Sheila sent a new iteration of the dashboard spec with some more  
detailed mockups.
http://lists.osafoundation.org/pipermail/design/2006-July/004983.html

Mimi sent out yet another revision to the dashboard spec clarifying  
the behavior of the date column.
http://lists.osafoundation.org/pipermail/design/2006-July/005014.html

Jim Sowers send a thread proposing we try and integrate Chandler with  
evite - parse evites and display details in Chandler.
http://lists.osafoundation.org/pipermail/design/2006-July/005060.html

List posted the call for participation in CEAS 2006 - Third  
conference on email and anti-spam
http://lists.osafoundation.org/pipermail/design/2006-July/005032.html

Ted sent a link for 10 mac tools for GTD.
http://lists.osafoundation.org/pipermail/design/2006-July/005036.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060721/c270fc79/attachment.html