I have put together a checklist of tasks and suggestions I advise you to follow during the community bonding phase. While you are not required to code until May 21 (end of the community bonding period), you are expected to get ready and be in good standing with your community. By now I suppose you have already contacted your mentor.
What follows also applies to Season of KDE students.
(1) Join the relevant communication channels.
KDE contributors do not just silently churn out code, they like to hang out a lot, exchange ideas and opinions. But since KDE pretty huge, different subprojects have their own communication channels. You should definitely join your subproject’s development mailing list (e.g. firstname.lastname@example.org for Amarok, email@example.com for digiKam, etc.) as an absolute minimum. I also strongly advise you to join your subproject’s IRC channel on irc.freenode.net, as many development discussions happen there (e.g. #kdevelop for KDevelop, #plasma for Plasma, etc.). You should also join #kde-devel and #kde-soc on irc.freenode.net. Your mentor will instruct you if there are other communication channels you should be aware of.
(2) Get acquainted with KDE’s infrastructure.
You should get a KDE Identity account and fill out your profile. This account works with most of the services provided by KDE, such as review board, wikis (Community and Techbase) and forums. You need to sign up separately for KDE’s issue tracker. You must then also apply for a contributor account to be able to commit code, please follow these instructions to do so.
(3) Get ready to blog.
Writing a blog is a great way to introduce yourself to the community and keep everybody informed on your progress. If you do not have a blog yet, consider starting one and having it aggregated on Planet KDE. I personally recommend WordPress which is also Free Software but you can use whatever platform you like. It is not mandatory but I think it’s a nice way to motivate yourself and bond with the community. Do not feel pressured to do it, but a few articles when you reach certain milestones in your project could be very nice.
(4) Learn the ways of the community.
Free Software communities work in certain specific ways which are sometimes very different from what a new Google Summer of Code student might be used to. To help you get up to speed quickly, Donnie Berkholz, Lydia Pintscher and Kevin Smith, Google Summer of Code administrators for Gentoo & X.Org, KDE and XMPP Standards Foundation respectively put together a very good article on the DOs and DON’Ts of Google Summer of Code for students. If you are new to KDE I consider this article a required reading assignment before starting your work. It is short, easy to read and to the point, and every word of it applies to your situation as Google Summer of Code students at KDE. For more information on getting involved with KDE specifically, I highly recommend the Free manual KDE Dev Guide, a step by step introduction to KDE for new contributors. A much more complete resource on getting involved with Free Software is Open Advice, a Free knowledge collection from a variety of prominent Free Software contributors.
(5) Talk it through.
You are not required to code for almost a month until the coding period begins, but work on your project starts now. Plan ahead. Do analysis and design. Make sure that if there’s any potential obstacle in your project, it comes up as soon as possible. Set aside a few hours and schedule meetings with your mentor to discuss the fine details of your project and iron out the kinks. It’s best if such discussions are held in the subproject’s IRC channel to allow all the interested parties in the community to contribute. Be ready to submit regular updates to your mentor once you start coding. KDE Google Summer of Code administrators strongly recommend weekly updates to the subproject’s development mailing list, but the exact way you do this is up to your mentor.
This year KDE has accepted 60 Google Summer of Code students. We are happy with this number, it is more than last year, and I’m sure these 60 students will make a great contribution to KDE as a whole.
But this number is still a hard limit: we had to say no to many brilliant proposals. The selection process has not been easy, and we had to make a lot of tough choices. KDE definitely has the mentoring capacity for more than 60 students at a time. So while we cannot come up with more Google Summer of Code slots, we can still make our mentors available through a similar scheme: Season of KDE.
What is Season of KDE?
Season of KDE is a community outreach program, much like Google Summer of Code, hosted by the KDE community. It is meant for people who could not get into Google Summer of Code for various reasons, or people who simply prefer a differently structured, somewhat less constrained program. Season of KDE is managed by the same team of admins and mentors that take care of Google Summer of Code and Google Code-in matters for KDE, with the same level of quality and care.
Who can take part?
Everyone can apply for Season of KDE. We give preference to those who have applied for Google Summer of Code and to students, but we will gladly consider applications from anyone.
What do I get out of this?
A great summer working on a really cool KDE project and gaining valuable experience. If you complete your project successfully you also get a T-shirt, a certificate, and maybe a few other goodies.
How do I apply?
If you are serious about it and have already contacted the relevant KDE subproject to discuss your proposal, fill out the Season of KDE application form and we will get back to you.
What is the timeline?
The timeline is up to you and your mentor. We advise you to stay as close to the Google Summer of Code timeline as possible. The only hard constraint is the application deadline: you apply through the application form before May 7, 2012 at 19:00 UTC in order to be eligible for participation.
Do I need to have a mentor before applying?
It is preferred. Ideally, you should contact a KDE subproject well before applying, ask for feedback on your idea if you have one, and request a mentor directly. A list of KDE subproject contacts is available on the Google Summer of Code 2012 ideas page. You can also apply without a mentor and we will try to find one for you.
Do I need to have a project idea before applying?
It is preferred. If you do not have one we will try to find one for you. Keep in mind that the KDE community is pretty big, so you should at least have an idea of which KDE subproject you wish to work on.
Do I need to write a proposal like in Google Summer of Code?
No, but we would like to see a brief project plan describing what you will be working on.
Is it only for coders like Google Summer of Code?
We are willing to consider non-coding projects as well, but you should definitely get in touch to figure out the details beforehand. The KDE Community Wiki describes ways to get involved with KDE that do not require coding.
I applied for a project in Google Summer of Code but another student got selected for it. Can I still work on it?
Maybe, but likely not. You should ask the mentor that was assigned to your idea. We can try to find something related for you if you want, or something completely different. Let us know what you wish and we will do our best to accommodate your request.
Is this an extension of Google Summer of Code or connected to Google?
No. While Season of KDE is in many ways modeled after Google Summer of Code and administered by the same members of the KDE community, it is completely independent from Google Summer of Code and has no connection to Google whatsoever.
For further questions feel free to join our IRC channel #kde-soc on Freenode or email the admin team at firstname.lastname@example.org.
In the past four years we had in order 1, 4, 8 and 20 successful Season of KDE students. We like to think this says something about how welcoming, helpful and fun the KDE community is. Our goal for this year is at least 30
Are you going to be one of them? You should be!
Google has just published the list of student proposals that have been accepted for Google Summer of Code 2012.
This year KDE received more than 200 proposals. 192 of those are valid and have not been withdrawn. The general quality level is very high, and most of those 192 proposals are very good. Google has allocated 60 student slots to KDE, which means that this year we are able to accept 60 Google Summer of Code students. The trouble is that we got a lot more than 60 good proposals! During the past few weeks the GSoC admins and mentors of KDE had to make some really tough choices.
If you are a student, you should have received a notification about the state of your proposals via email. Either way, you can check the status of your proposals on Google Melange.
Accepted into Google Summer of Code?
Has your proposal been accepted by an organization? Congratulations!
Has your proposal been accepted by none other than KDE? Awesome! This means that you will be spending your summer hacking with us. On behalf of the KDE community, I wish you a warm welcome! The selection process was hard and competitive, but if your proposal has been accepted it already means that we think you are the very best. Feel free to brag about it a bit, you’ve earned it!
I will write another blog article shortly on the next steps for accepted Google Summer of Code students.
Not accepted into Google Summer of Code?
If on the other hand your proposal has not been accepted, you are still very welcome to hack on KDE! Note that I never used the word “rejected” because I do not consider a proposal that has not be accepted for Google Summer of Code as something that’s unwelcome or unworthy for KDE. Many factors come into play in proposal selection which do not depend on the skill set of a student, including slot availability and mentor availability. We had to say no to quite a few brilliant proposals.
For those students whose proposals have not been accepted for Google Summer of Code who still wish to contribute to KDE in a guided, mentored way this summer, KDE hosts the Season of KDE program. Season of KDE is much like Google Summer of Code: while the student doesn’t get paid, he does get a mentor and a T-shirt, and he gets to hack on KDE for the summer and beyond. My first summer with KDE was as a Season of KDE student, and it was a very rewarding and enlightening experience. Season of KDE will be officially announced shortly, stay tuned
Some other organizations also host programs similar to Season of KDE for students who did not find a place in Google Summer of Code or simply prefer a differently structured program. Such programs include Haiku Code Drive (not confirmed yet for this year), illumos Students (not confirmed yet for this year), Umit Summer of Code (not confirmed yet for this year), X.Org Endless Vacation of Code, Ruby Summer of Code and possibly others. All of these programs allow you to work on really cool software with a mentor over a longer period and create something you can be proud of. Other communities will likely also be willing to provide guidance if you contact them directly, so don’t be shy
Prospective Google Summer of Code 2012 students.
This is a friendly reminder that the student proposal submission period closes in 3 days.
If you are still working on a proposal, or if you have prepared a proposal but you have not submitted it to Google Melange yet, you better do it very soon!