Akademy sponsorship request deadlines

Filed under: free software,KDE,PlanetKDE — Lydia at 7:14 pm on Saturday, February 18, 2012

Some of you need sponsoring from KDE e.V. to attend Akademy. The board will handle sponsorship requests for travel and/or accommodation in 3 rounds. The budget is limited and only the funds not spend in a round will be transferred to the next round. (So you want to be in the first round.) The deadlines for sending requests to the board are:

  • round 1: 1st of April
  • round 2: 1st of May
  • round 3: 1st of June

We try to handle requests within one week after these deadlines.
For more information about reimbursement rules please check KDE e.V.’s reimbursement policy.

Akademy Call for Papers

Filed under: free software,KDE,PlanetKDE — Lydia at 11:28 pm on Saturday, February 11, 2012

Akademy is getting closer and that means it is time to submit talk proposals. I’m sure you have something interesting to talk about. Check out the Call for Papers for more details and some suggestions of what the program committee is looking for. Submit now – don’t procrastinate ;-)

Don’t know what to talk about or have questions/doubts? Find me on IRC or email me.

Also don’t forget to register to attend the conference! Akademy is free but you need to register to attend.

accessibility co-mentors needed for GSoC

Filed under: free software,KDE,PlanetKDE — Lydia at 1:58 am on Friday, February 10, 2012

As announced earlier KDE will apply to become a mentoring org again for Google Summer of Code in 2012. We decided to focus on accessibility this round should KDE be accepted again. To make this happen KDE’s mentors need help. Most of the mentors do not have the knowledge needed to make good decisions when it comes to making our applications more accessible. We are therefor looking for co-mentors who can help them – people who either have a disability that requires changes in KDE’s software to make their life easier or people who are otherwise knowledgeable in the area. These co-mentors would not have to do any of the mentoring on the coding side but instead advice the student and main mentor on non-coding parts. Does that sound like something you can help with? Then please send an email to kde-soc-mentor@kde.org and introduce yourself and how you could help. Please also pass this on to anyone you think might be a good fit.

GSoC 2012 is on!

Filed under: free software,KDE,PlanetKDE — Lydia at 9:05 pm on Tuesday, February 7, 2012

At FOSDEM it was announced that Google will run Google Summer of Code again in 2012. Wohooooooo! KDE will apply as a mentoring organisation again. Here are the next steps to prepare:

For students:

  • Read the GSoC FAQ and timeline. (Don’t skip this step. It’s important.)
  • Read some GSoC infos from KDE.
  • Keep an eye on the ideas page to see what KDE is looking for. You’re also welcome to come up with your own idea as long as you discuss it with a mentor.
  • Get in touch with a mentor and discuss your idea. Maybe already contribute a little. (The better we know you the time it gets to voting on your application the better.)

For mentors:

  • Add ideas to the ideas page. Only add ideas if you are willing to mentor them! Please add them within the next 2 weeks. Earlier is better as students are already looking for ideas now. We will try to give a focus to accessibility this round. This does not mean that all ideas have to be related to that in some way but it would be great if a significant percentage of them would be.
  • Consider holding a GSoC info session at a university near you. Get in touch with me if you plan to do that. There are ready-made presentations and flyers available for you.
If you have any questions feel free to come to #kde-soc on freenode or send an email to the mailing list kde-soc at kde dot org.

changes in Kubuntu

Filed under: KDE,Kubuntu,PlanetKDE,PlanetKubuntu — Lydia at 2:03 am on Tuesday, February 7, 2012

I’ve been running Kubuntu ever since I decided to switch to Linux on my computers. Kubuntu is what got me hooked on KDE’s software. I was on it’s council for 2 years. It has a special place in my Free Software world.

At FOSDEM I had a long chat with Jonathan. He told me that he’ll no longer be able to work full-time on Kubuntu soon. This was sad news because I know how much it means to him.  For more details read his blog. While this is sad it is also good news. It clarifies Canonical’s position and gives the team behind Kubuntu more power.

I’d like to thank Canonical for sponsoring Jonathan for the past years. It was important for Kubuntu and for KDE. Kubuntu is important for KDE because a diverse distro eco-system is vital for us. Let this be a much-needed wake-up call and take it into our hands.

Hop over to #kubuntu-devel on freenode and see where you can help out for the next cycle.

Google Code-in stories – part 5

Filed under: free software,KDE,PlanetKDE — Lydia at 3:36 pm on Wednesday, February 1, 2012

KDE mentored a lot of students during Google Code-in and I asked some of them to write about their experience. This is the final part of the series.

Alexey writes:

