http://wiki.osafoundation.org/Journal/NoDataLossProposal
PJE, Morgen, Grant and I met yesterday with Philippe, Jeffrey, Brian Kirsch, Katie and Sheila to continue working through the intricacies of managing sharing and edit/update conflicts.
The original proposal discussed during the last on-site can be found here: http://wiki.osafoundation.org/Journal/ConflictResolution
Since then, we have drastically simplified the design and attempted to reframe the entire proposal as a 'No data loss' proposal, rather than a 'Conflict Resolution UI'. The reasons are many and varied and there are others better equipped to explain them than I.
Below is a 2nd stab at a UI / workflow proposal to deal with what we are now calling 'pending changes' aka changes people make to items whilst unaware of changes made by others. Such 'pending changes'
What's important to keep in mind is that changes made by 'other people' are always considered 'pending' and never automatically overwrite changes made by you. In other words, every Chandler is 'sovereign' of their own repository.
Please review the wiki proposal. As usual, there are some changes from what was agreed upon in yesterday's meeting, the most important of which is: *When an item has been deleted and a conflict is detected, the item is *NOT* taken out of the Trash. Instead, the Trash collection displays an error icon.*
Thx, Mimi _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
