Google Summer of Code Informations

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search

Back to home page of
the Dolibarr foundation

SoC Information

This is information page submitted to Google as Application in Google Summer of Code (GSOC). The submitter automatically becomes primary Admin. Most entries are mandatory and have to be filled out before the application can be submitted. To submit organization, we need at least two GSOC accounts called link_id.

For this we must create an account with form: http://www.google-melange.com/gsoc/profile/google/gsoc2012 (link_id is visible on "My profile" screen)

The two administrators GSOC for the foundation are:

  • Laurent Destailleur: link_id = eldy10


Organization Id:

dolibarr

Organization Name:

Dolibarr Foundation

Description:

The Dolibarr foundation is a french foundation created to develop and promote Dolibarr ERP-CRM software. Dolibarr is a web software to manage a small or mid-sized company, freelance or foundations. Development of software started during year 2002. The Dolibarr foundation was created in 2009 by Dolibarr users for Dolibarr users to develop and enhance Dolibarr software.

Home page:

http://www.dolibarr.org/

Main Organization License:

GNU General Public License version 2.0 (GPLv2) [Dropdown box answer!]

Backup admin

regishoussin

What is URL of ideas page

http://wiki.dolibarr.org/index.php/Google_Summer_of_Code_Ideas_2012

What is the main IRC channel for your organization

irc://freenode.net:6667/dolibarr

What is the main development mailing list

https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

Why is your organization applying to participate in GSoC? What do you hope to gain by participating?

Dolibarr project has a lot of developers into europe and south america. We lack developers from other area (north america and asia). Participating to Google Summer of Code may be a good way to promote developers from such area. Also the project becomes a big success into OpenSource world and we need more developers to develop more "touched" features the core team has no time to work on. Also, we hope developers found with Google summer of code are interesting people so that they might be valuable for project.

Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.

No

If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?*

No

Does your organization have an application template you would like to see students use? If so, please provide it now.*

Information for template for ideas is described on page: http://wiki.dolibarr.org/index.php/Google_Summer_of_Code_Ideas_2012

What criteria did you use to select your mentors for this year's program? Please be as specific as possible.*

As we apply for the first time, we don't want to take any risk. The mentors were chosen according to their activity on project. This means mentors are the major contributors of project (Laurent Destailleur, Régis Houssin, Juanjo Menent, Cyrille De Lambert, Philippe Grand). All of them works on project since now between 5 (minimum) and 10 years (maximum). Also all the mentors had to be volunteers.

What is your plan for dealing with disappearing students?*

The first thing will probably to avoid this by providing them a real interest to work for project (no hidden information, statistics, ...). Also we will try to avoid this by selecting correctly the student: if we do not see enough motivation among the candidate, we will probably not accept the couple student/idea at all. And if it happens, we will try to exchange again and again to try to restore communication and convince him to go back on project. Then, we will ask him to commit any code or documentation he produces at a regular frequency (to avoid loosing all the work) if disappearing is definitive. The mentor is already ready to try to use all works that is possible to restore. This is also a way for us to follow its work frequently and providing him frequent feedbacks/advices or directives, hoping this will show him he is not alone.

What is your plan for dealing with disappearing mentors?*

The template for ideas include a field "Backup of mentor" (for ideau where two mentors are already found). The Dolibarr foundation, for any validated idea/students will find the backup mentor before starting. The backup mentor will replace the mentor if the main mentor disappears.

What steps will you take to encourage students to interact with your project's community before, during and after the program?

We have a tutorial on our developer wiki site (wiki.dolibarr.org) to provide most possible information to help the student to understand how we works. This should help him to find any contacts and way to contacts. Also we also describe how to use tools to take in touch with team. This does not encourage him but avoid him to be discouraged. To encourage him, we have decided to define only major, influent and also very experienced developers. We will try to convince him, he has a lot of thing to learn by working with such mentors. We will also select student to be sure he is opened to criticism and curious as this is the best way to find people that naturally ask help.

Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here

New organization

Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.

As we apply for the first time, we don't think this is a good thing for the moment, even if we are a large organization.