Not really a KDE related post, but instead one about the OpenChange project.
OpenChange is a project to implement the Microsoft Exchange / Outlook protocols, and we're creeping up on the 0.9 release. For those not familiar with it, the aim is to be wire-level compatible, so that you can use a FOSS client (such as Evolution or an Akonadi client) with an unmodified Exchange server.
OpenChange depends on some underlying Samba4 libraries, so we normally work with the Samba project to get releases that basically match up - we don't want to rely on building bits of Samba4 from the git repository, and we don't want to depend on really on versions of Samba4. Not too far ahead, and not too far behind. Just right...
The next release of Openchange (0.9 "COCHRANE") will rely on Samba 4 alpha9. So the main thing to do is to make sure that we can work with the current state of Samba 4, to provide patches to Samba for stuff that needs to be fixed on the Samba side, and to have changes for OpenChange ready to go.
We expect to release within two weeks of Samba 4 alpha9, but OpenChange 0.9 will be released when it is considered done.
We anticipate a 0.10 release in early 2010, and probably a subsequent 0.11 release prior to 1.0.
I've gone through the trac tickets, and moved anything that can't reasonably be achieved for 0.9 to a 0.10 milestone. Large changes have to wait for 0.10 - it is getting very late to risk destablising libmapi.
So what we still have left:
- integrate exchange2ical work from Ryan Lepinski into trunk
- ensure that OpenChange works with FreeBSD/OpenBSD
- ensure that OpenChange works with OpenSolaris
- libmapi/Samba4 API updates
- mapiproxy/Samba4 API updates and association group API evolution
- a couple of tickets that may not be too hard to fix, related to pkg-config support
- a ticket related to Free / Busy time support that has a crash.
- a patch that checks some return values that we current don't handle.
- some documentation stuff.
Details are on http://trac.openchange.org.
Known problems:
- openchange development server will not be working "as it is". Resolving this requires revision of the OpenChange schema updates (to match Samba4 changes). This may not be resolved for 0.9.
If I've dropped a patch, or there is something you really need for 0.9, now is your chance to make yourself known. Probability of a patch being applied is inversely proportional to complexity, and also inversely proportional to how close I think the release is. That is, simple and soon is good.
Syndicate Blogs
keep it up
First of all I'd like to thank you and all other OpenChange developers for creating this highly important library. I can't possibly express how important I feel this project is.
Exchange interoperability is truly the most important missing link in the business-oriented FOSS stack in my opinion. It has taken a long time, and we're still not completely there yet. IMAP "works", provided that your Exchange admin is friendly enough to enable it, but managing appointments and contacts through Outlook Web Access gets old really fast.
It makes me wonder though why all of this has taken so long. I certainly don't mean to insult the OpenChange or Samba projects, on the contrary, I have a lot of respect for these major efforts. But what I don't understand is why some big corporation hasn't put its resources behind the development of libmapi and client support for it? I work in system administration, and have been using a Linux desktop for years, and in my daily routines there are only two areas left where I must admit that Microsoft holds a trump card: the Exchange/Outlook/Active Directory combination and the Visio diagramming tool (Kivio and Dia aren't half bad, but it's all in the stencils).
There are many, many large companies who could have a lot to win if Microsoft's power would fade away, so why are they holding back from accelerating a potential future Microsoft exodus? It's not a secret that the never-ending money flow from Windows Server + Exchange + Office licenses is vital in upholding their empire. GNU/Linux has been up to the job for years now, what has been missing is a non-disruptive migration path and OpenChange plays a key role in that.
Is it because the bigger players want to gobble up Exchange itself as well (e.g. IBM, open source groupware firms)? Or because they want to have all your mail on their own servers instead (like Google?) Or is it because they feel companies should completely dump Microsoft at once and switch both clients & mailserver & directory and all other tools at the same time? Is it a lack of interest by many open-source purists who think MAPI is evil and shouldn't find its way onto Linux desktops?
I feel that's a poor strategy. I'm certain there are thousands and thousands of office workers who'd do perfectly fine with a (KDE) Linux desktop if only they could get to their calendar/free-busy schedules through their mail client. People are addicted to the integrated groupware experience, it's essential in their daily routine, so making the switch has never really been an option in the past, and it still isn't today. I feel that Kontact would make an absolutely perfect Outlook replacement but Windows 7, Exchange 2010 and Office System 2010 are out already and we're still not there. The coming year many companies will evaluate upgrading, and may evaluate FOSS alternatives, and come to the conclusion that upgrading is easier and certainly a lot less risky. Meanwhile all that money keeps flowing to Redmond so they can keep working on getting more companies' data locked away for good in Sharepoint...
Trying to get IMAP + LDAP + a CalDAV server set up by IT departments who have mostly Windows experience is too disruptive for the users and they'll complain loudly if it doesn't work 100% all of the time. People would kill in order not to lose their Outlook companion... Kontact beats it in my opinion, but Outlook speaks Exchange and its working fine. I don't know about the situation with Domino/Notes as I've never worked at a company using it.
Anyway... Yesterday I read about the Pledge to fund Krita development. I was never really interested in Krita, I've been using GIMP for years, but now that I've had a look at it I did something that I hadn't done before in my life: I donated. And it felt good. As I see it, being proficient in open source environments has been paying my bills for five years now, and while using it, evangelizing it, filing bugs and taking part in communities certainly helps, money makes the world go round, doesn't it?
It made me think why OpenChange hadn't started such a Pledgie or similar highly-publicized raise yet? That was in fact the reason I started googling about the state of affairs and how I landed on your blog. Yes, I've found and used the "Donate!" button now too. For the first time I'm putting my money where my mouth is
I think you'd get a lot more people to donate if they only knew they could and knew about what's at stake. Many people like me would love to get more co-workers on Linux, but the absence of highly integrated groupware functionality is an incredible handicap.
Of course, regardless of finances, nine women can't have a baby in one month.
Keep up the good work.