Re: 'Weird triage and sharing bugs to focus on' Redux

Hi Aparna,

I've noticed this behavior for non-message events as well. Perhaps we  
should first give you an opportunity to investigate the problem a  
little bit and then meet up to see if we can design an effective test  
session. Assuming we conclude that a test session would help, do you  
think we could aim for next Wednesday? I think we should make sure  
Morgen is available and possibly Jeffrey as well.

Mimi

On Nov 30, 2007, at 10:10 PM, Aparna Kadakia wrote:

> One observation is we have been noticing these odd cases in case of  
> shared calendars that are being updated by multiple people and  
> rendered thru multiple states thru edit/update. Yesterday, I  
> mentioned to Philippe that I was seeing some odd behaviour with the  
> QA calendar as well where some of the old PTOs and meetings were  
> popping into the NOW section. I haven't had a chance to completely  
> investigate that and figure out if they are basically dups of bugs  
> you have filed below or different ones. I will look into that shortly.
>
> IOW, I think the scenario that will help nail these cases is  
> getting more people to use and update shared calendars. I am all  
> for doing a test session for this but generally speaking I haven't  
> been able to trigger these cases on demand. I happen to encounter  
> them occasionally with QA calendar.
>
> One idea is perhaps we could come up with some sharing scenarios  
> what require edit/update and have multiple people run thru those  
> scenarios in a single shared calendar during the test session. I  
> can work with you on coming up with those cases.
>
> In the meantime I will investigate the "popping into NOW" cases in  
> the QA calendar.
>
> On Nov 30, 2007, at 3:56 PM, Mimi Yin wrote:
>
>> Back in October, I started a thread on the design list re: weird  
>> triage/recurrence/sharing bugs having to do with items being  
>> marked Unread and popping into the NOW section for inexplicable  
>> reasons.
>>
>> I believe we've addressed some of the underlying causes (ie.  
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=10799: Need a  
>> mechanism to ignore certain EIM fields when determining which  
>> items move to NOW or get marked unread). But I believe there are  
>> still bugs at large.
>>
>> 'Notification' via automatically popping items into the NOW  
>> section is core to the personal information management and  
>> collaboration workflows. What do we need to do to make sure we've  
>> addressed this problem for 1.0 (which is in reality, less than a  
>> month away if you take the holidays into consideration)?
>>
>> Can we enlist the help of the Users list in some way? Have a  
>> dedicated test session? Ideas?
>> Mimi
>>
>> Below is a screenshot of my Office Calendar collection after 1.5  
>> days.
>>
>> Entire recurring series keep popping into NOW but no evidence of  
>> global edit
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=10948
>> - See IRC QA Session item that is selected in screenshot, that's a  
>> good example of this bug.
>> - I wonder if bug 10948 is somehow related to: https:// 
>> bugzilla.osafoundation.org/show_bug.cgi?id=10795 (Byline does not  
>> match Who column)
>>
>> Odd mixture of events keep popping into NOW in the Office Calendar
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=10894
>>
>> Nov 12th, 2007 Weekly PPD Meeting keeps popping back to NOW
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=11475
>> <uhoh-now.png>
>

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design