Comment 88 for bug 633352

Revision history for this message
In , Philipp-bugzilla (philipp-bugzilla) wrote :

(In reply to G. Richard Bellamy from comment #36)
> I'm running 1.9.1 on Windows 7 x64 SP1, and have disabled offline calendars.
> I still have this problem.
>
> As for comment #22, it never ceases to amaze me that software teams identify
> outside problems as the source of a bug as if that alleviates them from
> responsibility.
I think you overestimate the "software team" behind Lightning. We are very low on active contributors, there is me and a handful of people that have time once in a while to work on Lightning between job, wife and kids. With the little time left we try to take care of the most pressing issues, which is right now making sure the builds run, fixing major bugs (like: Lightning cannot be used at all because of a regression or change in the Mozilla Platform) and doing some minimal testing to make sure its not broken.

I agree (and I bet Stefan does too) that dismissing alarms is a vital feature, but from the looks of this bug I don't think its just one issue that is easy to identify and fix. Dismissing recurring events works fine for me, as some others have confirmed. Therefore I cannot debug this issue.

> And finally, my argument is well-founded regardless of whether or not I
> offer to "pitch in and fix it myself." While that's another favorite meme of
> the FOSS community (e.g. "Hey, if it's so important to you, we welcome pull
> requests!"), it's also flawed in that feedback is feedback, and should be
> taken on its own merits regardless of whether or not it's backed-up by
> substantive offers to help.

Feedback is very well welcome, Stefan merely asked for confirmation with another caldav server. This bug is (in general!) about dismissing reminders on caldav servers, not specific to Google Calendar. Nevertheless, we have taken action to make sure Google is aware of the issue and at least partially they seemed to have fixed this.

In fact, the best kind of feedback are reliable steps to reproduce. This doesn't just mean "it doesn't work for me when I dismiss a specific recurring reminder I happen to have in my calendar", but steps from a clean state to the bug with any edge case configuration that may apply (for example: 1. subscribe to a calendar where I am not owner (possible edge case) 2. create a recurring event in the Google Calendar UI 3. Modify that recurring event to have a reminder in the past 4. Synchronize in Lightning 5. Dismiss reminder. My extension used are ...)

Note also that by coincidence, a member of the team is working on an alternative that will allow you to dismiss the alarms locally, which will fix the problem for Google Calendar. Search bugzilla for details.

Thank you for your understanding, I hope you see our situation a little better now. If you would like to discuss further, please refrain from adding a comment to this bug, I am happy to reply via email or in the mozilla.support.calendar newsgroup if you cc me.