git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: giovana.vmorais@gmail.com
Cc: git <git@vger.kernel.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [Outreachy] Introducing
Date: Mon, 1 Oct 2018 17:56:22 +0200	[thread overview]
Message-ID: <CAP8UFD0D5pu+6e25KeHFUKAFHf966tJ3j-3bhigFcSfr_UmVzg@mail.gmail.com> (raw)
In-Reply-To: <CAEdN-uV6giCp6FbC=J3B--6_kEzFkG8Yq4VXgGnhoNjERsXSQw@mail.gmail.com>

Hi Giovana,

On Mon, Oct 1, 2018 at 4:04 PM Giovana Morais <giovana.vmorais@gmail.com> wrote:
>
> Hey there, Christian and Git!
>
> My initial Outreachy application got accepted and, looking through available projects, I was really interested in `git bisect` one, since I want to take my C skills to a next level and, of course, have a deeper understanding of git itself. I think it will be a hard, but awesome challenge. (:

Great!

About possible projects there is also
https://git.github.io/Outreachy-17/ but only the `git bisect` has been
officially proposed as an Outreachy project. I hope Dscho (Johannes
Schindelin) will be ok to submit one of the 2 others soon and to
register himself as a mentor or co-mentor on some of the projects.
Please add him in CC, like I did in this email.

> I took a look at the patches already sent but I'm still lost of where I can start contributing. Can you guys give me some light?

We usually ask Outreachy and Google Summer of Code applicants to first
work on a micro-project before starting to work on a bigger project.
There is https://git.github.io/SoC-2018-Microprojects/ for that though
it is not up-to-date. Some micro-projects we propose might have
already been taken by GSoC students last winter/spring. Sorry we
didn't update the page or create another one. Anyway there are some
micro-projects there like "Add more builtin patterns for userdiff"
that are still valid and still good small tasks to get started working
on Git. And there are explanations about how you can search for
micro-projects (especially how to search for #leftoverbits on the
mailing list archive).

Thank you for your interest in contributing to Git,
Christian.



> Thanks a lot!
> --
> Giovana Vieira de Morais

           reply	other threads:[~2018-10-01 15:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAEdN-uV6giCp6FbC=J3B--6_kEzFkG8Yq4VXgGnhoNjERsXSQw@mail.gmail.com>]

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=CAP8UFD0D5pu+6e25KeHFUKAFHf966tJ3j-3bhigFcSfr_UmVzg@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=giovana.vmorais@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).