From: Patrick Steinhardt <ps@pks.im>
To: Usman Akinyemi <usmanakinyemi202@gmail.com>
Cc: Neema Joju <neemajoju96@gmail.com>,
git@vger.kernel.org,
Phillip Wood Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [OutReachy] Introduction and Contribution Phase
Date: Thu, 10 Oct 2024 07:41:54 +0200 [thread overview]
Message-ID: <ZwdpHNOPKpi12n3e@pks.im> (raw)
In-Reply-To: <CAPSxiM_OssSLAGd1JC3UJ9Saorf4yxx9FtvnhpL4=hBrcoh8hw@mail.gmail.com>
On Thu, Oct 10, 2024 at 10:21:54AM +0530, Usman Akinyemi wrote:
> On Thu, Oct 10, 2024, 10:17 AM Neema Joju <neemajoju96@gmail.com> wrote:
>
> > Hi,
> > My name is Neema. Pronouns (she/her/hers).
> > I am an Outreachy applicant. Completed my initial application and am
> > currently in the contribution phase. Looking forward to working with
> > you.
> >
> > I have read through
> > https://git.github.io/General-Microproject-Information/,
> > https://git.github.io/General-Application-Information/ and
> > https://git.github.io/SoC-2024-Microprojects/.
> >
> > I am in the process of selecting a microproject. However, there are
> > some things I would like to clarify. As a part of outreachy
> > contribution phase, making one contribution is mandatory. In the
> > Project Contribution Information
> > [
> > https://www.outreachy.org/outreachy-dec-2024-internship-cohort/communities/git/
> > ]
> > section, an applicant has to complete a tutorial, microproject and
> > then make a contribution.
> > While I see detailed instructions regarding the microproject, there
> > aren't any regarding contributions. Is the microproject considered the
> > contribution? or are they separate entities?
> >
>
> Hi Neema, when you do the Microproject, you are also contributing to Git.
> The Microproject is all about making a contribution. You can also wait to
> hear more from the mentor.
No need to say much more than you did though, as what you've been saying
is exactly right :) The microproject is how applicants demonstrate their
ability to adapt to the workflow in the Git project. So this is how we
mentors ultimately decide which applicant is likely to be the best fit
for the Git project.
You are of course free to do additional changes after you have completed
the microproject to get more familiar with how things work. After all,
this is an open source project, so people are free to contribute at any
point in time. But this is not a requirement.
Patrick
next prev parent reply other threads:[~2024-10-10 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 4:46 [OutReachy] Introduction and Contribution Phase Neema Joju
[not found] ` <CAPSxiM_OssSLAGd1JC3UJ9Saorf4yxx9FtvnhpL4=hBrcoh8hw@mail.gmail.com>
2024-10-10 5:41 ` Patrick Steinhardt [this message]
2024-10-10 6:56 ` Neema Joju
2024-10-10 17:03 ` Junio C Hamano
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=ZwdpHNOPKpi12n3e@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=neemajoju96@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=usmanakinyemi202@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).