Fwd: Google Code-in tasks needed
Google Code-In is on the horizon again (see forwarded mail)! We had some tasks in last year's program, and for a teenager program, we got some pretty interesting results! Does anyone have any ideas for tasks? The tasks can be of the type - code - doc - research - QA - user interface They should be really small ("a task should take a normal KDE contributor about 2 hours"), but larger tasks can be split into several smaller ones which are likely to be taken by the same person anyway, so this should not be the problem. I think especially the non-coding categories can be interesting for us, since we don't have much personnel for that. E.g. QA would be very helpful (we can e.g. have participants spend a day putting a certain application through its paces), documentation could be helpful as well (maybe Sascha could mentor some tasks for an English version of the handbook?). I may put in some research tasks for small user tests. Anyone willing to create and mentor a task for Code-In? It's a few days of relatively intensive mentoring for each task. Cheers, Thomas Original Message Heya folks :) Sorry for mass-mailing but this concerns pretty much everyone. Google Code-in applications have started. I just submitted our application. To be successful we now need to add tasks to this list: http://community.kde.org/GoogleCodeIn/2012/Ideas Please only add tasks you are willing to mentor (or if you know someone else is)! A few things to keep in mind: * this is not just about code. We also need other tasks (likely even more than coding tasks) * we need at least 5 tasks in each category * a task should take a normal KDE contributor about 2 hours (This is to give you some idea of how much work a task should be. If you have doubts/questions please come to me.) * there are no translation tasks this time * there are no easy/normal/hard tasks - all the same this time * we get to choose 2 grand-price winners among our best kids. This means students are much more likely to stick with one org this time. * the kids don't get money this time * Google expects a turn-around time on tasks of less than 36 hours. I'd like to us try to get to less than 24 hours if at all possible. * check the timeline (http://www.google-melange.com/gci/events/google/gci2012). If you're not available to approve and review tasks for some of that time please add that to the task description We need this list finished latest by November 5th but earlier would be a lot better. Please spread the word to everyone who's not yet aware of it but should be. Cheers and thanks for your help Lydia PS: Please CC me on replies as I am not subscribed to all lists. -- Lydia Pintscher - http://about.me/lydia.pintscher KDE Community Working Group / KDE e.V. board member http://kde.org - http://open-advice.org ___ Kde-soc-mentor mailing list kde-soc-men...@kde.org https://mail.kde.org/mailman/listinfo/kde-soc-mentor ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Fwd: Google Code-in tasks needed
Hello Thomas, Thomas Pfeiffer wrote at Mittwoch, 24. Oktober 2012, 13:13:21: > Google Code-In is on the horizon again (see forwarded mail)! > We had some tasks in last year's program, and for a teenager program, we got > some pretty interesting results! > Does anyone have any ideas for tasks? The tasks can be of the type > - code > - doc > - research > - QA > - user interface > > They should be really small ("a task should take a normal KDE contributor > about 2 hours"), but larger tasks can be split into several smaller ones > which are likely to be taken by the same person anyway, so this should not > be the problem. > > I think especially the non-coding categories can be interesting for us, > since we don't have much personnel for that. E.g. QA would be very helpful > (we can e.g. have participants spend a day putting a certain application > through its paces), documentation could be helpful as well (maybe Sascha > could mentor some tasks for an English version of the handbook?). I may put > in some research tasks for small user tests. > Anyone willing to create and mentor a task for Code-In? It's a few days of > relatively intensive mentoring for each task. I've added the Handbook to the Ideas-Page as proposed. I'll checkin the english stuff this week. So the guys can start proofrading :-) So a english version of the book comes on the horizon too. -- Sincerly yours Sascha Manns Community & Support Agent / Balsam Plasma Active Developer open-slx GmbH Web (business): http://www.open-slx.com Web (private): http://saigkill.homelinux.net open-slx GmbH, GF: Dr. Ing. Stefan Werden , HR: 25786, Ust-ID: DE267619018 Einsteinring 7, 90 453 Nuremberg / Germany ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Fwd: Google Code-in tasks needed
On Tuesday 06 November 2012 07:51:02 Sascha Manns wrote: > Hello Thomas, > > Thomas Pfeiffer wrote at Mittwoch, 24. Oktober 2012, 13:13:21: > > Google Code-In is on the horizon again (see forwarded mail)! > > We had some tasks in last year's program, and for a teenager program, we > > got some pretty interesting results! > > Does anyone have any ideas for tasks? The tasks can be of the type > > - code > > - doc > > - research > > - QA > > - user interface > > > > They should be really small ("a task should take a normal KDE contributor > > about 2 hours"), but larger tasks can be split into several smaller ones > > which are likely to be taken by the same person anyway, so this should not > > be the problem. > > > > I think especially the non-coding categories can be interesting for us, > > since we don't have much personnel for that. E.g. QA would be very helpful > > (we can e.g. have participants spend a day putting a certain application > > through its paces), documentation could be helpful as well (maybe Sascha > > could mentor some tasks for an English version of the handbook?). I may > > put > > in some research tasks for small user tests. > > > > Anyone willing to create and mentor a task for Code-In? It's a few days of > > relatively intensive mentoring for each task. > > I've added the Handbook to the Ideas-Page as proposed. I'll checkin the > english stuff this week. So the guys can start proofrading :-) So a english > version of the book comes on the horizon too. Awesome! I guess proofreading and maybe a little editing is great task and it's helpful to us especially if native Englisch speakers claim the tasks. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active