threads / discuss / 66587

Outreachy: request for a focused global-state migration task

Subject: Outreachy: request for a focused global-state migration task

## tl;dr

4 messages between Oct 19, 2026 and Oct 20, 2026.

replies: 3people: 2as markdown or json

Joy· Oct 19, 2026, 15:00 UTC · lore

I'm preparing my contribution for the Outreachy project, “Reduce Git's global state to enable Git's libification.”

I've set up the Git development environment and studied the available migrations into struct repo_config_values, including push_default and has_symlinks. I also took a look at the abbreviation globals, but found that minimum_abbrev is used across several components, so I don't want to introduce a broad change without guidance.

Could you recommend a small, well-scoped follow-up task suitable for a first contribution to this project?

I'm happy to investigate the relevant code, implement the change, and run the appropriate tests before submitting a patch for review.

Thank you for your guidance.

Best regards, Joy Gundu

Usman Akinyemi· Oct 19, 2026, 16:39 UTC · re: Joy · lore

Re: Outreachy: request for a focused global-state migration task

Show 8 quoted lines
> I've set up the Git development environment and studied the available
> migrations into struct repo_config_values, including push_default and
> has_symlinks. I also took a look at the abbreviation globals, but
> found that minimum_abbrev is used across several components, so I
> don't want to introduce a broad change without guidance.
>
> Could you recommend a small, well-scoped follow-up task suitable for a
> first contribution to this project?
Quoting Philip, this is the best approach and what you should know:

" There are suggestions for microprojects at [1] and some additional guidance at [2]. The test conversions are a good way to get familiar with our test suite. To check you're not working on the same thing as someone else you should scan the mailing list archives [3] and/or see what is in the "seen" branch. In many ways the main point of a microproject is to get candidates familiar with sending patches to the mailing list and interacting with reviewers. You've shown that you understand how to send patches, respond to comments and ask for help even if this particular patch (which looked very sensible) did not end up being merged.

Thanks
Phillip

[1] https://git.github.io/SoC-2026-Microprojects/ [2] https://git.github.io/General-Microproject-Information/ [3] https://lore.kernel.org/git "

That above is relevant to you. Also, if you look at [1] above you will see good issues that are good for the first issue.

>
> I'm happy to investigate the relevant code, implement the change, and
> run the appropriate tests before submitting a patch for review.
>
Usman Akinyemi· Oct 20, 2026, 19:57 UTC · lore

Re: Outreachy: request for a focused global-state migration task

>
> Quick question about microprojects
>
> Hi Usman,
Hello,
>
> Thanks again for your earlier guidance.
>
> I’ve submitted my patch to move pack.packsizelimit into the repository configuration as part of my work on the global-state project.
I cannot find such a patch in the mailing list.
>
> I wanted to check whether this would count towards the microproject requirement, or if you’d recommend taking on a separate microproject as well.
>
> If a separate task would be helpful, I noticed a couple of file and directory checks in t/t0200-gettext-basic.sh that might be worth converting to Git’s test helpers. I haven’t made any changes yet, so I’d appreciate your thoughts on whether that would be a good task to pursue.

Generally, one microproject is what we requested for. But, previous successful applicants do send more patches after their microproject. Git is an opensource project, you can always send your patch.

>
> Thanks for your time!
>
Thanks.
> Best,
> Joy
>
Joy· Oct 20, 2026, 20:15 UTC · lore

Re: Outreachy: request for a focused global-state migration task

Hi Usman,
Thanks for clarifying!

I submitted my pack.packsizelimit patch through GitGitGadget. Here’s the mailing-list thread: https://lore.kernel.org/git/pull.2271.git.1792522587065.gitgitgadget@gmail.com

It moves the pack size limit into the repository configuration as part of my work on the global-state project.

Would this count towards the microproject requirement, or would you suggest I work on a separate, smaller microproject first?

I’ll wait for your advice before making any changes to the test-helper idea, as I noticed there’s already related work on the mailing list.

Thanks again for your help!

Best, Joy

On Tue, Oct 20, 2026 at 9:10 PM Joy <cryptocurrencydiva@gmail.com> wrote:
Show 49 quoted lines
>
> Hi Usman,
>
> Thanks for clarifying!
>
> I submitted my pack.packsizelimit patch through GitGitGadget. Here’s the mailing-list thread: https://lore.kernel.org/git/pull.2271.git.1792522587065.gitgitgadget@gmail.com
>
> It moves the pack size limit into the repository configuration as part of my work on the global-state project.
>
> Would this count towards the microproject requirement, or would you suggest I work on a separate, smaller microproject first?
>
> I’ll wait for your advice before making any changes to the test-helper idea, as I noticed there’s already related work on the mailing list.
>
> Thanks again for your help!
>
> Best,
> Joy
>
>
> On Tue, Oct 20, 2026 at 8:57 PM Usman Akinyemi <usmanakinyemi202@gmail.com> wrote:
>>
>> >
>> > Quick question about microprojects
>> >
>> > Hi Usman,
>> Hello,
>> >
>> > Thanks again for your earlier guidance.
>> >
>> > I’ve submitted my patch to move pack.packsizelimit into the repository configuration as part of my work on the global-state project.
>> I cannot find such a patch in the mailing list.
>> >
>> > I wanted to check whether this would count towards the microproject requirement, or if you’d recommend taking on a separate microproject as well.
>> >
>> > If a separate task would be helpful, I noticed a couple of file and directory checks in t/t0200-gettext-basic.sh that might be worth converting to Git’s test helpers. I haven’t made any changes yet, so I’d appreciate your thoughts on whether that would be a good task to pursue.
>>
>> Generally, one microproject is what we requested for. But, previous
>> successful applicants
>> do send more patches after their microproject. Git is an opensource
>> project, you can always send
>> your patch.
>>
>> >
>> > Thanks for your time!
>> >
>> Thanks.
>> > Best,
>> > Joy
>> >

← back to recent threads