All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: MOHAMED AYMAN <mohamedaymanworkspace@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Question about microprojects for GSoC
Date: Tue, 10 Mar 2026 10:27:17 -0700	[thread overview]
Message-ID: <xmqqtsunvbm2.fsf@gitster.g> (raw)
In-Reply-To: <CABWZVhraW4zD132R0iv1uhBwS=uuQZduksCCYN_+4+OcBKBodQ@mail.gmail.com> (MOHAMED AYMAN's message of "Tue, 10 Mar 2026 08:11:05 +0200")

MOHAMED AYMAN <mohamedaymanworkspace@gmail.com> writes:

> Hello,
>
> My name is Mohamed Ayman and I am an engineering student specializing
> in embedded systems. I am interested in applying to Google Summer of
> Code with the Git project.
>
> I am currently setting up my development environment and reviewing the
> recommended microprojects to become familiar with the Git workflow and
> contribution process.
>
> If anyone has advice on a good starting microproject or areas where new
> contributors could help, I would greatly appreciate the guidance.
>
> Best regards,
> Mohamed Ayman

Where did you hear about the need for GSoC applicant to finish one
microproject as a requirement for application?  That place should
have links to microprojects ideas.

https://git.github.io/General-Microproject-Information/ is one of
the canonical starting point.

No microprojects done by new contributors "could help" us, as a
microproject by definition is a trivial "Hello world" project that
is to help new contributors dip their toes in the water, getting
introduced to the development process.  Look at the list archive
https://lore.kernel.org/git and see what other aspiring GSoC
applicants are already working on.

Have fun.

      reply	other threads:[~2026-03-10 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  6:11 Question about microprojects for GSoC MOHAMED AYMAN
2026-03-10 17:27 ` Junio C Hamano [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=xmqqtsunvbm2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mohamedaymanworkspace@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.