public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: 김규래 <msca8h@naver.com>
To: "Martin Jambor" <mjambor@suse.cz>
Cc: "Jakub Jelinek" <jakub@redhat.com>, gcc@gcc.gnu.org
Subject: Re: [GSoC 2019] No application template?
Date: Tue, 26 Mar 2019 19:42:00 -0000	[thread overview]
Message-ID: <b4ad25e86f526e547136d6ff52729dd@cweb006.nm.nfra.io> (raw)
In-Reply-To: <ri67ecmzg0s.fsf@suse.cz>

 
Hello,
Thanks for your guidance.
I adopted a little bit from the HPX form and the previous year's form that you provided.
Below is the link to my proposal yet submitted to GSoC.
I will happily receive any feedback before submitting.
https://docs.google.com/document/d/1UwrBOsiAXsZSClsq1r6tAEw6QdqUzJvgW74SQpcWlIU/edit?usp=sharing
 
Ray Kim.
 
-----Original Message-----
From: "Martin Jambor"<mjambor@suse.cz>
To: "김규래"<msca8h@naver.com>; <gcc@gcc.gnu.org>;
Cc: "Jakub Jelinek"<jakub@redhat.com>;
Sent: 2019-03-26 (화) 08:32:51 (GMT+09:00)
Subject: Re: [GSoC 2019] No application template?
 
Hi,

On Sun, Mar 24 2019, 김규래 wrote:
> Hello,
> I was trying to write my application for GSoC 2019 but couldn't find an application form for GCC.
> Some other organizations seem to have GSoC application forms/templates.
> The gcc GSoC wiki page doesn't mention any.
> Is the application format free? or did I miss it somewhere?

No, you did not miss anything, we do not have any specific application
format to follow.  In the OpenMP tread you sounded like you knew what
to do and why anyway.  But to at last give an example, last year this
was an application that would have been accepted if the applicant did
not retract it:
https://docs.google.com/document/d/1YkKYI3J-pKFfHLdxljWVoJ89l2oVGibxslIW3ikluz8/edit
(at least at the moment it i still available).

> If it is free, is there anything I should include else than what is mentioned in [1, 2]
>  

Generally speaking, it is probably a good idea to accompany the proposed
project description with a brief motivation, an expected time-line (we
understand it is likely to change) and a brief introduction of your
technical background, skills and/or accomplishments.  The project
description is the most important part however (and each project is
perhaps best explained differently), we'll mostly judge your abilities
from your interactions with us, on mailing lists and IRC, rather than
from a CV.

If you share the proposal with us on this list some three or four work
days before submitting it, we are likely to have a look at it and
comment if we'd like something changed.

Good luck,

Martin


> Ray Kim
>  
> [1] https://www.drupal.org/node/59037
> [2] http://of-code.blogspot.com/2007/08/soc-experience-introduction.html

      reply	other threads:[~2019-03-26 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24  6:29 김규래
2019-03-25 23:32 ` Martin Jambor
2019-03-26 19:42   ` 김규래 [this message]

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=b4ad25e86f526e547136d6ff52729dd@cweb006.nm.nfra.io \
    --to=msca8h@naver.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=mjambor@suse.cz \
    /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).