[Chandler-dev] Re: Items in multiple collections -- avoid for now (until Cosmo 0.7)

[Aparna Kadakia]

Yes, we have some events like the IRC QA sessions, CHandler/Cosmo Bug  
Councils etc are both in OFfice Calendar as well as the QA calendar.  
These were not copied recently but back in the days when we starting  
dogfooding with the QA Calendar.

On Aug 17, 2007, at 3:19 PM, Katie Capps Parlante wrote:

> Many are in the PeePeeDee collection, and many others are in  
> personal calendars. It is a common use case to put an office  
> calendar event in another calendar.
>
> Cheers,
> Katie
>
> Morgen Sagen wrote:
>> So we're still getting events with UUIDs for their titles.  The
>> recurring events currently affected by this are:
>> Chandler Bug Council
>> Chandler Desktop Bug Council
>> Cosmo Bug Council
>> Cosmo Meeting
>> Cosmo release meeting
>> Desktop Tech Discussion
>> IRC Interns/SoC Chat
>> IRC QA Session
>> OSAF Staff Mtg
>> Ops Group Meeting
>> QA/Release
>> Weekly PPD Meeting
>> Weekly Preview Meeting
>> Weekly open design session - conf bridge in use
>> wx IRC Office Hour
>> Are these events that are in multiple shared collections?
>> Thanks,
>> ~morgen
>> On 8/3/07, Morgen Sagen <morgen at osafoundation.org> wrote:
>>> Recently I discovered (and Randy quickly fixed) a Cosmo bug where a
>>> change to a recurring event in  one collection wasn't being  
>>> reflected
>>> in other collections the item was also in on the server.  However,
>>> this fix won't be on the Hub until 0.7 is installed there, so it is
>>> probably a good idea for Hub users to not copy recurring events from
>>> one shared collection to another.  I suppose we could change  
>>> Chandler
>>> code to prevent such copying, but I don't know if it's worth it at
>>> this point, since the Hub upgrade should happen in a few weeks.
>>>
>>> So for now, don't drag recurring events between shared collections.
>>>
>>> Thanks,
>>> ~morgen
>>>
>>> P.S.  If you haven't already, please upgrade your Chandler to the
>>> latest checkpoint (or SVN) so we can see if the mysterious UUID- 
>>> titled
>>> events are due to old clients or a current bug.
>>>
>>>    http://downloads.osafoundation.org/
>>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> Open Source Applications Foundation "chandler-dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev