git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Khalid Masum <khalid.masum.92@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [GSoC23] Working on project Idea from SOC 2011
Date: Thu, 9 Mar 2023 14:23:26 +0100	[thread overview]
Message-ID: <CAP8UFD2s12CLDj6tOQAE-KMhog_qPpFUnp5TXHNSZAauue-8AQ@mail.gmail.com> (raw)
In-Reply-To: <CAABMjtGXGZtUnU+8KgEccNeLXRJmWnE5f24BMG8ysbZKfT-ctQ@mail.gmail.com>

Hi,

On Thu, Mar 9, 2023 at 1:15 PM Khalid Masum <khalid.masum.92@gmail.com> wrote:
>
> There is this SOC 2011 idea named "Resumable clone" here:
>
> https://archive.kernel.org/oldwiki/git.wiki.kernel.org/index.php/SoC2011Ideas.html

[...]

> Goal: Allow Git to resume a cloning process that
> has been aborted for any reason.
> Languages: C

> Can I work on this idea for GSoC23?

You would need to find (co-)mentors willing to mentor you on this project.

I think we don't propose this kind of project anymore as we think they
are too difficult. Some reasons are explained in the "Note about
refactoring projects versus projects that implement new features" in
https://git.github.io/General-Application-Information/

> If so how should I get started?

See the section I just mentioned. There is "an applicant proposing
something original must engage with the community strongly before and
during the application period to get feedback and guidance to improve
the proposal and avoid the above potential issues".

> I have completed one of the microprojects by the way.

Great, thanks for your interest in working on Git!

  reply	other threads:[~2023-03-09 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 12:07 [GSoC23] Working on project Idea from SOC 2011 Khalid Masum
2023-03-09 13:23 ` Christian Couder [this message]
2023-03-10  5:39   ` Khalid Masum
2023-03-09 14:26 ` Derrick Stolee
2023-03-10  5:46   ` Khalid Masum

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=CAP8UFD2s12CLDj6tOQAE-KMhog_qPpFUnp5TXHNSZAauue-8AQ@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=khalid.masum.92@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).