[Chandler-dev] 1.0 Conflict Resolution Review for Re-arch

[Mimi Yin]

Hi,

In yesterday's check-in, pje mentioned that he was working on  
conflict resolution in the re-architecture. I thought it would be  
good to do a review of how conflict resolution has worked thus far on  
Chandler Desktop 1.0

To start, I'm happy to report that we haven't really had complaints  
about people losing data due to conflicts. (Yay). So original mission  
accomplished!

Going forward, here are some general areas where users have reported  
running into problems:

1. Decrease the number of "false positive" conflicts caused by:
- Auto-triage to NOW
- Chandler not differentiating between sharing with yourself and  
sharing with others
- Email addressing field related conflicts

11414 Conflict on events auto-triaged when they have been moved to  
Later on the server
11615 Changes in addressing fields causing spurious conflicts on  
recurring events
11657 False-positive conflicts around email addresses
11989 Spurious conflict when changing To: field

2. More granularity about what happened
- When an item is removed / deleted, can we tell which collection it  
was removed / deleted from?
- 11662 Confusing pending change 'remove' message when item is in  
multiple collections

3. Review how conflicting changes to recurring events are handled.
- 11749 Recurring series I deleted in full or in part keeps coming back

I understand this is all a bit vague right now. I am going to be  
talking with Jeffrey more about this issue since we are working in- 
person today :)

Mimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20080916/ed9e7311/attachment.htm