From: Christian Couder <christian.couder@gmail.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [GSoC] Introduction
Date: Thu, 23 Jan 2020 23:51:08 +0100 [thread overview]
Message-ID: <CAP8UFD0jwWREegw5h7NOk1DJpu7AjpSy6yp8KiUJwK8OzFQ8dg@mail.gmail.com> (raw)
In-Reply-To: <20200123180421.16720-1-shouryashukla.oo@gmail.com>
On Thu, Jan 23, 2020 at 7:04 PM Shourya Shukla
<shouryashukla.oo@gmail.com> wrote:
> Thank you for your advice! Apologies for not tagging my patch with [GSoC],
> I didn't realise it before. Is it okay if I try solving a couple of issues
> and then focus on the GSoC project(following from what you advised)?
Yeah, it is okay, but we ask for "Only ONE quality focused
microproject per student". So solving other issues might not help much
your GSoC application.
> Also, I wanted to ask whether or not one can try attempting the projects mentioned
> last year[1] this year as well?
You should probably ask the persons mentioned as "possible mentors"
> I observed that only one idea[2] was picked out of
> the aforementioned project list.
>
> [2]: https://summerofcode.withgoogle.com/archive/2019/projects/5390155215536128/
Yeah, because one GSoC student suggested a project idea on his own.
Best,
Christian.
next prev parent reply other threads:[~2020-01-23 22:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 20:42 [GSoC] Introduction Shourya Shukla
2020-01-23 11:02 ` Christian Couder
2020-01-23 18:04 ` Shourya Shukla
2020-01-23 22:51 ` Christian Couder [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-01 13:02 [GSOC] Introduction Hariom verma
2020-01-23 11:16 ` Christian Couder
2020-01-23 20:18 ` Hariom verma
2020-01-23 22:38 ` Christian Couder
2019-02-24 10:05 [GSoC] Introduction Rohit Ashiwal
2019-02-24 14:47 ` Johannes Schindelin
2019-02-25 6:50 ` Christian Couder
2019-02-25 11:35 ` Rohit Ashiwal
2019-02-25 20:21 ` Christian Couder
2019-02-25 21:09 ` Eric Sunshine
2015-03-07 11:25 [GSOC] Introduction karthik nayak
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD0jwWREegw5h7NOk1DJpu7AjpSy6yp8KiUJwK8OzFQ8dg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=shouryashukla.oo@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).