From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Shourya Shukla <shouryashukla.oo@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>
Subject: Re: Git in GSoC 2021 ?
Date: Fri, 19 Feb 2021 00:52:27 +0100 [thread overview]
Message-ID: <CAP8UFD1VaOBWcf3RQTc6OdmkUZCOOOO0mubRoWAvao6uNtNkgQ@mail.gmail.com> (raw)
In-Reply-To: <20352639-deaa-0e3f-c99e-9bde937d67f9@gmail.com>
Hi Kaartic and all,
On Tue, Feb 16, 2021 at 7:12 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
>
> Hi all,
>
> Excuse my curiosity. I'm not sure if there has been discussion about
> Git's participation in GSoC 2021 but my search in the archives
> didn't get me anything. The deadline for Org application seems
> to be around the corner (this Friday, Feb 19th at 1900 UTC).
Yeah, sorry for not discussing that before, and thanks for starting
the discussion.
> So, I was curious to know if we've already applied to participate
> in GSoC 2021 (or) if we're planning to participate?
I don't think we have applied yet, but I would be ok to apply. I think
I will do it soon unless people objects.
> In case we're participating we'll need ideas that fit the new
> structure of GSoC 2021. Concise entry about the new structure
> from Rev News 68 [1]:
>
> Google Summer of Code 2021 has been announced with significant
> changes compared to previous editions. Notably coding hours and
> period will be reduced from 350 hours and 12 weeks to 175 hours
> and 10 weeks; there would be 2 evaluations (instead of 3).
> Additionally, eligibility requirements will be relaxed, among
> others allowing people participating in a variety of different
> licensed academic programs, not just students of accredited
> university programs.
>
> See the related blog [2] for detailed information.
I have just created an Idea page with 2 project ideas:
https://git.github.io/SoC-2021-Ideas/
Other ideas are very welcome.
> Speaking of GSoC, unlike last year I'll not be able to actively
> co-mentor this year due to certain circumstances in my family.
> I'll be able to help passively, though.
Ok, thanks for helping passively!
> Also, one thing about project ideas. Shourya Shukla who worked
> last year on the builtin conversion of `git submodule`
> (currently stalled [3]) has told me privately that he isn't
> interested in continuing the port further. So, finishing the
> port of `git submodule` could be a nice project for GSoC 2021.
> I believe it would fit the new GSoC structure but I might be wrong.
Yeah, I agree. In the ideas list Shourya is mentioned as a possible
(co-)mentor to a project to finish the builtin conversion of `git
submodule`, as he told me that he could be ok with co-mentoring on
this.
Best,
Christian.
next prev parent reply other threads:[~2021-02-18 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 18:12 Git in GSoC 2021 ? Kaartic Sivaraam
2021-02-17 17:01 ` ZheNing Hu
2021-02-18 23:52 ` Christian Couder [this message]
2021-02-19 6:00 ` Hariom verma
2021-02-19 8:47 ` Christian Couder
2021-02-19 10:20 ` Hariom verma
2021-02-19 11:09 ` Christian Couder
2021-02-19 17:08 ` ZheNing Hu
2021-02-19 18:26 ` Hariom verma
2021-02-20 6:11 ` ZheNing Hu
2021-02-19 14:56 ` Christian Couder
2021-02-19 16:30 ` Kaartic Sivaraam
2021-02-19 17:14 ` Christian Couder
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=CAP8UFD1VaOBWcf3RQTc6OdmkUZCOOOO0mubRoWAvao6uNtNkgQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=peff@peff.net \
--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).