KDE was my fourth open source community to work with in Google Code-In 2011 and I can say I really enjoyed my experience.

First of all I’d like to thank all the mentors assigned to KDE tasks for the quick claim requests responses, reviews and detailed feedback. Unfortunately, I can’t say the same about all the other communities I’ve participated in.
I completed 3 translations tasks and my translation included compiling and installing some KDE packages, working with translation system and working with graphical editors to translate some screenshots and edit some pictures.
As soon as I claimed one of the tasks I was able to start my work, because the task information was always full enough.

Of course sometimes I had some questions (for example, I had no clue why I could not install one of the necessary packages), but I always got professional feedback in a short time.

Also I have to record that almost every KDE project has a full and clear documentation.
Of course, the documentation is not always translated to native languages for users, but it didn’t bring any difficulties to me.
And I hope that such contests like GCI will bring more and more developers into your community and there won’t be any problems with it at all.

Evidently, it was a great pleasure to work with KDE. Thank you very much! To be honest, I would like to take part in KDE community, so I’m trying to choose the project I would be interested in most.
I would also like to thank Google for creating such useful projects for open-source world like Google Code-In!

Good luck, KDE!

Edwin writes:

In the beginning, when Google Code-In took place for the first time, I’ve found some information about it on Russian website dedicated to GNU/Linux (its address is not secret: linux.org.ru). I thought it’s a great opportunity to improve some skills, for example, programming or language knowledge.

To be honest: yes, it also was a good possibility to earn some money :)

But there is another reason: open souce projects are usually maintained by developers, who contribute their skills and time to make software better. They may create patches for programs, which they use. It’s just their hobby. If you use the software which you have contributed to, you can show a feature and say proudly: “My work!”.

That’s why I decided to participate in the contest.

Although I don’t use the software, which I’ve contributed to during the contest (and probably nobody of my friends does), I have decided to do something. Most of the tasks I’ve done during the contest (both times) are Russian translations (I’m too lazy to work with any code :D). I’m from Estonia, but Russian is my native language.

Last year I’ve done three tasks. One of them was Russian translation of Parley. Friendly mentors and community helped me to work it out at some points. Many thanks to them :).

This year seven of my tasks were Russian translations. Four of them were translations for KDE programs: Kleopatra, KMid, Rocs and PhotoLayoutEditor KIPI plugin. It was hard to translate some words, just because I didn’t know the topic very well. Anyway, I’ve figured it out.

If you don’t like going out, it’s better to spend time improving software rather than just doing nothing. Good luck to KDE developers and Code-In participants! :)

Google Code-in stories – part 4

Filed under: free software,KDE,PlanetKDE — Lydia at 3:36 pm on Tuesday, January 31, 2012

KDE mentored a lot of students during Google Code-in and I asked some of them to write about their experience.

Subhashish writes:

Well my first KDE task was “Research: Understanding KDE Users (Individuals)” with mentor Carl Symons (kallecarl). This was my fifth task in the Google Code-In Contest 2011. To be honest, this task (of the three KDE tasks that I’ve completed as of now) was one of my favorite tasks as it was a research tasks in which I tried my best not to leave out any little detail.

It was late night (12:00 AM, Monday, December 5) when I requested a claim for this task. Feeling tired after a nice Sunday, I went to sleep to wake up to a cool Monday morning to see task assigned to me, but I could proceed no more with the task courtesy, the power cuts we are facing here these days. The rest of the day was uneventful for I had to study for my forthcoming exams.

The next day I was able to get kallecarl’s contact details and contact him on #kde-promo. I had a long chat with him about my task asking him what KDE Promo team does, about the Akademy events and many more questions. The best part was that he was patient and was ready to answer my every query. He seemed to be an informative and helpful person (as I observed him) as the other mentors that I’ve worked with.

The above paragraph depicts my normal procedure of starting things with every task that I’ve done. Get the mentor’s email address and most importantly the IRC nick if he/she uses IRC. Then chat with them about the task, its background, scope where things can be improved etc. Then start working on the task.

Research tasks are my favorite because one can get to see how a project functions, which I did get to see but partially, to be honest, little but to a considerable extent. After all how much can one expect to observe within some countable days while working with one part of a project? But as the open source projects are (I mean transparent), one can get to understand it (the project) if one sticks with it and observe for some months which I’d gladly do but that’s another thing.

Understanding what the KDE Promo team needed for the task, I hopped onto the task, put my thinking cap on as I needed to put forward some proposals for conducting the research. I categorized my task’s objectives, looked into what methods may be needed to do the research, borrowed some ideas, drafted a sample document and mailed it to my mentor who politely suggested me some changes and said he was looking forward for more in his reply. From there on, I got excited enough to help me focus more on the task. Funny isn’t it how humans get more dedicated to a task they do if they are encouraged a little?

