Re: [Outrechy][RFC] Request for final application guides

From: Christian Couder <christian.couder@gmail.com>
Date: Oct 27, 2025, 08:15 UTC
Message-ID: <CAP8UFD39hqkcy3WeOdS3Z_N8t5kMTipmE6-N_MwR6PhozZLfXg@mail.gmail.com>
In-Reply-To: <CAD=f0L-Pr9MtQ1=Wrm3tybZFWKDUtDpVcOahoFUgdVcGKJm7Vg@mail.gmail.com>

Hi,

On Mon, Oct 27, 2025 at 7:09 AM Bello Olamide <belkid98@gmail.com> wrote:

Show 10 quoted lines

>
> 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.

There is no new information. Most of the interesting information should already be on Outreachy's website and on:

https://git.github.io/General-Application-Information/

I would suggest fully reading that page again. You might find ideas about things you could add to your application.

> 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/

Patrick's suggestions are great

> 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'

Yeah, it's nice if you can give the object ID of the merge commits for patches that are merged into 'master' too. For those that aren't merged into 'master', the branch name (like it appears in Junio's "What's cooking from git.git ..." emails) is interesting.

> 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.

It's important to send the application soon, so we have time to review it and iterate on it (like for patches that are sent to the mailing list).

> Is there any other information we should know of or this is good enough?

I see that Usman just replied and gave good suggestions too. So I think you definitely have enough good material to help you prepare a good application.

Thanks.