There aren't any good open calendar systems because geeks don't use calendars. :)
I got really interested in calendaring when our CEO insisted on Exchange for the calendaring, and I get the impression that the lack of a good open calendaring implementation is holding back a lot of businesses from going off Exchange+Outlook and onto free software on their mail servers. It's best to think of Outlook not as a mail client but as a database thick client for displaying objects from an OODB in forms. One of those forms is a mail message; calendar and contact items are others.
I think WebDAV is the answer, as it actually works where iCap doesn't. But unfortunately to really take off whatever solution has to provide some sort of DCE/RPC Exchangealike interface. Nobody's done this yet. All the free software exchange implementations require CLOSED-SOURCE client plugins, which tend to be flaky.
You're right about human scaleability problems; if it works at all people are going to use it to arrange supervisions.
You might be best off finding a way to funnel money or programmer time to the SRCF, as they were originally set up for this sort of thing: projects that the CS deemed infeasible due to lack of resources, security risks, Not Invented Here and spurious claims of impossibility...
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2004-02-18 20:26 (UTC)I got really interested in calendaring when our CEO insisted on Exchange for the calendaring, and I get the impression that the lack of a good open calendaring implementation is holding back a lot of businesses from going off Exchange+Outlook and onto free software on their mail servers. It's best to think of Outlook not as a mail client but as a database thick client for displaying objects from an OODB in forms. One of those forms is a mail message; calendar and contact items are others.
I think WebDAV is the answer, as it actually works where iCap doesn't. But unfortunately to really take off whatever solution has to provide some sort of DCE/RPC Exchangealike interface. Nobody's done this yet. All the free software exchange implementations require CLOSED-SOURCE client plugins, which tend to be flaky.
You're right about human scaleability problems; if it works at all people are going to use it to arrange supervisions.
You might be best off finding a way to funnel money or programmer time to the SRCF, as they were originally set up for this sort of thing: projects that the CS deemed infeasible due to lack of resources, security risks, Not Invented Here and spurious claims of impossibility...
As for a directory, what's wrong with LDAP?