From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Mihai Mandrescu <mihai.mandrescu@gmail.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: Google Summer of Code
Date: Wed, 19 Mar 2014 03:43:00 -0000 [thread overview]
Message-ID: <41D35226-43F0-49EA-BDA2-F44436C83BC7@linaro.org> (raw)
In-Reply-To: <CAPuyOWC_37qYJUx9tSQmp7Rn0OXOv76ADXYev5kp4jRSphRPgQ@mail.gmail.com>
On Mar 17, 2014, at 2:39 AM, Mihai Mandrescu <mihai.mandrescu@gmail.com> wrote:
> Hello,
>
> I just enrolled in Google Summer of Code and would like to contribute
> to GCC. I'm not very familiar with the process of getting a project
> for GSoC nor with free software development in general, but I would
> like to learn. Can someone give me some hints please?
>
Hi Mihai,
There is very little time left for student application -- only 2 days.
In general, by now you should have a specific idea that you want to work on, it doesn't have to be your own, there are many ideas for potential GSoC projects at http://gcc.gnu.org/wiki/SummerOfCode .
You need to be realistic about your experience in compiler development and GCC development. It is better to apply for an easier/smaller project and successfully finish it, than to work on a complicated project and not get it done.
Finally, please don't cross-post to several lists, gcc@gcc.gnu.org is the correct list for development discussions (with gcc-patches@gcc.gnu.org being the list for discussion of specific patches).
Thank you,
--
Maxim Kuvyrkov
www.linaro.org
next prev parent reply other threads:[~2014-03-19 3:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 13:39 Mihai Mandrescu
2014-03-19 3:43 ` Maxim Kuvyrkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-05 3:50 Supriya Palli
2019-04-05 9:24 ` Martin Jambor
2019-04-05 10:15 ` Jonathan Wakely
2019-01-21 18:08 Google Summer Of Code Vikramsingh Kushwaha
2019-01-21 18:14 ` Vikramsingh Kushwaha
2019-01-28 18:01 ` Martin Jambor
2005-06-01 5:35 Google Summer of Code Jeyasankar Kottalam
2005-06-01 6:34 ` Ranjit Mathew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41D35226-43F0-49EA-BDA2-F44436C83BC7@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=mihai.mandrescu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).