On 12/14/07, Mimi Yin <[EMAIL PROTECTED]> wrote: > As I was helping someone set up their Chandler Desktop + Hub account > yesterday, it was kinda painful to watch them try to understand all the > explaining I had to do: > [...]
Yes, prompting to publish -- like the way we now prompt to subscribe -- makes a lot of sense. I think if we move back to "compartmentalized" sharing as I talked about in my last design post then we can solve the "sharing with myself" issue. I just realized that this requires publishing the same collection UUID twice to the server and I'm sure that's an issue Randy, Brian and I will have to resolve. > OPEN ISSUES > + Morgen: What happens if you have already subscribed to collections you > previously published to Chandler Hub and then you set up our Hub account? > Can Chandler figure out that they're the same collections you have on the > server and rationalize them? I believe so. Under the hood I'll need to distinguish between which collections in your account on the server are "private" (meaning just sharing with yourself, or serving as an online backup), and which are being shared with others. You could have two copies of each collection in your account: the private one and the shared one. > + It's kind of weird from the Desktop perspective to have an OOTB Hub > collection sync down to Chandler Desktop. Can we delete this collection for > the Desktop user if the user hasn't added anything to it from the web UI? Well, I'm not sure if Chandler can determine which collection is OOTB. > There are also content modeling improvements we need to make in order to > have it all work truly well. Mainly, you always want to share all attributes > with yourself, but there are some attributes you never want to share with > others (Read/Unread, Alarms, BCC:). Would this relatively 'dumb' fix work to > address this issue? > > + We add Read/Unread/Needs reply status to the list of sharing filters; and > + When you publish, we change the default sharing filters to select > everything; but > + When you subscribe, we set the default sharing filters to only check > Triage Status + Event Status. I think the private/shared copies of the collections will solve this issue instead. The private copies won't have any filtering turned on at all. ~morgen _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
