Calendar Talk:QA CalDAV Support

Column meanings?

Nice start. But...

What do the columns (0.8 | 0.9 | basic | scheduling) mean in the CalDAV support matrix? (I expected either the basic column to mean the same as the 0.9 column, so basic is checked if Lightning 0.9 basic features work with that server, but they are different. The 0.9 column is not the same as the scheduling column either.)

Is CalDAV scheduling new for 0.9?

Do the columns Features/Basic-or-scheduling refer to whether the server version supports the feature, or whether Lightning is compatible to how the server implemented the feature?

Maybe reorganize the columns

 | Calendar |    Features        |
 |0.8 | 0.9 | basic | scheduling |

as follows:

 __________|____Calendar__________|
 __________|_0.8_|____0.9_________|
 Scheduling|Basic|Basic|Scheduling|

Gekacheka 13:53, 28 August 2008 (UTC)

Tasks

Another proposal, make a separate column for tasks (todos), since some server (at least zimbra) have not implemented tasks parallel with events:

 |____Mozilla Calendar__________|
 |_0.8__|________0.9____________|
 |Access|___Access___|Scheduling|
 |Events|Events|Tasks|__Events__|

Access refers to creating and editing events and tasks via rfc4791(CalDAV-access). Scheduling refers to proposing and accepting events via CalDAV-sched.

Gekacheka 17:55, 20 September 2008 (UTC)

Three states

Maybe distinguish problems that are because server doesn't implement feature vs. other problems. Then table won't need to have take space with separate columns for indicating both whether server implements feature and whether it works with moz calendars.

Each server+client cell may have one of 3 states:

• (server+client works)
• (server+client fails)
• (not implemented by server)

(If not implemented by client, then client feature column doesn't exist)

Gekacheka 17:55, 20 September 2008 (UTC)

DAVMail

It might be a good idea to add information for DAVMail (an Exchange to CalDAV proxy written in Java). Russell Jones 09:54, 17 September 2009 (UTC)