[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Like to do with ideas at GSoC2013

From: Miguel Ángel Arruga Vivas
Subject: Re: Like to do with ideas at GSoC2013
Date: Mon, 11 Mar 2013 17:00:01 +0100

Hi Sreedhar,

I also would like to participate in GSoC this year, but already I am
contributing to GNU Gettext, so I will try to answer your questions.

First of all, _Free Software_* community is open to anybody, so there
are lots of places where you can start to work[1][2]. Almost everything
in GNU is in C[3], so you should not have any problem with the
programming language because you already know it. Neither you should
expect to work with anything ending in .NET (other than dotGNU
project[4], of course).

IMHO, the best advice is: _scratch your own itch_, something like adding
a feature you love to a program you are using or fixing a bug you face
up regularly is the best way to start. You should start reading the
documentation of that specific project[5][6] and learning what the
source code really does. Also you should send a mail to the mailing
list[7], because someone could be also working on that or It could be a
really hard task. Also they could help you and give you valuable tips
and advices.

You also should know about version control systems[8], every project use
one, nowadays almost all distributed, usually git[9] and bazaar[10]. But
this should be the last step, even if you do not have any knowledge
about that, because you always could send patches[11] while you are
learning how to use project's one and somebody will commit them.
Nevertheless, you will find it very useful as soon as you are accustomed
to work with VCS.

Also always remember, Google is your friend. Even more in Google Summer
of Code. ;-)

D'oh! I almost forgot it. Also you some knowledge about GNU Make[12] and
Autotools[13][14][15] would help you a lot, because they are the GNU
building system and are widely used.

Best regards,
(*) I remarked Free Software, because GNU is not open source. You should
read an essay from rms at
<> that
explains it better than I could do.
[2] (Some of that are spam, sorry)
[11] Most projects use unified style for readability, see at:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]