The release is getting really close so it’s about time we have some parties 🙂
We’ll have a get-together at Vogelbräu in Karlsruhe next Saturday at 18:00. Let me know if you want to come and meet cool people.
If you are not anywhere near Karlsruhe you can check the wiki to see if there is a party near you. No party near you? Organize one!
This is a guest post from one of our Google Code-in students. Enjoy and watch the video! 🙂
Hello everyone! My name is Claudio Desideri (snizzo) and since the 22nd of November I took part in Google Code-in 2010. I did 6 tasks and worked only with the KDE Community, with promo people in particular. It was kind of a surprise for me to work with videos and multimedia because I’m a quite skilled php coder and so my original idea was to help kde-www. Unfortunately www tasks weren’t available at the time the contest started so I claimed one for a Konqueror screencast. While working on that I felt inspired and for the next task I chose one called “KDE Ad”.
In that particular moment I got the real point of Google Code-in. I decided not to take care of points and timing but I focused only on my work. That decision leads me to spend about 3 weeks just to realize an ad video for KDE in general with my mentor’s help. Then I really started talking with the KDE community and I got in touch with everyone for opinions on my work and I tried to improve myself through that. I’m writing this as my last task too and have to thanks really all the KDE community for what it gave me.
Actually I found any member very helpful and nice with me also when I became a little too pedantic. I did things I’ve never done before, I met very nice peope (especially one girl) during this and I really enjoyed myself. I also undestood the real meaning of “open source project” and gained experience in team work.
Also the main thing I learnt here is: when there is a problem, maybe YOU could fix it, and anyway you’re not alone doing it. And from now, I’ll never leave this community and will work again for KDE because it has been the most amazing experience I’ve ever had in my entire life.
For the last 1,5 months I’ve been herding cats for Google Code-in as the KDE admin. For those who are unfamiliar with Code-in: It’s a contest for 13 to 18 year olds to get involved in free software projects, one of them KDE. Today Code-in ended and the students (and mentors and me!) can get some rest 😉 And for me it’s time to write a wrap-up.
Boy, did the students rock! 300 closed tasks was my personal goal and in the end 338 where closed for KDE. Among them things like handbook writing for Amarok, bug triage for KHTML, coding on Marble, Rekonq and others, doing cool video clips for promo and edu and much much more. You might already have seen some of the work on PlanetKDE and more posts will follow. It’s been an amazing ride.
Let me write a bit about KDE’s experience. I’ve asked the mentors to tell me what they liked and didn’t like about the contest. First of all nearly everyone agreed that this is a really cool program. I don’t think we’ve had one before where we got so much done in such a short time with such a largely high-quality output. It’s a great opportunity for students to get to know high-profile free software projects with clear tasks for them to work on. It is great to see how some of the students gain confidence with each task they do and are proud of what they achieved. For me personally the hardest part was having to tell some students that their work wasn’t good enough yet – that they should push themselves a bit more (which they always could). Code-in being a contest encourages students to rush. This is great because it gets so much done but it needs mentors to keep an eye on quality with some students. That being said I was thrilled to see the first very good patch come in only a few hours after the contest had opened.
The other thing that made this a very demanding time for me is the fact that both students and mentors needed an enormous amount of hand-holding with the web app. It’s the same application that is being used for Google Summer of Code and I know it’s quirks and can probably navigate people through it while sleeping by now but new mentors and students had a lot of problems with it and needed help.
For future versions of the contest I’d like to see a few improvements that would make the life of mentors, admin and students a lot easier. Currently a student could only work on one task at a time and needs to wait for his mentor to approve the task before he could claim the next task. Then he has to wait again until the mentor of that next task approves his request and he can start working. This system is very demanding for a contest. It could be improved by allowing students to claim their next task once they have submitted the result of their current task. But as we’ve already learned with GSoC and Season of KDE: mentoring takes time and is demanding – in Code-in doubly so. The other major bottle-neck (which I think/hope I managed pretty well) is the admin. He/she needs to approve every single task the mentors suggest in the web app before students get to see them. This is good to make sure the tasks are ok, are not too easy or too hard and have enough details for the students to start working on them. However it also means that I’ve constantly had mentors and students pinging me to approve tasks. If you don’t have a very attentive admin this is not ideal – given that the contest ran over Christmas this probably happened in a few orgs. Next time I should probably try to get more people for screening tasks.
Oh and one last thing: the naming is a bit unfortunate. I’ve had to explain multiple times that Code-in isn’t actually just about code but also artwork, translations, promotion, testing and much more.
To sum it up Code-in has been an amazingly useful and stressful experience. We’ve gotten a lot of those things done that everyone of us has on their todo list but just doesn’t get around to but that make a huge difference for the project. And of course we gotten an opportunity to introduce a lot of new people to our community. I hope each of them stays around and continues to do awesome.
I’ve been admin for GSoC and SoK (with great help from Leo, Jeff and Ian) for 4 years now and this time also for Code-in. We’ve improved it together with pretty damn amazing mentors and students and I think we’ve reached the point where we can be really proud of our mentoring programs. I’m convinced that they are among the best out there. However I’m also convinced that we can still do better. Two days ago I had a long call with Jos. During that call I realized that we’ve reached a point where I think to make them any better it needs new eyes and fresh ideas. In addition I have the feeling these programs depend way too much on me being around which is always a bad sign. So in order to get some help and fresh ideas I’m looking for someone to help with running the next GSoC and SoK. If you’re interested let me know. I’d be delighted.
The Community Working Group will be around to discuss all kinds of community-related questions again on January 14th at 8pm UTC. Come to #kde-cwg on freenode for a chat. Want to find out how to make your release party rock? Trying to find ways to get more diversity into your team? Unsure how to handle a situation? Anything else? We’ll try to figure it out together. It would be great if you could add your topic to the agenda. See you on Friday.