Re: [Outreachy][RFC]: Final Applications expectations.

[Patrick Steinhardt <ps@pks.im>]

On Tue, Oct 22, 2024 at 11:45:14AM +0000, Usman Akinyemi wrote:
> Hello,
> 
> I hope you're doing well. As the deadline for the final Outreachy
> application is approaching (Oct 29), I had a few questions regarding
> submitting the final application, specifically for Git projects:
> 
> Is there a specific way we should record our contributions? For
> example, should we include a link to the public mailing list
> discussion of a patch?

Yes. In order to make it as easy as possible for us mentors I'd suggest
to provide a link to every patch series you have sent to the mailing
list in the context of Outreachy. It would also help us if you included
the current status, e.g. whether it has been merged to `master` or
`next`, as well as the commit ID with which things have been merged.

> Are there any community-specific questions or expectations we should
> be aware of?

We outline the details that should be included in your application at
[1]. The most important things are:

  - Your self-presentation.

  - An explanation of the project you want to tackle as well as a
    rough timeline of how you want to tackle it.

  - Links to the microprojects / other projects you have done during the
    initial Outreachy phase.

It is encouraged that you send the proposal/application to the Git
mailing list so that we can provide feedback on it, which also allows
you to iterate on it before the deadline. You can search our mailing
list for examples -- most of the recent proposals in the context of GSoC
for example had a "[GSOC][PROPOSAL]" tag.

[1]: https://git.github.io/General-Application-Information/

> How should we go about detailing the project timeline in our application?

We only expect a very rough timeline here. It should give you enough
ramp-up time to learn about the code area you'll be working in and then
give a rough idea for how things will be progressing. I'd recommend to
not be overeager -- it is fine if things take time, and Git is not the
fastest-moving project. Also, account for the time it will take you to
get knowledgeable in the area.

Of course, that timeline isn't binding at all. It rather serves as a
demonstration to us that you understand the project and what subtasks it
can be split into.

> Is there anything specific that mentors are looking for in the final
> application that we should take note of?

It would be nice if you mentioned anything that could conflict with the
internship up front. This includes things like you picking up a new job
during the internship, which may limit the time you have available to
work on projects.

Anything else should be mentioned in the link provided above, I guess.

> Thank you for your time and guidance!

Thanks, and please let me know in case you have further questions!

Patrick