[Design] Fwd: [Bug 6978] All recurring mail occurrences appear in the In collection

[Mimi Yin]

Forwarding this to the design list, we've started a discussion in  
bugzilla about Communications + Recurring events....answering  
Jeffrey's questions in-line.

Begin forwarded message:

> From: bug-comment at osafoundation.org
> Date: October 5, 2006 4:29:39 PM PDT
> To: mimi at osafoundation.org
> Subject: [Bug 6978] All recurring mail occurrences appear in the In  
> collection
>
> http://bugzilla.osafoundation.org/show_bug.cgi?id=6978
>
>
>
>
>
> ------- Comment #2 from jeffrey at osafoundation.org  2006-10-05 16:29  
> PST -------
> Subject: Re:  All recurring mail occurrences appear in the In  
> collection
>
> But can you send just one occurrence of a recurring mail?

Conceptually, that makes sense. I invite you to just this meeting.  
Not the entire series.

>
> If you can send individual occurrences, how do you mail all of a
> recurring event?

When you stamp a recurring event to address it, the standard edit  
dialog pops up to say:

Address 'All' 'Just this event' or 'This and Future', you select All.

>
> We can certainly store a data structure representing a recurring
> communication, but I don't see how one can distinguish communication
> about a recurring event (please come to this meeting every Thursday!)
> and recurring communications (I'm sending out the notes from this
> Thursday's instance of the regularly scheduled Thursday meeting).

Could we do any of the following?

1. The recurrence field would say Once as opposed to Every week until  
an End date
2. The date/time fields say Thursday from 3-4PM instead of Thursday,  
October 5, 2006 from 3-4PM

>
>
> -- 
> Configure bugmail: http://bugzilla.osafoundation.org/userprefs.cgi? 
> tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20061005/f3eb5368/attachment.html