 So it's a banner for one, so it's going to be three-yard where there's student programs and I'm sure a lot of the people who are here are ignoring myself, are venting into a thanks to the student programs. So I think one of the goals will be to have a sort of on-world interview with others and that's going to be a big help for us. So yes, Usha, Valerie and me are here to talk about and answer your questions about our student programs. First I want to start with a short introduction of what this actually is and so on. So the KD community has three goals currently. Sorry, technical problems. That looks good. So three goals. Currently those are privacy software, top-notch usability and productivity and streamlined onboarding of new contributors. And that last one is highly related to our student programs because KD as a community has always been very much about mentoring people, teaching them how to write good code, how to contribute to an open source project and we have programs who help with that. What do we have? We have Season of KDE, Google Summer of Code and Google Code in. We have also taken part in Outreachy once but currently not, so we left them. Google Summer of Code. It's a program by Google as the name says that's run to get university students a summer job basically to work on open source software and it's really great. We have participated since 2005, certainly, and it's always been a meaningful contribution to KDE because it got us to think about, okay, what can people actually do in our projects? How can they do it? What kind of things do we need to improve in terms of documentation, explaining what we do and so on. And Google is nice enough to pay those students for us so they can work on our software for a summer. There are a few important things in Google Summer of Code. The most important one is probably the community bonding period at the beginning where they really get to know the people in their team and in their sub-project and their community. There are regular evaluations to really help the students stay in track of their project and adjust that if needed. And it is very much focused on code and development work so not marketing, documentation, translations and things like that. The next program we take part in is Google Code in which is a similar program but for younger high school students mostly. Also hosted by Google in the other half of the year. And it's not paid. It's more a contest where people get points and rewards for the tasks they have done. It's a much more bite-sized task compared to Google Summer of Code and it's a bigger thing that you get to work on and it's a lot more students that the mentors support as part of this program. And it's always busy time but it's also a lot of fun to interact with the younger kids and get them excited about our software. Last year we decided not to participate because everyone was kind of... Tired. Tired as it worked probably. But we hope we can participate again in the next one with much more energy and support the students that are coming through. And for the kids the really exciting thing is probably the grand prize which is getting to go to Google and visit the campus and get to know other students who worked on other projects as part of Google Code and so on. And the mentor who also gets to go to the grand prize trip. Then we have Season of KDE which is our own program that we run because we have seen that there was a lot of answers around Google Summer of Code but there were people who didn't really fit into criteria for Google Summer of Code either because they weren't university students or because they didn't want to do development work or because Google Summer of Code's timeline didn't fit them or any number of other reasons why they couldn't be a part of Google Summer of Code but still wanted this structured program contributing to a free software project. So we have this, it's much more relaxed and less demanding and competitive than Google Summer of Code is. There's also an evaluation period at the end and we send them a t-shirt and some stickers and a nice card. This is a thank you for their time spent on KDE and a certificate to say that they successfully completed their project which they can use for example through a university application or similar when they want to. And it is open to more kinds of contributions so not just code but also code. All right. And currently it's mostly the three of us, to be honest, mostly two of them doing the work on running these programs and if one of you wants to join us and have us out it would be super appreciated and it's a very nice and rewarding thing to see all these people coming to our community and getting their first taste of contributing to KDE's software. All right. And with that we are opening for questions. Maybe I have a question first. Who has taken part in any of our programs? Yeah! Give yourself a hand. Awesome! Did you ever do a season of KDE? Yes, it was a season of KDE. I didn't actually do a season of KDE. All right. So you had a question? No. You also took part. Okay. Any more questions? I have a small question. Okay, I can try to repeat the questions. My question is, do we have, like they tell how many students we are trying to do this in Germany this year? And how many of them actually take part in the program? So the question is, do we know how many people take part in that? We do have some data. The success rate isn't super high, but that is to be expected, I would say, to a degree. And we do have enough success cases to make it worth all of our time. I would say that if you ask any team that has participated, they know very well how valuable it is. It is valuable for the mentors, because there's nothing like teaching somebody else to help you figure out what you know and what you don't know. And it also helps you clarify things. And it probably makes your own code better. Also, we're always trying to figure out how to onboard the students better, how to include them in the community more. The fact that we didn't do GCI last year, Google Code, we usually call it GCI, we wanted the students from previous years to be mentors, because they're closer in age to the students. So the fact that we didn't do it last year was a loss for us in that we couldn't recruit those students to be part of that. But now is the time, if you're in a team, that has any sort of short tasks that can be done in a day or two to start collecting those somewhere, not just in your head, but on a wiki or some sort of shared document or even just an email to your team mailing list to get discussion started, because now is the time to start collecting those ideas. Any more questions? What the actual season of KB is? Is it spring or summer or a wiki? Do you have any days when it happens? Depends on who's with you on. Not something very fair, winterish at all. But it's much more flexible than it is, so if it doesn't fit the schedule of someone, then it can be tricky. So now we are trying to start, so it's not tricky when someone wants power to end, so that we can also get some time to relax and create a way to do it. Otherwise it's a whole year for us to participate in different, and as we said last year it was a bit too much for us so we just offered out of our dreams so yeah, thanks a lot. Thank you very much. Maybe not a question. Because you said that the season of KB is less competitive than the new season of Kodai, I appreciate that because I think the correlation with access or approach is maybe more creative. And is it also crossing the generations or are there mostly young students or are there some good individuals or artists? One of our most successful Google, or Summer of KDE people was not a student, had been a student for many years and created the first CI system for KDE. So that has been superseded, but she got the ball rolling and she was just overjoyed that she could do that at not being enrolled as a student. So it is open to anybody who needs mentoring if we can find a mentor for the project. We'll do it. If you like administration, join us. You too can send nagging emails. If you like administration, join us. You too can send nagging emails. If you like administration, join us. Thank you. Thank you.