git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Anushka Saxena <anushka.saxena.iips@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Regarding candidature for Google Summer of Code 2023.
Date: Mon, 20 Feb 2023 10:46:15 +0100	[thread overview]
Message-ID: <CAP8UFD2bTBz2wTVjV+amtipQ-U78oW0ApE2pKCiLC+A1Nj_Z-A@mail.gmail.com> (raw)
In-Reply-To: <CACkQP8tskwh6CcSFRCzyf82eoo9q_aLfSKD=2=jL+hgYH=f3Rg@mail.gmail.com>

Hi,

On Sun, Feb 19, 2023 at 10:20 PM Anushka Saxena
<anushka.saxena.iips@gmail.com> wrote:
>
> Greetings team Git!
> I am Anushka Saxena. Currently, I am pursuing an integrated Master of
> Technology in Information Technology from International Institute of
> Professional Studies, Devi Ahilya Vishwavidyalaya, India. I have a
> strong interest in open-source technology and the Git versioning
> system.

Great!

> I am excited to introduce myself and express my interest in
> contributing to Debian as part of the Google Summer of Code program.

Contributing to Debian or to Git?

> I have been using Git & GitHub as the primary version control tools
> for all of my projects and have been impressed with its stability,
> security, and flexibility. As a student, I am eager to contribute to
> this innovative and widely used distribution of Git and learn from
> experienced members of the Git community.
> However, I am new to the project and would appreciate guidance on how
> to contribute effectively. I have reviewed the Git documentation
> and familiarized myself with the project's goals and objectives.
> I would be grateful if you could provide me with some guidance on how
> to get started with contributing to Git. Specifically, I would
> appreciate any advice on how to identify good first issues, best
> practices for contributing code, and how to collaborate with the
> community effectively.

About good first issues, we have the following documentation:

https://git.github.io/General-Microproject-Information/

There is also the microproject idea page from last year's GSoC:

https://git.github.io/SoC-2022-Microprojects/

We haven't updated it for this year yet, so some ideas might be
outdated. It might be a good idea anyway to discuss a bit your
micro-project idea on the list when you have found one before starting
to work on it.

Thanks and welcome to the Git community,
Christian.

      reply	other threads:[~2023-02-20  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 20:26 Regarding candidature for Google Summer of Code 2023 Anushka Saxena
2023-02-20  9:46 ` Christian Couder [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

  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=CAP8UFD2bTBz2wTVjV+amtipQ-U78oW0ApE2pKCiLC+A1Nj_Z-A@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=anushka.saxena.iips@gmail.com \
    --cc=git@vger.kernel.org \
    /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).