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

<
From version < 6.2 >
edited by Ecaterina Moraru (Valica)
on 2014/02/13 20:37
To version < 6.3 >
edited by Ecaterina Moraru (Valica)
on 2014/02/13 20:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -90,29 +90,8 @@
90 90  Step 2
91 91  {{/warning}}
92 92  
93 -== 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.) ==
94 94  
95 -We have been accepted in 7 out of 8 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.
96 96  
97 -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 continues to be a star of GSoC almost every year. 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. Finally, 2012 brought improvements to the Android connector, and laid the foundation for a new mobile-friendly skin based on "Foundation", and a new search engine using Solr.
98 -
99 -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, the failure is not a complete failure, as they still earn experience, expand their knowledge and improve their communication skills.
100 -
101 -{{velocity}}
102 -#*
103 -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.
104 -*#
105 -{{/velocity}}
106 -
107 -Our pass/fail ratios are:
108 -2005: 6/7
109 -2006: 4/5
110 -2007: 5/6
111 -2008: 8/10
112 -2009: 4/6
113 -2011: 3/3
114 -2012: 3/3
115 -
116 116  == Why is your organization applying to participate? What do you hope to gain by participating? ==
117 117  
118 118  Each year, SoC has been a great help for our projects, by providing not just a few developers during the summer, but also by increasing the number of permanent contributors.
... ... @@ -127,9 +127,11 @@
127 127  *#
128 128  {{/velocity}}
129 129  
109 +== 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? ==
130 130  
131 -== What criteria did you use to select your mentors for this year's program? Please be as specific as possible ==
111 +From our community we have 5 willing people to mentor students this year.
132 132  
113 +Criteria:
133 133  * Desire to be a mentor
134 134  * Knowledge of the code base and development best practices
135 135  * Availability to mentor the students
... ... @@ -252,3 +252,26 @@
252 252  N/A
253 253  *#
254 254  {{/velocity}}
236 +
237 +== 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.) ==
238 +
239 +We have been accepted in 7 out of 8 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.
240 +
241 +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 continues to be a star of GSoC almost every year. 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. Finally, 2012 brought improvements to the Android connector, and laid the foundation for a new mobile-friendly skin based on "Foundation", and a new search engine using Solr.
242 +
243 +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, the failure is not a complete failure, as they still earn experience, expand their knowledge and improve their communication skills.
244 +
245 +{{velocity}}
246 +#*
247 +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.
248 +*#
249 +{{/velocity}}
250 +
251 +Our pass/fail ratios are:
252 +2005: 6/7
253 +2006: 4/5
254 +2007: 5/6
255 +2008: 8/10
256 +2009: 4/6
257 +2011: 3/3
258 +2012: 3/3

Get Connected