[Glug-nith-discuss] Google Summer of Code

[Debarshi 'Rishi' Ray]

This is from the Bombay GLUG mailing list, thought some of you might
be interested. Just for the sake of information, Pradeepto
Bhattacharya is a KDE hacker and a co-ordinator of the KDE Project in
India.

Happy hacking,
Debarshi

- -------- Original Message --------
Subject: [ILUG-BOM] KDE Google Summer of Code
Date: Thu, 15 Mar 2007 23:50:14 +0530
From: Pradeepto Bhattacharya <address@hidden>
Reply-To: GNU/Linux Users Group, Mumbai, India <address@hidden>
To: GNU/Linux Users Group, Mumbai, India <address@hidden>

Hi folks,

    I am sure Google Summer of Code is nothing new to most of you
people. So we have GSoC '07 even. And like previous years, even this
year The KDE Project will be an mentor organisation. Some of you might
have seen the dot[1] news.

    So I would really urge the students on the list who are
familiar with C++ and Qt/KDE development to take part in SoC. So send
in your proposals. Its a great way to learn new stuff and become a
part of a FOSS project.

     Here are a few pointers [2] and [3]. Please note that [3] is a
list of ideas that various mentors have put in. They are not the only
ideas. You can come up with your own - say for your favourite KDE
application - and recommend the same to the maintainer/author of that
application. See what he/she says and work on the idea and put forth
an proposal to google. If the mentors like your proposal and it gets
selected nothing better than that. Go ahead and do some cool stuff.

       Now here's some simple points that I have realised from my
last year's experience : While putting forth an proposal, don't be
lazy and just cut/copy/paste what the mentor has already posted on
[3]. Be original and explain what exactly you would like to do, how
etc.

      Now if there are students on this list who think that they
are not good in C++/Qt yet, especially the ones in 1st and 2nd year,
fret not. You have an year or two to learn the same and work on it.
And most importantly getting involved in FOSS - in this case Qt/KDE
development doesnot need a SoC even. Just fix a bug or whatever  - I
am sure you know the drill or have heard it countless times. There is
loads of source lying around, pick it up and get going. And trust me,
your chances increase manifold if you already are an contributor.
Because the mentors know that you can do stuff. Although that means
nothing, last year I saw many students who were new and did an awesome
job and some of them kept going on and are now actually contributing
to various KDE projects.

      Good luck to all of you.

      [1]http://dot.kde.org/1173949256/

[2]http://techbase.kde.org/Projects/Summer_of_Code/2007/Participation
      [3]http://techbase.kde.org/Projects/Summer_of_Code/2007/Ideas
      [4]http://code.google.com/soc/student_step1.html

Pradeepto
- --
The KDE Project : http://www.kde.org
KDE India : http://in.kde.org
Mailing List : http://mail.kde.org/mailman/listinfo/kde-india

--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu