Re: [Evolution-hackers] MAPI backend

2008-09-05 Thread Suman Manjunath
On Tue, Sep 2, 2008 at 11:17 PM, Patrick Ohly [EMAIL PROTECTED] wrote:
 On Tue, 2008-08-19 at 20:22 +0200, Patrick Ohly wrote:
 I'm on Exchange 2007 now. Setting up the MAPI backend worked, but I had
 to patch the source to get past a calendar authentication problem [1].

will take a look later today :-)

 Afterwards I could see some events, but not all. It seems that recurring
 meetings are not yet supported: these seem to be the ones that I'm
 missing and creating one anew leads to an unspecific error message.

Just added recurrence support in r9483 (Note: You need to update to
LibMAPI r710)
Except 'modifying single instances of recurring appointments', all
sorts of recurrence-rules which are supported by evolution are
fetched/can be set.

 FWIW, I also had other problems (I don't plan to file bug reports for
 those because I assume that it's too early for that):
  * the character set for emails were detected incorrectly, thus
displaying emails with English text with Chinese (?) characters

this might be related to fetching the PR_BODY_HTML property. I've
removed it in my last commit. Lemme know if you still see this issue.

Evolution-hackers mailing list

Re: [Evolution-hackers] Evolution: Taking forward...

2008-09-05 Thread Lucian Langa
I was kindly asked for this:

Permission granted for any pieces of code I've produced.

Lucian Langa.

 We have had a set of problems that we are carrying around for
 some time like :
   * Copyright assignments, which is not the best way
 looking for the future of Evolution. It sucks and sort of
 limits contributions to Evolution and we wanted to drop it.
   * The current licensing incompatibility issues of
 Evolution with Samba4/libmapi (GPLv3). Evolution needs to link
 with libmapi/samba4 for the new mapi based connector being
 developed for Exchange 2007.
 So here is the plan :
   * Drop Evolution copyright assignments and make it
 really easy to contribute to Evolution
   * Move Evolution licensing to  LGPL v2 and LGPL v3 to
 let us re-use the code more easily around the platform.  This
 also moves us closer to Thunderbird's MPL/LGPL model. 
 We think this is good for Evolution and (of course) we
 continue to invest in Evolution. We are also working to ensure
 we have the rights to re-license all of the code. We will do
 the licensing/header changes as we audit the code ownership
 It would be really helpful if you can post a public/explicit
 mail with permissions to do it, or code pointers - if you
 think you wrote a piece of Evolution code  object.
 We are really excited about this and we feel this would really
 help Evolution a lot. We need your support now for making this
 change and to take Evolution to great heights.
 ´╗┐Thanks for your contributions and support.

Evolution-hackers mailing list