With that enthusiasm I completed that task and I’ve been completing all of my claimed tasks by doing everything I could to do the tasks justice and which every student participating in this contest would be doing too. Coming to us (the participants), we must realize how great an achievement it is for us to complete at least one task in this contest because we are contributing our efforts to the organizations who need them the most because they serve the humanity by crafting certain free technologies that are class apart and which help the common people. Most of the contributors of these organizations put their heart into these valuable creations in their spare time. These open source organizations, the developers, the contributors and all those who help such projects to improve are the real heroes. Working with them to contribute to their (and ultimately our) cause is a great achievement in itself. It is how I feel and how every participant of this contest must feel.

To be honest, the prizes set for each student who does at least something in this contest are a draw for students like us but it also creates an awareness in us to understand the importance of the term ‘open source’ for those who can see it. I got an opportunity to interact with real heroes who are also nice people. I also understood that there are more ways to contribute other than ‘coding’ and I am really glad that I am doing it. Thank you KDE for giving me a chance voice my opinions! Thank you Google for giving us a rewarding opportunity to work with such amazing organizations!

Google Code-in stories – part 3

Filed under: free software,KDE,PlanetKDE — Lydia at 3:36 pm on Monday, January 30, 2012

KDE mentored a lot of students during Google Code-in and I asked some of them to write about their experience.

Areke writes:

When I first heard about the Google Code In, I was riled up with anticipation. I waited anxiously until midnight of November 21 so I could get started on a task, as this was my first year participating. When the time came, I quickly became disappointed because Melange had quite a few bugs and it was impossible to actually start a task. Well, that might not have been the case for everyone, but it was for me. After about an hour of frustration, I went to sleep hoping to find a task first thing in the morning.

Many days went by and I started completing some tasks. After about five tasks, I started one for KDE. The task was to create a donations landing page to increase the amount of donations they get. After claiming the task, I immediately went on IRC to ask my mentor how to get started. I was given editing access to a blank page and began to code away.

I had gotten the basic layout down and now it was time to fix some issues. I needed to clean the page up a bit because there were a few parts that didn’t look so good. I started to have problems. Every time I tried to fix something, another problem came up. More and more frustration started building inside of me so I decided to take a break.

When I came back to it, I found that I was able to resolve the issues very quickly and was appalled by how simple the solution was. I submitted the URL to my work and waited for a response. I was bummed out when I was told to fix some things, but it was no problem. They were easy fixes and I was soon on my way to my seventh task.

Working with KDE hasn’t just widened my knowledge of programming, it also taught me some important values. Working with KDE has taught me how important it is to have patience, but if I ever feel discouraged or frustrated, I should take a break and come back to what I was doing later. This is something that I feel is very important in life, and now I am very glad that I worked with KDE.

Radoslav writes:


My name is Radoslav, I am from Bulgaria and it is my first apperance in Google Code-in. It all started when my teacher, who is also my cousin, gave us homework to make at least two tasks. A completed my first task which was to check if old KMail bug reports are still valid, which was easy and I finished it for no time. Afer that I had to make a Team Presentation of the Amarok developers team. Now I know who is behind it. And then I completed two more tasks form KDE. One was to make a research and to give some ideas which KDE apps could be ported to work on Plasma Active which once more made me think that KDE developers are doing some crazy stuff :) The other task was to make a research how to understand the KDE users and my mentor was Carl Symons and he helped me a lot with the task.It was more like a team work: I write and he gives he second opinion on the problem. My task was to make five different research methods for understanding the KDE users, I had to search and say for every method what are the pros and what are the cons. It was a hard task and some kind of important for everybody. The task was completed and when the actual research I hope I will be a part of it too :). I met some other very interesting people and I see that KDE is not a community but a family and I want someday to be part of a family like that. :)

Google Code-in stories – part 2

Filed under: free software,KDE,PlanetKDE — Lydia at 3:36 pm on Sunday, January 29, 2012

KDE mentored a lot of students during Google Code-in and I asked some of them to write about their experience.

Arushi writes:

