From: Bello Olamide <belkid98@gmail.com>
To: git@vger.kernel.org, Usman Akinyemi <usmanakinyemi202@gmail.com>,
christian.couder@gmail.com
Subject: [Outrechy][RFC] Request for final application guides
Date: Mon, 27 Oct 2025 07:09:12 +0100 [thread overview]
Message-ID: <CAD=f0L-Pr9MtQ1=Wrm3tybZFWKDUtDpVcOahoFUgdVcGKJm7Vg@mail.gmail.com> (raw)
Hello, I hope you all are doing well.
I'd like to appreciate everyone including Christian, Junio,
Usman and Kristoffer for the guides and assistance during
this contribution phase.
The deadline for the final application is in exactly a week's time.
I'd like to know if there is any new information on how to submit
the final application as the Outreachy page requires us to record
a contribution by submitting a link to the contribution and also
submit a final application to the project.
While going through the mailing list for previous final applications,
I came across this thread
https://lore.kernel.org/git/CAPSxiM-kf8U=vzp5MoD3tUuOtnNjcCgPhLdriyeQo5CGf=EhyQ@mail.gmail.com/
where the main points regarding my questions were answered as follows.
1. We should use the link to the microprojects for the patch reviews as the
contribution link.
2. We should specify the current status of the patch, 'master' or 'next'
3. Send the final application to the mailing list for review which should
include an explanation of the project we want to tackle, links to the
microprojects and a rough estimate of the project timeline.
Is there any other information we should know of or this is good enough?
Thank you.
Bello
next reply other threads:[~2025-10-27 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 6:09 Bello Olamide [this message]
2025-10-27 7:40 ` [Outrechy][RFC] Request for final application guides Usman Akinyemi
2025-10-27 8:49 ` Bello Olamide
2025-10-27 8:15 ` Christian Couder
2025-10-27 8:58 ` Bello Olamide
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='CAD=f0L-Pr9MtQ1=Wrm3tybZFWKDUtDpVcOahoFUgdVcGKJm7Vg@mail.gmail.com' \
--to=belkid98@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--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.
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).