Any idea how much time you will be spending on it? Do you have deliverables? Are you full time at this company or contract basis?I am full time, and it looks like this project will be my #1 project... until it's reasonably working.
Of course, it is not my one and only occupation: I'm not far from truth if I say 4 hours/day.
Under what license if I may ask? Have you (or your company) considered a dual license scheme? This may help you recoup development costs.our goal is to grab customers from Exchange world, not to sell the connector alone.
What are those needs exactly?we are an italian ISP: besides raw connectivity, we sell some value added services.
Some of these are mail and calendaring for workgroup.
We already have our self-developed mail and calendaring servers.
The mail system talks imap, pop3 and smtp while the calendar system is brand new and right now it only has its own web client and palm support.
There is no standard calendaring protocol yet: afaik webdav is the nearest-to-standard interface, and we have planned support for it.
Our customers are mainly medium to large companies, which are used to have Outlook/Exchange or LotusNotes as workgroup tools: we would like to interface Outlook to our servers with 100% features support.
And here comes the need for a connector.
As you can see, we really have no interest in selling the connector alone.
On the other side, an open source project can bring wide testing - which is kindly welcome.
Our needs could be resumed as "an Outlook plugin that lets you exploit every feature of Outlook client with a server talking imap, smtp and webdav (or whatever calendaring protocol should arise)"
I am the lead developer of the oser project (http://www.oserproject.org) which is developing an open source exchange replacement. I am working with the openchange (http://www.openchange.org) project that is developing an exchange compatible layer that my project will use.
This was my first attempt: an "Exchange emulator" that lets our system appear just like an exchange server. No distributed software, single application environment... it would be the cleanest solution.
But I read that the reverse-engineering of the exchange rpcs is a tough problem and could take years.
Am I wrong?
Luca
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ otlkcon-devel mailing list otlkcon-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/otlkcon-devel