At such a young age working for KDE was like a dream come true. KDE gave me the kind of exposure I have always wanted. It allowed to communicate with different people across the globe and thus enhanced my communication skills. Not only this, I also got to know what opinion other people had about KDE. Surprisingly, all the tasks that I have done are for KDE.
Join The Game, a great program working for a great cause really helped me kick start my work. The very first task that I did was for this organization where in I was required to collect quotes from prominent community members. This task not only encouraged me to converse with people across the globe but also gave me awareness about a magnificent community which encourages free software. Yes, its true :- KDE has awesome technology developed by an incredible community. So, don’t be late Join the Game :D
My second task that was a survey based task improved my research skills and by all means increased my knowledge and awareness about different non- profit organizations. I was also able to get an inside on what these organizations do for their donating members. Exploring the official websites of the organizations such as FSFE, Mozilla etc. was challenging yet amusing, I really learned lots of new things.
But, the most fun task was to help organize a release party. It was fun and an awesome experience as I got to create different pages and also the opportunity to advertise such a great event. KDE made me realize how much effort and hard work everyone is putting in. I even got the chance of being an amateur blogist :P as I wrote two articles for the parties to be organized.
KDE has helped me grow in ways which I can’t even explain. I think I owe a lot to KDE ;)

ravst writes:

The whole idea of the contest is to show to young people what taking part in open source projects fells like. Every contestant gets to choose a task form a HUDGE tasks list, where lot of different organizations put jobs that should be done to improve they projects.
I signed up for the event mainly to earn some money and of course also to learn something and gain valuable experience, but when I started working on my first task, everything changed. I felt something I’ve never felt before; I was happy because I knew that what I was doing wasn’t just another school project, which would be marked and forgotten. It was something that could help people. To be honest, it wasn’t anything spectacular, but even though it felt great to be helpful. My first task was to write subtitles for a You Tube video about a pearl environment. It was very satisfying to see those subtitles being uploaded seconds after I’ve sent them to my mentor. Another task I relay enjoyed doing was dividing a big audio file into smaller ones, containing step by step instructions that would be used in a GPS application for a mobile phone. Thanks to the GCI contest I realized what it is like to take part in an open-source project. Believe me, it’s great.

Google Code-in stories – part 1

Filed under: free software,KDE,PlanetKDE — Lydia at 3:44 pm on Saturday, January 28, 2012

KDE mentored a lot of students during Google Code-in and I asked some of them to write about their experience. I’ll be publishing them here over the next 5 days.

Valery writes:

Google has given school students from all over the world a great opportunity to work with open-source projects, and not only help community, but also earn some money and get a great branded T-shirt. The opportunity is Google Code-In.

It’s the second time I take part in this contest, and the second time I contribute to KDE.

When I claimed my first task in Google Code-In 2010, I felt a little anxious. That task was about improving a sky map application — KStars. I’d already had some experience with C++ and Qt but I had never worked with such a big project before. But when I got in touch with the mentors — Victor Carbune and Akarsh Simha — I understood that there was nothing to worry about! If I had any questions I always got answers to them.

This year I took part in the development of a similar (in some aspect) application — Marble Virtual Globe. This time I had more experience and was better prepared for the tasks. Mentors — Dennis Nienhüser and Torsten Rahn — were really supportive. With their help I’ve managed to improve some of the Marble plugins: Open Desktop social network plugin, Weather plugin, Measure plugin. Also I’ve recorded a new Russian voice set for the navigation speaker. Now everyone can hear my voice while using Marble Navigator!

Also I’ve prepared some Russian translations for KDE applications.

Unfortunately, that’s the last time I take part in Google Code-In. Next year I will be a university student. I am really happy that I was given such a great chance to work with the KDE community. I’d really like to contribute to KDE in future, maybe as part of Google Summer of Code, too.

Thank you very much!

Joan writes:

GCI, Google Code-in, is a project by Google in which FLOSS organizations create tasks for students to complete. KDE is among them, and I completed one task for this organization.

While I did already know about KDE, and have been using it for long, I had never heard of OwnCloud, the subproject for which I completed tasks. My first thought was “how weird, a KDE project without a K!”. However, it turned out to be an amazing project: a cloud computing server, with an HTML interface, which was free and open.

I liked the idea and started working with it. The task consisted in embedding a PDF viewer inside the interface; the viewer to be used was the amazing PDF.js by Andreas Gal, among others. I had heard of it, and thought it would be great to actually work with it, and learning about its internal API.

I completed the task, mentored by Bartek Przybylski. It turned out to be much fun, and I also learned a lot from it. To begin with, interaction with another FLOSS community. I had already worked with other FLOSS organizations, but I found the environment different (new things!). On the other hand, it was really great because I learned a lot about git, the revision control system. Used to SVN, this was a huge step forward. Furthermore, I also had to use it in other tasks, so it was great.

Overall, a great experience. I learned a lot, from it, and was really worth the effort. The initial thoughts about prizes faded away as I began working on this task.

« Previous PageNext Page »