Re: Outreachy: request for a focused global-state migration task
- From
Usman Akinyemi <usmanakinyemi202@gmail.com>
- Date
- Oct 19, 2026, 16:39 UTC
- Message-ID
- <CAPSxiM_5J-LzAx6pkMrH1L08QX2hP5KgqWbmc6b1Oa2thboZBw@mail.gmail.com>
- In-Reply-To
- <CAKA8Uu1oLhdhNC9hGwMvQSC1+jzJqXnnWPGHLZUm5ZBdPkEM0A@mail.gmail.com>
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. >