SoC Information for Google - Revision history

Noy at 19:14, 20 February 2015

2015-02-20T19:14:30Z

Noy: /* SoC Information for Google */

2015-02-20T19:14:07Z

‎SoC Information for Google

Noy: /* If you chose "veteran" in the organization profile dropdown, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. */

2015-02-20T19:09:34Z

‎If you chose "veteran" in the organization profile dropdown, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.

SkeletonCrew: /* Description* */ Updated the information regarding the latest development release

2014-02-08T18:47:18Z

‎Description*: Updated the information regarding the latest development release

SkeletonCrew: /* Description* */ Make the links look sane

2014-02-08T18:16:37Z

‎Description*: Make the links look sane

SkeletonCrew: /* What is your plan for dealing with disappearing mentors?* */ not all mentors have mentored before

2014-02-08T18:08:41Z

‎What is your plan for dealing with disappearing mentors?*: not all mentors have mentored before

Shadowm: /* Description* */ Make my suggested changes from #wesnoth-dev

2014-02-08T12:44:01Z

‎Description*: Make my suggested changes from #wesnoth-dev

Ivanovic: /* Description* */

2014-02-08T12:20:43Z

‎Description*

Ivanovic at 12:18, 8 February 2014

2014-02-08T12:18:34Z

Ivanovic: /* If you chose "veteran" in the organization profile dropdown, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. */

2014-02-08T12:10:23Z

← Older revision		Revision as of 19:14, 20 February 2015
Line 1:		Line 1:
−	{{Template:~~SoC2014~~}}	+	{{Template:SoC2015}}

	== SoC Information for Google ==		== SoC Information for Google ==

@@ Line 2: / Line 2: @@
 == SoC Information for Google ==
-This is the information that we submit to google as Application in Summer of Code (current status: 2014). The submitter automatically becomes primary Admin. Most entries are mandatory and have to be filled out before the application can be submitted.
+This is the information that we submit to google as Application in Summer of Code (current status: 2015). The submitter automatically becomes primary Admin. Most entries are mandatory and have to be filled out before the application can be submitted.
 === First page of questions ===
@@ Line 78: / Line 78: @@
 ==== Backup administrator* ====
-neuhausercova
+Ivanovic
 ==== Checkboxes ====

@@ Line 157: / Line 157: @@
 [left empty]
-==== If you chose "veteran" in the organization profile dropdown, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. ====
+Since 2008 we have participated in 5 years of GSOC, with good results. With the exception of our first year, we pass approximately 75% of our students, and usually get some really interesting code from them.
 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:
-* 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.
+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.
-* 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.
+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.
 results: 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 mentored a student this year. For a summary of the 2009 results have a look at [1].
-results:
+results: In 2010 we mentored 4 students as part of Summer of Code, all the projects were a success. from those 4 developers, 1 is still part of our code development team and maintains the work he has done as part of Summer of Code.
-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 mentored a student this year. For a summary of the 2009 results have a look at [1].
+results: In 2011 we mentored 5 students, with four of those successfully completed their projects. Some continued the work polishing their projects a little further even after GSoC, one continues to actively polish his work and just released a new version of his WML Editor.
 results: In 2012 we mentored five students with four of them completing their project successfully. Most were from a set list of ideas provided by the project, which were aimed at fixing or updating parts of the code that never seemed to get fixed.
-results:
+results: In 2013 we mentored three students, all of them completing their project successfully. The projects centered around unification of singleplayer and multiplayer content, work on recreating the add-on server as well as improvements for our AI to ensure units are recruited smartly.
-In 2010 we mentored 4 students as part of Summer of Code, all the projects were a success. from those 4 developers, 1 is still part of our code development team and maintains the work he has done as part of Summer of Code.
+results: We had three passes, which included a very difficult improvement of AI programming, and moderately difficult SDL2 transition and unifying single and multiplayer code paths. Our failures was a sprite sheet programming and improving the user made content daemon. These two failures showed similar difficulties, where the deliverables were not met according to deadlines, despite very good initial discussions.
 [1] http://forums.wesnoth.org/viewtopic.php?f=5&t=26955
-: 2/4
+: 2/4 2009: 5/6 2010: 4/4 2011: 4/5 2012: 4/5 2013: 3/3 2015: 3/5
 ==== If you are a new organization, have you applied in the past? If so, for what year(s)? ====

@@ Line 16: / Line 16: @@
 <p><em>Battle for Wesnoth</em>, or simply <em>Wesnoth</em>, is a Free, turn-based strategy game with a high-fantasy theme that was designed in June 2003 by David White (Sirp).</p>
 <p>Although the core rules are fairly simple and meant to be easily learned[1], they provide interesting gameplay and rich tactical options. A major strength of the project is the Wesnoth Markup Language (WML) for writing scenarios. Programming skills are not required to compose with it, and a large WML-modding community has generated a vast amount of user-maintained content. We polish the best of this content and lift it into our official release tree.</p>
-<p>The first stable release (1.0) was on October 2, 2005, and the latest stable release (1.10.7) happened in August 2013. Version 1.10 was released in January 2012, while the current development branch is at version 1.11.8, released at the beginning of January 2014. We are currently working towards another stable release which should be out in Q2 2014.</p>
+<p>The first stable release (1.0) was on October 2, 2005, and the latest stable release (1.10.7) happened in August 2013. Version 1.10 was released in January 2012, while the current development branch is at version 1.11.9, released at the beginning of February 2014. We are currently working towards another stable release which should be out in Q2 2014.</p>
 <p><em>Wesnoth</em> is one of the most successful open-source game projects in existence, with an exceptionally large developer base and user community:
 <ul>

