[Design] [Sum] The State of Sharing

[Mimi Yin]

Notes from brain dump session with Morgen:

There are 3 categories of Sharing issues:

1. Items are popping-to-NOW that shouldn't be

+ Under-the-hood attributes are changed: email 'from' field and other  
mail headers, icalUID

+ Email updates are interfering with sharing edits and registering as  
conflicts, even when they're not actually conflicts - https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=11710

+ Server-side issues: Start-times were changing spontaneously - these  
are supposed to be fixed now.

+ Recurrence - related issues: Get the run down from Jeffrey
- I'm having trouble deleting recurring events, they keep coming back  
- https://bugzilla.osafoundation.org/show_bug.cgi?id=11749

+ Events are tickling to NOW the morning of the event instead of at  
the start-time - https://bugzilla.osafoundation.org/show_bug.cgi? 
id=11750

2. Keeping your desktop client and hub account in sync

+ Currently, we're able to automatically download your published  
collections
+ We still need to get syncing subscriptions working (uploading and  
downloading) - The Cosmo team has recently added a new API for this.
+ We also need a way to automatically publish all your collections so  
that people don't need to figure out how to add collections to their  
hub account mnually. Morgen thinks this would be relatively simple to  
implement.

I think we're losing users at this critical stage of the setup  
experience. So I imagine that this is one of the areas we'll tackle  
first.

Bugs:
+ Wizard for keeping Desktop + Hub in sync. - https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=11594
+ Keep subscriptions in sync between Cosmo and Desktop - https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=10983
+ Syncing published shares makes them all 'Not-Mine' - https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=11717
+ Reconcile subscriptions with published collections - https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=11732

3. Read-only security hole issues

https://bugzilla.osafoundation.org/show_bug.cgi?id=11013
See Morgen's write-up on the design list - http:// 
lists.osafoundation.org/pipermail/design/2007-December/008185.html

+ The server needs to isolate each item within each collection
+ As a result, the server stores 1 copy of the item per collection

+ Downside: Web UI needs to figure out how to deal with multiple  
versions of the same item living in the same account in different  
collections.
- What if 1 version was edited more recently than the other? Which  
version do  users see? Especially when they have overlayed calendars?
- What if the web UI user edits 1 version of the item, does the edit  
automatically propagate to the other version?

+ How do we reconcile conflicting permissions? I have 1 item in 2  
collections. I collection I subscribed to read-write, the other read- 
only. Which kind of access to I have to that item? This needs to be  
worked out on both web and desktop clients.
https://bugzilla.osafoundation.org/show_bug.cgi?id=11717

+ Currently, we're able to automatically download your published  
collections
+ We still need to get syncing subscriptions working (uploading and  
downloading) - The Cosmo team has recently added a new API for this.
+ We also need a way to automatically publish all your collections so  
that people don't need to figure out how to add collections to their  
hub account mnually. Morgen thinks this would be relatively simple to  
implement.

I think we're losing users at this critical stage of the setup  
experience. So I imagine that this is one of the areas we'll tackle  
first.

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