From: Emily Shaffer <emilyshaffer@google.com>
To: Karina Saucedo <karina.saucedogza@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Outreachy Winter 2019
Date: Mon, 21 Oct 2019 11:43:20 -0700 [thread overview]
Message-ID: <20191021184320.GB139951@google.com> (raw)
In-Reply-To: <CAJxDvSsZLz+oxPQ15YiGatURSyuxnriiL5TjXMay0W7VPVjNsQ@mail.gmail.com>
On Mon, Oct 21, 2019 at 11:54:01AM -0500, Karina Saucedo 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!
Hi Karina!
It's best to start on a microproject; some of the other applicants are
already doing so as well. You can search this list for "outreachy" (try
it from public-inbox.org/git) to see some of the discussions with other
applicants and what they are or are not working on; there are also some
good-first-issues in the GitGitGadget bug tracker
(github.com/gitgitgadget/git/issues). Git project doesn't use Github to
organize bugs itself; the bug trackers are all abstractions of
conversation on the list (such as this one -
https://public-inbox.org/git/20190916184208.GB17913@google.com/ -
explaining some possible Outreachy microprojects).
Thanks and good luck - I'm the mentor for "Did you mean" so you can feel
free to ask me directly if there's something you're not sure of and you
don't want to ask the list. :) Although, of course the list will be
happy to answer your questions as well.
- Emily
next parent reply other threads:[~2019-10-21 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJxDvSsZLz+oxPQ15YiGatURSyuxnriiL5TjXMay0W7VPVjNsQ@mail.gmail.com>
2019-10-21 18:43 ` Emily Shaffer [this message]
2019-10-21 16:56 Outreachy Winter 2019 Karina Saucedo
2019-10-22 9:28 ` 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=20191021184320.GB139951@google.com \
--to=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).