From: Junio C Hamano <gitster@pobox.com>
To: Neema Joju <neemajoju96@gmail.com>, Patrick Steinhardt <ps@pks.im>
Cc: Usman Akinyemi <usmanakinyemi202@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 10:03:07 -0700 [thread overview]
Message-ID: <xmqqiktzlwl0.fsf@gitster.g> (raw)
In-Reply-To: <ZwdpHNOPKpi12n3e@pks.im> (Patrick Steinhardt's message of "Thu, 10 Oct 2024 07:41:54 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> > ... 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.
> ...
> 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.
There seems to be a bit of confusion between what Outreachy wants to
see and what we need to see before adopting somebody as an Outreachy
intern.
I doubt Outreachy considers a microproject contribution qualifies as
the "required" contribution.
Instead of being a theme for a full 3-months internship, a
microproject is designed to be a bite-sized project, with which a
potential participant can experience the end-to-end contribution
process of proposing a change, polishing it while working with
others, and seeing the evolution of the proposed change through to
completion, without requiring technical skills or project specific
knowledge. It is primarily a "dip your toes in the water, learn how
things are done in the development community that may choose you as
an intern" practice session.
As Patrick said, it may still be a "contribution" from the Git
project's point of view, but it is not designed to be something that
qualifies as a "Contribution" they talk about when they say the
"Applicants are required to make a contribution" section in their
https://www.outreachy.org/docs/applicant/#make-contributions page.
prev parent reply other threads:[~2024-10-10 17:03 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
2024-10-10 6:56 ` Neema Joju
2024-10-10 17:03 ` Junio C Hamano [this message]
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=xmqqiktzlwl0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=neemajoju96@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--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).