Wiki source code of Organization Application Form

Last modified by Eduard Moraru on 2020/01/27 13:55

Show last authors
1 {{info}}
2 This document is to be updated each year with the information asked by Google. If some sections are no longer asked, they should be kept commented at the end of the page.
3 {{/info}}
4
5 {{toc/}}
6
7 = Latest =
8
9 == Why does your org want to participate in Google Summer of Code? ==
10
11 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.
12
13 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.
14
15 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.
16
17 == How many potential mentors have agreed to mentor this year? ==
18
19 1-5
20
21 == How will you keep mentors engaged with their students? ==
22
23 Our mentors are key members of the community which also have experience in mentoring students (from previous editions).
24
25 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 forum and IRC/Matrix 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.
26
27 == How will you help your students stay on schedule to complete their projects? ==
28
29 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.
30
31 To reduce the risk we will ask the student to regularly give updates and to discuss about their work on the forum. We will also require that the student commits their progress at least once a week. This way they can easily get code reviews and make sure they are going in the right direction.
32
33 If we feel the progress is not good, we will discuss with the student on how they can adjust their approach and even their targets, but also acknowledge that in some cases failing the student may be needed.
34
35 == How will you get your students involved in your community during GSoC? ==
36
37 Our IRC/matrix channel and forum 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.
38
39 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 they 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.
40 We believe that this intensive interaction with the community is likely to increase the student's motivation to stick with the project.
41
42 == How will you keep students involved with your community after GSoC? ==
43
44 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.
45
46 == Has your org been accepted as a mentoring org in Google Summer of Code before? ==
47
48 Yes
49
50 == Which years did your org participate in GSoC? ==
51
52 2019
53 2018
54 2017
55 2016
56 2013
57 2012
58 2011
59 2009
60 2008
61 2007
62 2006
63 2005
64
65 == For each year your organization has participated, provide the counts of successful and total students. (e.g. 2016: 3/4) ==
66
67 2019: 3/4
68 2018: 3/3
69 2017: 2/4
70 2016: 0/1
71 2013: 0/1
72 2012: 3/3
73 2011: 3/3
74 2009: 4/6
75 2008: 8/10
76 2007: 5/6
77 2006: 4/5
78 2005: 6/7
79
80 == Is there an organization new to GSoC that you would like to refer to the program for 2020? Feel free to add a few words about why they'd be a good fit. ==
81
82 == If your org has applied for GSoC before but not been accepted, select the years: ==
83
84 2015
85 2014
86 2010
87
88 == 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) ==
89
90 == What year was your project started? ==
91
92 2003
93
94 == Where does your source code live? Please provide URLs that point to repositories, GitHub organizations, or a web page that describes how to get your source code. ==
95
96 [[http:~~/~~/dev.xwiki.org/xwiki/bin/view/Community/SourceRepository>>doc:Community.SourceRepository]]
97
98 = Is your organization part of any government? This will not affect your selection into the program. However, as stated in the Program Rules, we can not issue org stipends to orgs that are part of any government. This includes public universities, government research institutions, etc.. =
99
100 No
101
102 == Anything else we should know (optional) ==
103
104 = From previous years =
105
106 == If you are a new organization, have you applied in the past? If so, for what year(s)? ==
107
108 N/A
109
110 == If you chose "veteran" in the dropdown above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. (was: Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.) ==
111
112 We have been accepted in 8 out of 10 editions of GSoC so far. Every Summer of Code has had an amazing impact on XWiki. We learned from the first year in particular to distinguish greedy students versus passionate students. We also learned how students can overestimate their capacities. We also learned the work we need to do to mentor the students. Year by year we feel that we do a better job at introducing the students to high quality development practices and communication in an Open Source project.
113
114 The GSoC projects have created great additions to the XWiki software as well as brought stable contributors to the XWiki projects. Some of the most notable contributions are: a complete makeover of XWiki's UI, standard compliant backend storage for XWiki, a Chart Macro to transform tables to charts, an experimental peer-to-peer library allowing to replicate wikis, Google Docs integration, a better testing framework, and others. One SoC 2007 project even evolved into a fully featured XWiki product, namely the XEclipse offline editor of wiki pages, which was continued along successive GSoC editions in the following years. 2008 was the year with the largest number of projects and successes. It brought 3 permanent contributors, and all the projects that have passed the final evaluation have been successfully integrated: syntax highlighting and code completion for XEclipse, Open Office integration providing import for office documents and a much better copy/paste support in our WYSIWYG editor than what any other editor offers, WebDAV and REST access to the wiki, a better user experience in XWiki Watch, SSO through OpenID. GSoC 2009 was an occasion for fresh ideas, bringing new features to some of our existing projects (XEclipse and XOffice), and laying the foundation for some exciting and rather complex new ones: XOO - an OpenOffice Plugin for editing Wiki pages, OpenSocial integration with XWiki, Wiki Import Module, which started out very promising. In particular, the work done on the OpenSocial integration project was the starting point for XWiki 3.0's new Dashboard. GSoC 2011 branched out towards the Android platform with a comprehensive library which allows Android applications to communicate with a remote XWiki instance, revitalized XEclipse with the "RESTification" project and brought it up to date with XWiki's latest features, and prototyped an auto completion feature which speeds up content editing. GSOC 2012 brought improvements to the Android connector, and laid the grounds for a new mobile-friendly skin based on "Foundation", and a new search engine using Solr (which ended up replacing XWiki's default search engine!).
115
116 GSoC 2011 was the our first year with a 100% success ratio, a goal achieved in 2012 as well, but not all our previous GSoC experiences were the same. Even though the students we have chosen showed enthusiasm and willingness, some are not, in the end, capable to produce code that can be integrable in our code base. However, for those students who make efforts to do a good job until the end, event the failure is not a complete failure, as they still earn experience, expand their knowledge and improve their communication skills.
117
118 {{velocity}}
119 #*
120 Basically, we believe that enthusiastic students that register for the experience deserve to be accepted and participate more than skilled students who register for the money, and consider the Summer of Code not a challenge, but a 'sure thing'. Thus, we prefer to give the young and inexperienced one a chance, even knowing they might fail, since, in our opinion, the summer of code is also an educational process.
121 *#
122 {{/velocity}}
123
124 Our pass/fail ratios are:
125 2005: 6/7
126 2006: 4/5
127 2007: 5/6
128 2008: 8/10
129 2009: 4/6
130 2011: 3/3
131 2012: 3/3
132 2013: 0/1
133
134 == Why does your org want to participate in Google Summer of Code? (Was pre 2016: Why is your organization applying to participate? What do you hope to gain by participating?) ==
135
136 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.
137
138 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.
139
140 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.
141
142 == How many potential mentors do you have for this year's program? What criteria did you use to select your mentors for this year's program? ==
143
144 From our community, we have 4 people willing to mentor students this year.
145
146 The selection criteria we used were:
147
148 * Desire to be a mentor
149 * Knowledge of the code base and development best practices
150 * Availability to mentor the students
151 * General view of the XWiki goals and roadmap
152 * Mentoring skills and past experience in mentoring people and especially GSoC students
153 * Tolerant but firm in what they expect
154
155 == What is your plan for dealing with disappearing students? ==
156
157 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.
158
159 To reduce the risk we will ask the student to stay in Instant Messaging contact with his mentor in order to give regular updates, and to regularly discuss their work on the main mailing list. We will also ask the student to quickly show results (code, specifications) to be able to judge his understanding.
160
161 If we feel this isn't done we are able to invalidate the student at the mid-term evaluation, or, in extreme cases, even before the end of the bonding period.
162
163 == What is your plan for dealing with disappearing mentors? ==
164
165 We expect that this will not happen since our mentor are active people in the community and wouldn't volunteer if they didn't feel they could. In any case, we are able to activate one of our backup mentors. 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.
166
167 == What steps will you take to encourage students to interact with your project's community before, during and after the program? ==
168
169 Outside GSoC we're always maintaining a friendly community on our mailing lists, gently encouraging people to contribute.
170
171 {{velocity}}
172 #*
173 Before the project we have prepared a questionnaire for students so that our community can participate in selecting the students. We plan to pre-screen the proposal and then ask our community for selecting the ordering of projects that will lead to the selection of the most interesting projects. We will also have the tentative mentor for a project talk with the candidate to feel the motivation of the student.
174 *#
175 {{/velocity}}
176
177 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.
178
179 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.
180 We believe that this intensive interaction with the community is likely to increase the student's motivation to stick with the project.
181
182 {{velocity}}
183 #*
184 We will of course keep an open line with the student, propose module ownership. We also have thought of proposing bounties from project sponsors to continue working on enhancements to the projects. During the previous editions we noticed that projects that get integrated in the trunk early tend to increase the students' desire to continue maintaining the code.
185 *#
186 {{/velocity}}
187
188 After the project we will, of course, invite the student to continue work in our community if the project was successful.
189
190 == What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?* ==
191
192 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. Finally, the main company which sponsors the development of XWiki may consider funding the students' subsequent contributions, or even make job offers to graduates.
193
194 == Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ==
195
196 N/A
197
198 == 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. ==
199
200 N/A
201
202 == Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application? ==
203
204 N/A
205
206 == What is your success/fail rate per year? ==
207
208 2018: 3/0
209 2017: 2/2
210 2016: 0/1
211 2013: 0/1
212 2012: 3/0
213 2011: 3/0
214 2009: 4/2
215 2008: 8/2
216 2007: 5/1
217 2006: 4/1
218 2005: 6/1
219
220 == Are you part of a foundation/umbrella organization? ==
221
222 No
223
224 {{comment}}
225 #* No longer asked, but maybe useful in the future:
226
227 == If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? ==
228
229 N/A
230
231 == Does your organization have an application template you would like to see students use? If so, please provide it now. ==
232
233 [[http:~~/~~/dev.xwiki.org/xwiki/bin/GoogleSummerOfCode/student+application+form>>doc:GoogleSummerOfCode.student application form]]
234
235 == If accepted, would this be your first year participating in GSoC? ==
236
237 No
238
239 == 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. ==
240
241 2005: 6/7
242 2006: 4/5
243 2007: 5/6
244 2008: 8/10
245 2009: 4/6
246 2011: 3/3
247 2012: 3/3
248 2013: 0/1
249
250 == How many of your organization's Google Summer of Code students remained active with the project for at least 1 year after Google Summer of Code ended? ==
251
252 If unsure, please estimate to the best of your ability
253 Artem
254 Catalin
255 Evelina
256 Asiri
257 Sergiu
258 Marta
259 Ecaterina
260 Eduard
261 Ana Maria
262 - as of February 2013: 9
263
264 == How many of your organization's past Google Summer of Code students have become project committers? ==
265
266 If unsure, please estimate to the best of your ability
267 Artem
268 Catalin
269 Asiri
270 Sergiu
271 Marta
272 Ecaterina
273 Eduard
274 Jun Han (xeclipse)
275 - as of February 2013: 8
276
277 == How many of your organization's past Google Summer of Code Students have become Mentors or Org Admins? ==
278
279 If unsure, please estimate to the best of your ability
280 Asiri
281 Sergiu
282 Marta
283 Ecaterina
284 Eduard
285 - as of February 2013: 5
286
287 *#
288 {{/comment}}

Get Connected