Google Summer of Code Informations: Difference between revisions

Google Summer of Code Informations (view source)

Revision as of 20:42, 1 March 2012

2,551 bytes removed , 14 years ago

no edit summary

VisualWikitext

Eldy

Bureaucrats, Interface administrators, Administrators

31,029

edits

@@ Line 2: / Line 2: @@
 {{Template:SoC2011}}
-== SoC Information ==
+= SoC Information =
 This is the info that we submit to google as Application in Summer of Code.
 The submitter automatically becomes primary Admin. Most entries are mandatory and have to be filled out before the application can be submitted.
@@ Line 9: / Line 9: @@
 For this we must create an account with form: http://www.google-melange.com/gsoc/profile/google/gsoc2012
-The link_id is visible on "My profile" screen. Submition was made with link_id: eldy10 and xxx
+The link_id is visible on "My profile" screen. Submition was made with link_id: '''eldy10''' and '''regishoussin'''
-==== Organization Id: ====
+=== Organization Id: ===
 dolibarr
-==== Organization Name: ====
+=== Organization Name: ===
 Dolibarr
-==== Description: ====
+=== 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: ====
+=== Home page: ===
 http://www.dolibarr.org/
-==== Main Organization License: ====
+=== Main Organization License: ===
 GNU General Public License version 2.0 (GPLv2) [Dropdown box answer!]
-==== Backup admin ====
+=== Backup admin ===
-xxx
+regishoussin
-==== What is URL of admin page ====
+=== 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 ====
+=== What is the main IRC channel for your organization ===
 irc://freenode.net:6667/dolibarr
-==== What is the main development mailing list ====
+=== What is the main development mailing list ===
 https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
-==== Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? ====
+=== Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? ===
-Most of our developers have particular areas of interest in which they work. Though they are efficient in their areas, there are other, presently uncovered, areas of the code with a need for improvements but a high barrier to entry for casual contributors.
+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.
-Our previous SoC experience shows that a motivated, full-time, student can be brought up to date in any area fairly quickly.
+=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
+No
-By bringing new people in and allowing them to be actively responsible for an area of code, we hope to kickstart some areas of the project that are currently lagging behind.
+=== 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
-Moreover, our previous experiences has shown us that SoC developers tend to stay after the end of the Summer of Code and become valuable members of our community. This has been a win in all directions and we want it to happen again.
-==== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ====
-results:
-Wesnoth participated in GSoC 2008 with four students. Out of these, two were great successes (that is they became full-fledge developers before the actual start of GSoC), did huge improvement during GSoC (A new recruitment algorithm for the AI and the basic structure for a new map editor, the student finished this work after the summer), and are still active developers in the Wesnoth community.
-Of the two other, one of them was very active for the first half of GSoC and provided some useful infrastructure for AI development that we used as base in GSoC 2009, but was much less active and didn't reach expectations for the second half of GSoC. The lesson we learned is that great students should be left on their own, that's the best way to have them work, but average students should be monitored much more closely than we did. If things seems to start to go wrong, it's important to react very quick, to meet with other mentors and get things back on track early.
-Timezone problems were also a serious barrier for student/mentor communication, and we will take that more into account when pairing mentors and students
-For our other students, multiple problems collectively led to failure
+=== Does your organization have an application template you would like to see students use? If so, please provide it now.* ===
-* We should enforce IRC communication, E-mail is a barrier. This applies both for students and mentors. Both should be on IRC several hours a day, with overlapping hours.
+Information for template for ideas is described on page: http://wiki.dolibarr.org/index.php/Google_Summer_of_Code_Ideas_2012
-* We should be more strict about mid-term evaluation. If the student is slightly lacking at mid-term we should give a clear message that he needs to get back on track.
+=== 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 amount and activity on project. This means
+mentors are the major contributors of project.
-results:
+=== What is your plan for dealing with disappearing students?* ===
-In 2009 we mentored 6 students as part of Summer of Code. Out of these 5 projects were a success. From those 5 developers 3 are still part of our core development group and still maintain and improve the work they submitted as part of Summer of Code. One of the students even became the "head" of our AI development department and wants to mentor a student this year. For a summary of the 2009 results have a look at [1].
+The first way, will be by selecting correctly the student: if we do not see any motivation among the candidate, we will probably not accept the idea at all.
+Then, 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.
-Sadly one student was not able to continue his work past midterm due to his computer failing completely as well as personal problems that we won't delve into further here. It was not a salvageable situation.
+=== 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.
-==== If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.====
-(empty)
-===== Add a Comment (optional): =====
-(empty)
-==== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? ====
-No
-==== What is the URL for your ideas page?====
-http://wiki.dolibarr.org/index.php/SummerOfCodeIdeas
-==== What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use. ====
-The main development mailing list is "dolibarr-dev@nongnu.org".
-Our main means of communications is this mailing-list. If you have questions you should ask them in #wesnoth-dev on irc.freenode.net and wait for a reply (might take some hours!).
-==== What is the main IRC channel for your organization? ====
-(empty)
-===== Add a Comment (optional): =====
-If you have questions you should ask them in #wesnoth-dev on irc.freenode.net and wait for a reply (might take some hours!). The Wesnoth related channels are logged in public and the logs tend to be read by developers.
-==== Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site. ====
-(empty)
 ==== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible: ====