Aparna and Andre have been investigating a bug where Andre gained
read-write access to a Chandler item he received via email by adding
it to a second shared collection he has read-write access to.
As a result, Aparna and I were seeing Andre's non-emailed edits on
the item and vice versa, even though we never set up a formal sharing
relationship by exchanging read-write ticket URLs for a commonly
shared collection.
Randy, Morgen, could you give us on the design list an update on
where you are wrt this issue (or point us to the latest dev-list
write-up)?
===
Hi Aparna,
We *want* users to be able to edit and update email they send/
receive. However, you, Andre and I have *not* formally established
any kind of sharing relationship by exchanging read-write tickets for
a shared collection, so we shouldn't see each other day-to-day edits,
only edits that are sent via email updates.
Currently, the server stores only 1 instance of any item, so even
though the 3 of us aren't sharing a collection, we end up sharing the
item because the server figures out at we've each uploaded the same
item to our respective collections on the server and any edits we
each make to that item are made to the same item on the server.
Anyhow, my understanding is that we will fix this issue for 1.0...but
I'm not clear on the details and hoping Randy and Morgen can fill us in.
On Dec 17, 2007, at 10:43 AM, Aparna Kadakia wrote:
My thoughts are that this makes sense actually and is not a bug. It
seems to me to be a reflection of the inability to mark an item as
read-only before forwarding it to another Chandler user. What are
you guys thinking?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
