From: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>
Subject: Re: [Outreachy] internship contribution
Date: Mon, 10 Oct 2022 15:18:50 +0300 [thread overview]
Message-ID: <CA+PPyiF5KK6p7rv57YL_wsDO+WPifoRp1oe0F-6mo5NxLAwDWw@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1o5qxSvbV05DK_J=zbU=D_+HS0Q2ufEFSQVaBoWw_7Ow@mail.gmail.com>
I see most of the articles are UNIX based, does it mean that I should
have a UNIX based operating system in order to contribute?
Currently, I have windows installed 11 on my PC
On Mon, Oct 10, 2022 at 11:19 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> Hi Wilberforce,
>
> On Sun, Oct 9, 2022 at 6:46 AM NSENGIYUMVA WILBERFORCE
> <nsengiyumvawilberforce@gmail.com> wrote:
> >
> > Hi, I am Nsengiyumva Wilberforce From Uganda. I am happy that my first
> > application for outreachy internship was accepted.
> >
> > When I read about Git in the project list, I got interested and I will
> > be glad to be hooked into this community and get my hands dirty in
> > contributions. I am eager to learn new things from my mentor and the
> > entire community.
> >
> > I will be glad to hear from the community on some tips on how to get
> > started with contribution.
> >
> > And more so would like to get in touch with the my mentor
>
> As you also sent me a private message, I already replied privately.
> But for the public record and maybe other applicants for an Outreachy
> internship who might be interested in working on Git, we have
> information about how to get started contributing on the following
> pages:
>
> - https://git.github.io/Hacking-Git/
> - https://git.github.io/General-Microproject-Information/
>
> About microproject ideas, we haven't set up a specific page yet for
> this Outreachy round. Maybe we will do it but you shouldn't count on
> it. You can still take a look at the pages for the previous GSoC or
> Outreachy rounds like:
>
> - https://git.github.io/SoC-2022-Microprojects/
> - https://git.github.io/Outreachy-23-Microprojects/
> - https://git.github.io/SoC-2020-Microprojects/
>
> You will see that some ideas are quite generic and we propose them
> over and over as they are still valid.
>
> You are welcome to ask specific questions (publicly is preferred so
> that others can benefit).
>
> Thanks again for your interest in working on Git,
> Christian.
next prev parent reply other threads:[~2022-10-10 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 4:37 [Outreachy] internship contribution NSENGIYUMVA WILBERFORCE
2022-10-10 8:19 ` Christian Couder
2022-10-10 12:18 ` NSENGIYUMVA WILBERFORCE [this message]
2022-10-10 16:22 ` Christian Couder
2022-10-10 16:33 ` Derrick Stolee
2022-10-10 16:57 ` Luna Jernberg
2022-10-10 18:17 ` NSENGIYUMVA WILBERFORCE
2022-10-10 18:22 ` Derrick Stolee
2022-10-11 6:48 ` NSENGIYUMVA WILBERFORCE
2022-10-12 3:31 ` NSENGIYUMVA WILBERFORCE
2022-10-12 4:42 ` Junio C Hamano
2022-10-12 6:45 ` Đoàn Trần Công Danh
2022-10-12 10:37 ` NSENGIYUMVA WILBERFORCE
2022-10-12 14:21 ` Christian Couder
2022-10-12 15:18 ` Đoàn Trần Công Danh
2022-10-12 16:37 ` NSENGIYUMVA WILBERFORCE
[not found] ` <CA+fEeODMVNrnFRbuNVgbBShSA2Juo8Ux5ahd2J8nCfmPetdpvA@mail.gmail.com>
2022-10-13 10:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+PPyiF5KK6p7rv57YL_wsDO+WPifoRp1oe0F-6mo5NxLAwDWw@mail.gmail.com \
--to=nsengiyumvawilberforce@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@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.
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 NNTP newsgroup(s).