Calendar:Feature Implementations:iTIP-iMIP: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
==Proposal pages== | ==Proposal pages== | ||
*<strike>[[Calendar:iTIP and iMIP Support| Original iTIP and iMIP Proposal]]</strike> | *<strike>[[Calendar:iTIP and iMIP Support| Original iTIP and iMIP Proposal]]</strike> | ||
* [[Calendar:Feature_Implementations:iTIP-iMIP:iTIP_Processor| New iTIP Processor Interface Proposal]] | |||
* (No proposal page) - natural language processing of emails/webpages for dates/events/schedules. Allows people to get the ease of iTIP/iMIP without requiring that others use it as well. (jminta) | * (No proposal page) - natural language processing of emails/webpages for dates/events/schedules. Allows people to get the ease of iTIP/iMIP without requiring that others use it as well. (jminta) | ||
Revision as of 20:55, 23 October 2006
This page is meant to be used by calendar developers. To add minor comments/feedback, please use the discussion page. More extensive discussion should be taken the newsgroup.
Basic overview
This page covers features generally related to... This is cool because... Our eventual goal(s) for this feature include...
Proposal pages
Original iTIP and iMIP Proposal- New iTIP Processor Interface Proposal
- (No proposal page) - natural language processing of emails/webpages for dates/events/schedules. Allows people to get the ease of iTIP/iMIP without requiring that others use it as well. (jminta)
Related bugs
Design/Implementation status on the CVS trunk as of YYYY/MM/DD
We can do all this cool stuff...