[Dev] Re: [Cosmo] Free/Busy in Chandler 0.7

Philippe Bossut pbossut at osafoundation.org
Sun Mar 12 17:03:35 PST 2006


Hi,

Morgen Sagen wrote:
>
> On Mar 12, 2006, at 4:14 PM, Philippe Bossut wrote:
>> [...] For instance, a Chandler user can pick an event in a "not mine" 
>> collection and move it to a "mine" collection making it mine in the 
>> process (e.g. one of those "Events managed for Lorenzo" meeting is a 
>> meeting that you are going to attend).
>
> Actually, as currently implemented, if you drag an item from a 'not 
> mine' collection and copy it to a 'mine' collection, that event will 
> not appear in 'My Calendar'.  In other words 'not mine' currently 
> trumps 'mine'.  The exception to this is if you drag an item from a  
> 'not mine'  *directly* to 'My Calendar' -- in that case it will show 
> up in 'My Calendar'.  There is a discussion about changing this 
> behavior (making 'mine' trump 'not mine') in this bug:  
> https://bugzilla.osafoundation.org/show_bug.cgi?id=5368
I forgot about that bug (or I assumed that we'll go with making "mine" 
trump "not mine").

One thing that bug reminded me which is relevant to this thread is that 
we want something for free/busy which is consistent with what we do for 
minical. We don't want to explain to users how "My Calendar" shows one 
set of event, "minical" is computed on another one and "free/busy" a 3rd 
one... Delay in synchronization is hard enough to cope with that we 
don't want to add difference in logic to the mix.
>> Chandler does not duplicate that meeting. I'm not sure how the sync 
>> works right now (does the event appears in both collections?). If the 
>> event is not duplicated, this won't work.
>
> Regardless of mine/not-mine, if an event lives in two collections 
> within Chandler, and those two collections are published to Cosmo, 
> that event will be published twice (once in each Cosmo collection).  
> It's not really an exact duplicate necessarily because you could be 
> sharing reminders/status for one of those collections, and not the 
> other, so the .ics files representing that event could be different. 
Interesting. So that being cleared, I'm inclined to favor E) because of 
its better "Chandler off line" story (e.g. I update my calendar using 
Scooby while on the go from a kiosk and everyone has an updated 
free/busy to work with. That's cool...).

That being said, the word of caution on consistency made above still 
holds. Something to think about for Jeffrey I guess.

Cheers,
- Philippe



More information about the chandler-dev mailing list