After going back and forth on this on IRC and in bugzilla, Morgen and
I have worked out the following solution:
1. Disable sharing for the Dashboard, In, Out, and Trash collections.
This was the option I originally rejected because I favored allowing
users to share everything, even if they got themselves into weird
workflow situations...but I now see that it's a good forcing function
to prevent users from ending up with duped collections when
Reloading, primarily because there's a better way for users to
'shared their Dashboard collection' across machines.
Logged as: https://bugzilla.osafoundation.org/show_bug.cgi?id=9172
If you didn't understand that summary, here's the long explanation:
+ Sharing the Dashboard, In, Out and Trash collections is most useful
for sharing with yourself across multiple machines. However,
currently, this workflow doesn't work quite.
User has 2 machines: A and B.
+ User shares their Dashboard collection from Machine A.
+ User Saves Settings from Machine A.
+ User Restores Settings from Machine B.
+ Machine B cannot hook up the shared Dashboard collection from
Machine A to the existing Dashboard collection in Machine B. As a
result, the user ends up with a sidebar on Machine B that looks
something like this:
Dashboard (from Machine B)
In
Out
Trash
==========
Dashboard (from Machine A)
Not ideal. Instead, users are much better off re-creating the same
'Dashboard collection' across multiple machines by sharing all of
their user-defined collections from Machine A and then restoring
those shares on Machine B via Save and Restore Settings, Dump and
Reload or Subscribe, etc... This is more labor-intensive, but the
extra 15 minutes of work will result in a much better long-term user
experience with the Dashboard collection.
2. We will proceed with http://bugzilla.osafoundation.org/
show_bug.cgi?id=6545, which was to create 3 additional user-defined
collections, out of the box in order to help users orient themselves
in the UI with some sample data.
Bug 6545 almost bit the dust because it exacerbated the duped-
collection scenario Pieter originally identified, which is logged as:
http://bugzilla.osafoundation.org/show_bug.cgi?id=9169, by creating
more ootb collections that users might share, which in turn would get
duped when users migrated with dump/reload.
However, Morgen and Grant have worked out a solution for this for
Preview: When users reload, Chandler knows not to create the user-
defined ootb collections specified in bug 6545.
Logged as: https://bugzilla.osafoundation.org/show_bug.cgi?id=9173
Morgen, have I captured everything?
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
