-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Followup of the GCI post. If you know of a task that you would also be willing to mentor, please tell noy about it so that he can add it in. Cheers, Nils Kneuper aka Ivanovic
- -------- Original-Nachricht -------- Betreff: Re: Wesnoth in Google Code-In (GCI) Datum: Sun, 4 Nov 2012 18:26:20 -0800 Von: Arc Riley <[email protected]> An: Nils Kneuper <[email protected]> http://gci.copyleftgames.org/templates/tasks/pysoy.xml If you could provide a few (at least 2-3) tasks in the above format I can get them into the site. I'm building it out at http://gci.copyleftgames.org/ I can also give you and other mentors vcs push access which updates the site in realtime. It uses xslt on a hg hook to regenerate on each push. On Sat, Oct 27, 2012 at 5:38 AM, Nils Kneuper <[email protected] <mailto:[email protected]>> wrote: Hi everybody! During this years GSoC mentor summit the Google Code-In [1] was mentioned, too. This is a program for high school students to get them into helping on open source software. Projects that participated in GSoC can apply as mentor organization for GCI. Regarding their website the tasks can be from the following areas: 1) Code: Tasks related to writing or refactoring code 2) Documentation/Training: Tasks related to creating/editing documents and helping others learn more 3) Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions 4) Quality Assurance: Tasks related to testing and ensuring code is of high quality 5) User Interface: Tasks related to user experience research or user interface design and interaction I discussed this topic with noy and came to the conclusion that we would not be able to provide the required number of tasks and the associated mentoring on our own. Luckily we met with Arc Riley, a mentor from the python foundation who also created the Shavian transliteration for Wesnoth, who said that teaming up for GCI might be a good idea. When teaming up we would not have to provide more than 100 but just a maybe 20 tasks (or less if we can't find this many small chunk tasks). Personally I think this is a good idea and there are directly some tasks which come to my mind would make sense: 1) creation of new screenshots for stable as well as development (one task each) 2) create new UI themes for specific use cases like e.g. a high resolution theme for 1080p and larger 3) create tutorial videos, some kind of "how to play" or "how to create" series which could feature the basics of playing wesnoth, basics of tactics, how to create a simple add-on and upload it, ... 4) work on an updated trailer for the latest stable release The general format for each task should be the following: <li>Title of the task.</li> <li>Description, for markup use HTML.</li> <li>Time to complete in hours, as integer.</li> <li>Link ID's of mentors for this task, comma separated.</li> <li>Task types, one or more of the allowed types <i>({{ types }})</i>, comma separated.</li> <li>Task tags, any custom tags you want to add, comma separated.</li> What do you think? Should we go for this and do you have some ideas for tasks? Yes, the acceptance criteria per task should be detailed and understandable even if the students don't talk to us via IRC (this might happen for some of them!). Cheers, Nils Kneuper aka Ivanovic [1] http://code.google.com/gci/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlCXXzIACgkQfFda9thizwWYuwCghfGqOMLzL8zWYz3+eC1642Vc JH0AoIpOlXr/5l9YXTXDrjxy8SWGquxE =Q8Ne -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