@@ Line 35: / Line 35: @@
 </ul></p>
 <p>For our Ideas page, please have a look at [4]. There you can find all information required to get you started working on Wesnoth.</p>
-<p>[1] <a href="http://www.wesnoth.org/wiki/WesnothPhilosophy">http://www.wesnoth.org/wiki/WesnothPhilosophy</a><br />
+<p>[1] http://www.wesnoth.org/wiki/WesnothPhilosophy<br />
-[2] <a href="http://www.linuxquestions.org/questions/linux-news-59/2009-linuxquestions.org-members-choice-award-winners-788028/">http://www.linuxquestions.org/questions/linux-news-59/2009-linuxquestions.org-members-choice-award-winners-788028/</a><br />
+[2] http://www.linuxquestions.org/questions/linux-news-59/2009-linuxquestions.org-members-choice-award-winners-788028/<br />
-[3] <a href="http://www.linuxquestions.org/questions/2010-linuxquestions-org-members-choice-awards-93/open-source-game-of-the-year-855937/">http://www.linuxquestions.org/questions/2010-linuxquestions-org-members-choice-awards-93/open-source-game-of-the-year-855937/</a><br />
+[3] http://www.linuxquestions.org/questions/2010-linuxquestions-org-members-choice-awards-93/open-source-game-of-the-year-855937/<br />
-[4] <a href="http://wiki.wesnoth.org/SummerOfCodeIdeas">http://wiki.wesnoth.org/SummerOfCodeIdeas</a></p>
+[4] http://wiki.wesnoth.org/SummerOfCodeIdeas</p>
 </code>

@@ Line 126: / Line 126: @@
 ==== What is your plan for dealing with disappearing mentors?* ====
-All our mentors are long time developers that volunteered for the job, so we don't expect that to happen. We observed in during the last years the amount of time required to mentor, and our mentors accepted the job knowing the amount of work it involved. All of this years mentors mentored last year as well, most have contributed since 2008, or been organizational admins.
+Most of our mentors are long time developers that volunteered for the job, so we don't expect that to happen. We observed in during the last years the amount of time required to mentor, and our mentors accepted the job knowing the amount of work it involved. Most of this years mentors mentored last year as well, most have contributed since 2008, or been organizational admins.
 However, should it happen, we would continue to mentor as a developer community the student until we find a new "official" mentor to take on the job.

@@ Line 14: / Line 14: @@
 ==== Description* ====
 <code type="html">
-<p><em>Battle for Wesnoth</em>, or simply <em>Wesnoth</em>, is a free, turn-based strategy game with role-playing elements that was designed in June 2003 by David White (Sirp).</p>
+<p><em>Battle for Wesnoth</em>, or simply <em>Wesnoth</em>, is a Free, turn-based strategy game with a high-fantasy theme that was designed in June 2003 by David White (Sirp).</p>
-<p>Although the core rules are fairly simple and meant to be easily learned[1], they provide interesting gameplay and rich tactical options. A major strength of the project is the Wesnoth Markup Language (WML) for writing scenarios. Programming skills are not required to compose with it, and a large WML-modding community has generated a great deal of user-maintained content. We polish the best of this content and lift it into our official release tree.</p>
+<p>Although the core rules are fairly simple and meant to be easily learned[1], they provide interesting gameplay and rich tactical options. A major strength of the project is the Wesnoth Markup Language (WML) for writing scenarios. Programming skills are not required to compose with it, and a large WML-modding community has generated a vast amount of user-maintained content. We polish the best of this content and lift it into our official release tree.</p>
-<p>The first stable release (1.0) was on October 2, 2005, and the latest stable release (1.10.7) happened in August 2013. Version 1.10 was released in January 2012,  while the current development branch is 1.11.8 that was released at the beginning of January. We are currently working towards another stable release which should be out in Q2 2014.</p>
+<p>The first stable release (1.0) was on October 2, 2005, and the latest stable release (1.10.7) happened in August 2013. Version 1.10 was released in January 2012, while the current development branch is at version 1.11.8, released at the beginning of January 2014. We are currently working towards another stable release which should be out in Q2 2014.</p>
 <p><em>Wesnoth</em> is one of the most successful open-source game projects in existence, with an exceptionally large developer base and user community:
 <ul>

@@ Line 31: / Line 31: @@
 <li>Well&shy;-balanced by a tireless team of playtesters</li>
 <li>Fun, unique gameplay</li>
-<li>Even after nearly a decade of development and a very solid, fun product already created, there are still plenty of new developers</li>
+<li>Even after a decade of development and a very solid, fun product already created, there are still plenty of new developers</li>
 <li>Strong support of internationalization with many supported languages, thus experience in working with non-native English speakers. In fact, more than half of our developers are not native English speakers.</li>
 </ul></p>

@@ Line 48: / Line 48: @@
 ==== Logo URL ====
-[left empty]
+https://raw.github.com/wesnoth/wesnoth-old/master/icons/wesnoth-icon.png
 ==== Ideas list* ====