[Sum] The State of Sharing
Mimi Yin <[email protected]> Tue, 15 Jan 2008 15:44:19 -0800
| Newsgroups | gmane.org.osaf.design |
|---|---|
| Message-ID | <[email protected]> |
--===============2022338302== Content-Type: multipart/alternative; boundary=Apple-Mail-5-942644170 --Apple-Mail-5-942644170 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed 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. --Apple-Mail-5-942644170 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; ">Notes from brain dump session = with Morgen: <div><br class=3D"webkit-block-placeholder"></div><div><div>There are 3 = categories of Sharing issues:</div> <div><br></div> <div><b>1. Items are = popping-to-NOW that shouldn't be</b></div> <div><br = class=3D"webkit-block-placeholder"></div><div>+ Under-the-hood = attributes are changed: email 'from' field and other mail headers, = icalUID</div> <div><br></div> <div>+ Email updates are interfering with = sharing edits and registering as conflicts, even when they're not = actually conflicts - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11710">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11710</a></div> = <div><br></div> <div>+ Server-side issues: Start-times were changing = spontaneously - these are supposed to be fixed now.</div> = <div><br></div> <div>+ Recurrence - related issues: Get the run down = from Jeffrey</div> <div>- I'm having trouble deleting recurring events, = they keep coming back - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11749">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11749</a></div> = <div><br></div> <div>+ Events are tickling to NOW the morning of the = event instead of at the start-time - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11750">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11750</a></div> = <div><br></div> <div><b>2. Keeping your desktop client and hub account = in sync</b></div> <div><br></div> <div>+ Currently, we're able to = automatically download your published collections</div> <div>+ We still = need to get syncing subscriptions working (uploading and downloading) - = The Cosmo team has recently added a new API for this.</div> <div>+ 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.</div> <div><br></div> <div>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.</div> <div><br></div> <div>Bugs:</div> = <div>+ Wizard for keeping Desktop + Hub in sync. - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11594">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11594</a></div> <div>+ = Keep subscriptions in sync between Cosmo and Desktop - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D10983">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D10983</a></div> <div>+ = Syncing published shares makes them all 'Not-Mine' - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11717">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11717</a></div> <div>+ = Reconcile subscriptions with published collections - <a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11732">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11732</a></div> = <div><br></div> <div><b>3. Read-only security hole issues</b></div> = <div><br class=3D"webkit-block-placeholder"></div><div><a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11013">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11013</a></div> <div>See = Morgen's write-up on the design list - <a = href=3D"http://lists.osafoundation.org/pipermail/design/2007-December/0081= 85.html">http://lists.osafoundation.org/pipermail/design/2007-December/008= 185.html</a></div> <div><br></div> <div>+ The server needs to isolate = each item within each collection</div> <div>+ As a result, the server = stores 1 copy of the item per collection</div> <div><br></div> <div>+ = 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.</div> <div>- What if 1 version was edited more recently = than the other? Which version do=A0 users see? Especially when they have = overlayed calendars?</div> <div>- What if the web UI user edits 1 = version of the item, does the edit automatically propagate to the other = version?</div> <div><br></div> <div>+ 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.</div> <div><a = href=3D"https://bugzilla.osafoundation.org/show_bug.cgi?id=3D11717">https:= //bugzilla.osafoundation.org/show_bug.cgi?id=3D11717</a></div> = <div><br></div> <div>+ Currently, we're able to automatically download = your published collections</div> <div>+ We still need to get syncing = subscriptions working (uploading and downloading) - The Cosmo team has = recently added a new API for this.</div> <div>+ 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.</div> = <div><br></div> <div>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.</div> <div><br></div></div></body></html>= --Apple-Mail-5-942644170-- --===============2022338302== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design --===============2022338302==--