Community
Participate
Working Groups
Provide an extension point structure to allow Mail Calendar extensions
What is the scope of the mail and calendaring support, i.e. what kind of functionality would these connectors provide?
There is a need to provide mail/canlendar services with different settings e.g. Outlook, SMTP/Vcalender, mailto/Vcanlendar, etc.. SMTP may require specific corporate server addresses, So the idea is to provide one generic for open source e.g. mailto/Vcalendar and leave the other possibilities opened for specific needs but establishing an interface to treat them the same way.
That sounds interesting. I would like to understand how that fits into the framework and what kind of use cases these connectors would support in R4E. I have added an item to the agenda for tomorrow's meeting to discuss this.
Can we keep all of this in the R4E namespace for now? I think if we later generalize the code it is much more likely to move to the o.e.m.commons project since there is some potential for reuse across all sub-projects. Unfortunately the current name "notifications" is already associated with the desktop notifications API. Would it be possible to choose another name for the this framework. Maybe something related to messages or events would work, e.g. org.eclipse.mylyn.reviews.r4e.messages or org.eclipse.mylyn.reviews.r4e.events.
as discussed during a previous mylyn meeting, we can keep the name "notifications" for now. We can re-open the discussion before merging the functionality. this is now fixed.
