I agree it's not ideal, but I wonder if the fallout is that dire in
the Preview timeframe.
Just to play devil's advocate, in the brief discussion we had in the
Design Session, we realized that all this would mean is that:
1. Chandler users would end up resolving any conflicts, not Cosmo
Casual Collaborators.
2. Cosmo Casual Collaborators wouldn't see changes made by Chandler
users. Instead, Cosmo changes would just automatically overwrite
Chandler user changes on the server.
3. However, Chandler users wouldn't have their local changes
automatically overwritten by Cosmo Casual Collaborators. Instead,
Cosmo changes would get stored as Pending Changes and the Chandler
user would decide whether or not to apply them.
#2 is a drag, but we're hoping it won't be a big deal since Casual
Collaborators will after all be Casual.
Mimi
On Feb 8, 2007, at 7:18 AM, Andre Mueninghoff wrote:
I agree with Davor. It seems to me this behavior may discourage
Chandler
users from collaborating with the "casual collaborator" type users of
Cosmo. In a sense, inserting some separation between the preview of
Cosmo from the preview of Chandler. Bad weather in the ecosystem,
so to
speak.
Andre
On Wed, 07 Feb 2007 22:33:04 -0800, "Davor Cubranic"
<[EMAIL PROTECTED]> said:
Mimi Yin wrote:
+ Is it a problem that Cosmo won't have conflict resolution UI and
won't have a way to 'quarantine' conflicting pending changes? In
other
words, whatever changes the Cosmo user makes will overwrite anything
any Chandler user has synced to the server in the meantime.
Uh, this sounds like bad news...
Davor
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
--
Andre Mueninghoff
[EMAIL PROTECTED]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design