GSoC 2010 Mid term evaluations

Mid term evaluations are here and I hope to have a progress meeting with my mentor to get his detailed feedback on the project.

I have packaged the MailNews sync engine into an xpi file and uploaded it to the mailnews sync project site (http://code.google.com/p/weave-mailnews-sync/downloads/list). It requires Firefox 1.4 (https://addons.mozilla.org/en-US/firefox/addon/10868/) to work (it is basically an extension of an extension!). The MailNews Sync extension currently syncs status, flag and tag data of Feed and Newsgroup items between different Seamonkey instances. I tested it on Seamonkey 2.0. I couldn't test it on Seamonkey trunk 2.1 yet but I'm hoping that everything will work smoothly there as well. Since comm-central build is not working (sm tinderbox is having a few hot days..) I will test with currently available nightly build.

Few things left to be done this week:

- Decide on a solid test plan for MailNews sync engine
- Start testing and bug fixing for mailnews engine

Update!

I have posted the MailNews engine test plan to the project site ( http://code.google.com/p/weave-mailnews-sync/wiki/TestPlan?ts=1279510088&updated=TestPlan ). Testing will be done using 4 configurations.

Week 1 (18th to 24th July) :Config 01&02
Week 2 (25th to 31st July) : Config 03&04

All issues will be reported and tracked on http://code.google.com/p/weave-mailnews-sync/issues/list.

Testing begin today!

Writing the new mailnews sync engine as a separate extension

I have shifted the mailnews sync engine into a separate extension so that it can be used with existing weave extension. You can find the code here.

http://svn2.xp-dev.com/svn/mailnews-sync/trunk/

I am currently working on this repository but the basic engine functionality is already implemented. This extension should be used along with latest Firefox Sync version(1.4a1pre). New mailnews engine however will not show up in the Sync preferences pane unless a slight code change is made in weave(http://pastebin.mozilla.org/733149). However the mailnews engine is set to be active by default.

I will start submitting the mailnews engine patches to Weave as well soon. Since Weave is due to be a part of the central mozilla code i need to have the new engine code integrated into Weave.