So when Sheila and I met with Katie, we talked about having 2 guiding
principles for interop bugs. Let me see if I can articulate them here:
1. Make it easy and useful for iCal/Lightening users to share with
Chandler Desktop users. This could be Desktop users subscribing to
calendars from iCal/Lightening users or vice versa.
2. Make it easy and useful for iCal/Lightening users to use Chandler
Hub and make the Chandler Hub experience a solid representative of
Chandler's core value as a "knowledge manager" so that we get more
users using the Chandler eco-system for knowledge management.
The flip-side of this is that we are *not* targeting iCal/Lightening
users looking for Exchange-like functionality. We are looking for
iCal/Lightening users who are in need of a Chandler-style knowledge
management system.
Questions:
- What about Evolution? Mulberry? other CalDAV clients?
- Do we also want / need to support Google Calendar users to the
extent that we support iCal / Lightening users?
From looking at the bugs, I can't always figure out what the end-
user consequences are. For example:
1. Are we corrupting data? Losing data, changing data, etc.
2. Are we missing data? Is there data you see in iCal, but don't see
in the web UI? Are we talking entire events or metadata of event
items? How critical, universally used is the missing data? Everyone
finds event start-time useful. Not everyone finds task due dates
useful. Very few people find event status useful.
3. How frequent are these scenarios? Once a month you might notice
something? Every day? Every other event is wrong?
4. How common are these scenarios? Every iCal/Lightening user will
notice this. One person has reported it.
More in-line...
On Feb 27, 2008, at 3:28 PM, Sheila Mooney wrote:
So Randy and I met on Monday to review all the server related bugs
and figure out what should be worked on in the short term and what
should be punted to future. One question that did come up was
around interop. There are several interop bugs we came across and
we weren't really sure how to determine if we should be fixing
these soon.
I wanted to hear from others about how we should be crafting our
interop goals to target these and future bugs.
iCAL BUGS
https://bugzilla.osafoundation.org/show_bug.cgi?id=10969
ical doesn't like multiple dates in single EXDATE property
- Couldn't even make up a user consequence for this one ;) Randy, how
does this bug manifest itself in the UI?
https://bugzilla.osafoundation.org/show_bug.cgi?id=11216
iCal3 Interop :: Creating a calendar causes iCal to mark the CalDAV
account offline
- this is really an iCal bug, no? To 'fix' this on our end, we'd have
to implement scheduling, which we're not planning on doing any time
soon.
- There is awkward workaround for this, which is to create all
calendars on Hub, instead of from iCal.
- Nominate for Future
SUPPORT FOR TASKS
https://bugzilla.osafoundation.org/show_bug.cgi?id=11808
iCal not seeing tasks
- Well all items in Chandler are now tasks more or less. So we could
sync all non-event items so that they appear as Tasks in CalDAV
clients. This would also provide a way for us to leverage iSync to
get Chandler data onto mobile devices
- Nominate for Future
https://bugzilla.osafoundation.org/show_bug.cgi?id=11236
Tasks managed with CalDAV should set triage status intelligently
- I think this bug depends on how we resolve bug 11808 above, whether
we try to make sharing Tasks work between Chandler and other CalDAV
clients.
- There are also a number of open design issues about whether to auto-
triage tasks based on due dates, which we don't have a concept of in
Chandler. The closest thing we have for non-event item is custom
alarms (ticklers) and we currently do *not* auto-triage based on
ticklers.
- I *do* think mapping 'Done' in CalDAV to Chandler 'Done' is a
pretty straightforward thing.
- Nominate for Future
OTHER CLIENT SPECIFIC BUGS
https://bugzilla.osafoundation.org/show_bug.cgi?id=9813
Evolution using CalDAV plugin fails to sync with Cosmo and fails to
create events
- Depends on what clients we decide to target
https://bugzilla.osafoundation.org/show_bug.cgi?id=11480
Mulberry 4.0.8 + Chandler Hub
- Depends on what clients we decide to target
https://bugzilla.osafoundation.org/show_bug.cgi?id=11706
Events imported on Google Calendar appear "(No Subject)"
- According to the bug, this happens for occurrences that have been
modified as "exceptions".
- Again, depends on what clients we decide to target
I am posting this on chandler-dev since planning related and we
might as well think about it more globally to cover desktop issues
as well.
Cheers,
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
