git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Rajni Jha <rajnikjha98@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Outreachy
Date: Mon, 7 Oct 2019 13:36:54 -0700	[thread overview]
Message-ID: <20191007203654.GA20450@google.com> (raw)
In-Reply-To: <CAAe2+-RUhQDuw2kR4xCh2Sjh0CvpuBsWtK2iLmHih1iWtcP60w@mail.gmail.com>

On Sun, Oct 06, 2019 at 01:32:54AM +0530, Rajni Jha wrote:
> Hello!
Welcome! Thank you for introducing yourself and please don't hesitate to
ask any questions you may have.

> 
> I am an outreachy applicant and I am looking forward to working with git
> for my outreachy internship.

Hope this will help you get started. The community discussed the list of
microprojects for applicants to try in this mailing list thread:
https://public-inbox.org/git/20190916184208.GB17913@google.com/
I don't think you need to wade through the replies on that thread to
determine whether the microproject you are interested in is available,
although you're certainly welcome to. You can also ask me if you see a
microproject you are interested in and I will be happy to help
summarize it and point you in the right direction :)

It is also probably a good idea for you to search that mailing list
archive for "[Outreachy]" so you can see what Outreachy interns have
done in the past and try to emulate how they submitted finished
microprojects. I also recommend that you read through
https://git-scm.com/docs/MyFirstContribution.html#ready-to-share to
learn how to share your code with us when you have finished.

 - Emily

       reply	other threads:[~2019-10-07 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAe2+-RUhQDuw2kR4xCh2Sjh0CvpuBsWtK2iLmHih1iWtcP60w@mail.gmail.com>
2019-10-07 20:36 ` Emily Shaffer [this message]
2019-10-08  8:27   ` Outreachy Johannes Schindelin
2020-10-15  7:03 Outreachy Zodwa Phakathi

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=20191007203654.GA20450@google.com \
    --to=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=rajnikjha98@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).