Last modified by Eduard Moraru on 2022/02/21 15:42

<
From version < 7.7 >
edited by Eduard Moraru
on 2016/02/19 19:14
To version < 7.8 >
edited by Eduard Moraru
on 2016/02/19 20:07
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,6 +8,91 @@
8 8  Profile
9 9  {{/warning}}
10 10  
11 += Latest =
12 +
13 +== Why does your org want to participate in Google Summer of Code? ==
14 +
15 +Every Summer of Code that we have participated so far has had an amazing impact on XWiki. It not only helped our project by providing some much needed manpower and enthusiasm during the summer, but also by increasing the number of long-term contributors.
16 +
17 +GSoC allows us to propose some fun and useful projects around the XWiki platform which are self-containing and which we can hopefully incorporate into XWiki's development branch. In addition, it's also rewarding to acknowledge that we can help students discover Open Source and professional software development practices.
18 +
19 +We had a great time participating in the previous editions, which allowed us to meet great people, both students and other mentors. We hope to discover new talented contributors that share the same faith we have in the wiki concept and want to build on top of it.
20 +
21 +== How many potential mentors have agreed to mentor this year? ==
22 +
23 +1-5
24 +
25 +== How will you keep mentors engaged with their students? ==
26 +
27 +Our mentors are key members of the community which also have experience in mentoring students (from previous editions).
28 +Even more, we don't encourage a private student-mentor relationship. We prefer that students and mentors discuss their projects in the open on our dev mailing list and IRC channel, and we try to get the student to work with the whole community, where the mentor is just the person who knows the most about that project
29 +
30 +== How will you help your students stay on schedule to complete their projects? ==
31 +
32 +We plan to screen students based on their available time and technical capability to achieve the goal. Our past experience with Summer of Code projects is that students must not be overloaded with other work to be able to focus on the Summer of Code project. In our previous projects we had two disappearing student who had overestimated their capabilities and available time. We believe we have learned from that and the first thing we check is if the student *can* finish his project on time.
33 +
34 +To reduce the risk we will ask the student to give regularly give updates and to discuss about their work on the main mailing list. We will also require that the student commits his progress at least once a week. This way he can easily get code reviews and make sure he is going in the right direction.
35 +
36 +If we feel the progress is not good, we will discuss with the student on how he can adjust his approach and even his targets, but also acknowledge that in some cases failing the student may be needed.
37 +
38 +== How will you get your students involved in your community during GSoC? ==
39 +
40 +Our IRC channel and mailing lists are very active, and at almost any time of the day and night there's a dev available to talk to interested students (people in general). The community is very responsive and patient with new people who are in need of some help, or simply curious and willing to learn something new.
41 +
42 +During the project we will ask the student to participate in the developers mailing list to explain what they are working on and will try to have as much communication as possible done in public so that our community knows what is happening. If the student interacts with the core he will be trained by the community to comply with the community rules. We're trying to make the students develop code that can be integrated on the spot, and not some sandboxed projects that might one day be used or not.
43 +We believe that this intensive interaction with the community is likely to increase the student's motivation to stick with the project.
44 +
45 +== How will you keep students involved with your community after GSoC? ==
46 +
47 +Successful students will be granted committership on the module(s) they have come to master during their GSoC experience. Committership means both power and responsibility, and from our prior experience it strongly motivates students to remain involved. Also, we will make sure that successful GSoC work gets integrated and made available to the community, where both devs and users can express their interest in using and extending it, can provide informed feedback and raise questions. Knowledge that their project is being used and appreciated will boost the student's confidence, and such interactions with an interested community are likely to trigger not only the student's involvement in discussions, but also further contributions in response to the community's feedback. Of course, we will continue to guide the student through all this as needed.
48 +
49 +== Has your org been accepted as a mentoring org in Google Summer of Code before? ==
50 +
51 +Yes
52 +
53 +== Which years did your org participate in GSoC? ==
54 +
55 +2013
56 +2012
57 +2011
58 +2009
59 +2008
60 +2007
61 +2006
62 +2005
63 +
64 +== What is your success/fail rate per year? ==
65 +
66 +2005: 6/1
67 +2006: 4/1
68 +2007: 5/1
69 +2008: 8/2
70 +2009: 4/2
71 +2011: 3/0
72 +2012: 3/0
73 +2013: 0/1
74 +
75 +== If your org has applied for GSoC before but not been accepted, select the years: ==
76 +
77 +2015
78 +2014
79 +2010
80 +
81 +== If you are a new organization to GSoC, is there a Google employee or previously participating organization who will vouch for you? If so, please enter their name, contact email, and relationship to your organization. (optional) ==
82 +
83 +== Are you part of a foundation/umbrella organization? ==
84 +
85 +No
86 +
87 +== What year was your project started? ==
88 +
89 +2003
90 +
91 +== Anything else we should know (optional) ==
92 +
93 +
94 += From previous years =
95 +
11 11  == Organization ID ==
12 12  
13 13  xwiki

Get Connected