264
edits
No edit summary |
XFallenAngel (talk | contribs) m (→Meeting Log) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<small><<[[Calendar:Status Meetings:2006-12-13| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings: | <small><<[[Calendar:Status Meetings:2006-12-13| previous meeting]] | [[Calendar:Status Meetings|index]] | [[Calendar:Status Meetings:2007-01-03| next meeting >>]]</small> | ||
== Meeting Details == | == Meeting Details == | ||
Line 71: | Line 71: | ||
*** And there is another issue that Lightning is still lacking in terms of group calendaring abilities. | *** And there is another issue that Lightning is still lacking in terms of group calendaring abilities. | ||
*** There is a bug to help create non-default providers (bug 348028). | *** There is a bug to help create non-default providers (bug 348028). | ||
*** '''TODO:''' | *** '''TODO:''' Philipp (xFallenAngel)will start creating a wiki page to list the hooks that the provider developers will need in order to aid provider developers | ||
*** The fact that some of the items (for group and remote scheduling) aren't in the product doesn't mean that we didn't want those features, just that we haven't needed them yet. Rather than having each and every provider re-invent these items, we need to define an interface and a common UI that everyone uses and everyone can program against that. | *** The fact that some of the items (for group and remote scheduling) aren't in the product doesn't mean that we didn't want those features, just that we haven't needed them yet. Rather than having each and every provider re-invent these items, we need to define an interface and a common UI that everyone uses and everyone can program against that. | ||
*** Dmose: I think that ^^^^ has been our strategy all along, and we will continue that way. | *** Dmose: I think that ^^^^ has been our strategy all along, and we will continue that way. |
edits