Summary of work from June 9th to June 22th

In the past two weeks I've finished my planned work before midterm. Here are the details:

To bring the GUI configuration of module EAS back to use, several things are done: the basic configuration and collection code for configuration, the EAS server auto-detect aspect, and some update to the deprecated usage of gtk+ in our project. Some steps are similar to the EWS module, so I borrowed some code from EWS.

Since I will have several final exams in the few weeks, the remaining part of my project will be covered a little bit later, maybe start at mid-July.

Summary of work from May 26th to June 8th

After two weeks of coding, the task planned before midterm has been partly accomplished. Here is the work:

The main part of the configuration UI of EAS has been finished, including the whole configuration step and the auto-discover function. More details will be added and we will finish that after some test.

There are several exams ahead, so I will focus on this project recently and hope to finish the work earlier to save some time for those tests.

Summary of work from May 12th to May 25th

These two weeks are right before GSoC's start of coding, so I did some research work and made my first commit.

1. Some research work: digging into the Evolution-ActiveSync module, learning the implementation of the outdated EPlugin, and the usage of EExtension.

2. First commit: Trying to bring the GUI configuration of EAS back to use. Tested on the Evolution on my laptop, and waiting for my mentor's opinion. It should be a good start, I believe.

Helping people around the world is something wonderful. I also joined the TED translation group to translate the subtitle into Chinese so that more people, especially the people in my country, can reach the greatest idea in the world. Keep working.

Summary of work from April 27th to May 11th

In the first two weeks of our project, I did some work with our community and my mentor since it's the community bonding period.

1. Some things regarding to GNOME community, like an introduction letter, a GNOME wiki page about my project, and an application for Planet GNOME (though not accepted yet). Also, IRC and mailing list are involved.

2. Communication with my mentor, Mr. Woodhouse. I've figured out the implementation of the first step of my project with the help from Mr. Woodhouse, and are working on that now. It will be committed soon.

Thanks GNOME to give me this chance to make my contribution to the open source world, and I'm on my way~

Participation of GSoC 2015

Got accepted by this year's GSoC, and following are some tips for anyone who may be interested to apply:

Feel free to contact your potential mentor: mentors are all friendly and kind people, they will be glad to guide anyone who is willing to contribute to the open source world(at least in my experience), and their opinions really matter in your apply. So please pay more attention on your communication. Even you are not accepted, their help will makes your coding easier.

Pay attention to the project you want to apply: to show that you are the right person for them, you have to dig into the project and make some patches. Maybe it's not easy for a person who is totally new to a project to make a patch, but you really need one to show your programming skill and interest in that project.

There are a lot of helpful information on the Internet about GSoC, but these two tips above will make you special out of other applicants. Hope it will help you~

Hello World!

Hello World!