Editing GSoC Project Ideas

I'd be very grateful if someone with write access could please update 
the description of "Refactoring in order to reduce Git’s global state" 
[1] to stop recommending moving settings from `environment.c` into 
`struct repository_settings`. That struct was originally added to hold 
config settings that were already lazily parsed. We've had a number of 
submissions that move eagerly parsed config settings into that struct 
where an invalid config setting causes git to start dying in unexpected 
places when the lazy parsing fails.

The current wording of the suggested microproject does not mention any 
of the subtleties involved which sets students up to fail. A better 
suggestion would be for them to look at what Bello Caleb Olamide has 
been doing in their Outreach project [2].

I haven't been following Stolee's work [3] on "git conifg list --type" 
closely but I think it introduces some functions to parse config 
settings gently. Those functions might enable us to parse some config 
settings lazy where the functions using the lazily parsed settings are 
already set up to return a error. Doing that would require careful 
analysis and should not be a blanket recommendation.

Thanks

Phillip

[1] https://git.github.io/SoC-2026-Ideas/
[2] 
https://lore.kernel.org/48821a3848bef25c13038be8377ad73e7c17a924.1771258573.git.belkid98@gmail.com (local)
[3] 
https://lore.kernel.org/pull.2044.v3.git.1771849615.gitgitgadget@gmail.com (local)