git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Karina Saucedo <karina.saucedogza@gmail.com>
Cc: git <git@vger.kernel.org>, Emily Shaffer <emilyshaffer@google.com>
Subject: Re: Outreachy Winter 2019
Date: Tue, 22 Oct 2019 11:28:04 +0200	[thread overview]
Message-ID: <CAP8UFD0PGPVwq0vWq19knuQ_23ToOG-nqbgkJuCUXswtpQe48A@mail.gmail.com> (raw)
In-Reply-To: <CAJxDvStLi2usG_X7e8FeOSjKCXN4Yb+b_JCpUc8Y0HZ-GuTUgw@mail.gmail.com>

Hi Karina,

Please see my answer below.

On Mon, Oct 21, 2019 at 6:59 PM Karina Saucedo
<karina.saucedogza@gmail.com> wrote:
>
> Hello, my name is Karina and I'm and Outreachy applicant.
> I´m interested in applying to the project 'Add did you mean hints´ and
> I was wondering how can I start contributing since there seem to be no
> issues on the github page. Thank you!

Thank you for your introduction email and for your interest in Git!

Emily posted some interesting information on the Git mailing list that
you can see in the archives there:

https://public-inbox.org/git/20191007203654.GA20450@google.com/

We require Outreachy (and GSoC) applicants to work on a microproject
before they can be selected. There are microproject suggestions in
Emily's email and the following discussions.

Unfortunately we only have a web page that we prepared for the last
Google Summer of Code:

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

So it might not be up to date but you can still find interesting
information on top of what Emily posted.

Don't hesitate to ask if you have any further questions.

Best,
Christian.

  reply	other threads:[~2019-10-22  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 16:56 Outreachy Winter 2019 Karina Saucedo
2019-10-22  9:28 ` Christian Couder [this message]
     [not found] <CAJxDvSsZLz+oxPQ15YiGatURSyuxnriiL5TjXMay0W7VPVjNsQ@mail.gmail.com>
2019-10-21 18:43 ` Emily Shaffer

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=CAP8UFD0PGPVwq0vWq19knuQ_23ToOG-nqbgkJuCUXswtpQe48A@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=karina.saucedogza@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).