{"thread":{"id":"66587","subject":"Outreachy: request for a focused global-state migration task","startedAt":"2026-10-19T15:00:39Z","lastAt":"2026-10-20T20:15:24Z","messageCount":4,"participants":["Joy","Usman Akinyemi"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"555427","messageId":"CAKA8Uu1oLhdhNC9hGwMvQSC1+jzJqXnnWPGHLZUm5ZBdPkEM0A@mail.gmail.com","threadId":"66587","inReplyTo":null,"subject":"Outreachy: request for a focused global-state migration task","fromName":"Joy","fromEmail":"cryptocurrencydiva@gmail.com","sentAt":"2026-10-19T15:00:39Z","receivedAt":"2026-10-19T15:00:39Z","isPatch":false,"sender":{"key":"cryptocurrencydiva@gmail.com","avatar":null},"body":"I'm preparing my contribution for the Outreachy project, “Reduce Git's\nglobal state to enable Git's libification.”\n\nI've set up the Git development environment and studied the available\nmigrations into struct repo_config_values, including push_default and\nhas_symlinks. I also took a look at the abbreviation globals, but\nfound that minimum_abbrev is used across several components, so I\ndon't want to introduce a broad change without guidance.\n\nCould you recommend a small, well-scoped follow-up task suitable for a\nfirst contribution to this project?\n\nI'm happy to investigate the relevant code, implement the change, and\nrun the appropriate tests before submitting a patch for review.\n\nThank you for your guidance.\n\nBest regards,\nJoy Gundu\n\n"},{"id":"555437","messageId":"CAPSxiM_5J-LzAx6pkMrH1L08QX2hP5KgqWbmc6b1Oa2thboZBw@mail.gmail.com","threadId":"66587","inReplyTo":"CAKA8Uu1oLhdhNC9hGwMvQSC1+jzJqXnnWPGHLZUm5ZBdPkEM0A@mail.gmail.com","subject":"Re: Outreachy: request for a focused global-state migration task","fromName":"Usman Akinyemi","fromEmail":"usmanakinyemi202@gmail.com","sentAt":"2026-10-19T16:39:57Z","receivedAt":"2026-10-19T16:39:57Z","isPatch":false,"sender":{"key":"usmanakinyemi202@gmail.com","avatar":"https://avatars.githubusercontent.com/u/86585626?v=4"},"body":"> I've set up the Git development environment and studied the available\n> migrations into struct repo_config_values, including push_default and\n> has_symlinks. I also took a look at the abbreviation globals, but\n> found that minimum_abbrev is used across several components, so I\n> don't want to introduce a broad change without guidance.\n>\n> Could you recommend a small, well-scoped follow-up task suitable for a\n> first contribution to this project?\n\nQuoting Philip, this is the best approach and what you should know:\n\n\"\nThere are suggestions for microprojects at [1] and some additional\nguidance at [2]. The test conversions are a good way to get familiar\nwith our test suite. To check you're not working on the same thing as\nsomeone else you should scan the mailing list archives [3] and/or see\nwhat is in the \"seen\" branch. In many ways the main point of a\nmicroproject is to get candidates familiar with sending patches to the\nmailing list and interacting with reviewers. You've shown that you\nunderstand how to send patches, respond to comments and ask for help\neven if this particular patch (which looked very sensible) did not end\nup being merged.\n\nThanks\n\nPhillip\n\n[1] https://git.github.io/SoC-2026-Microprojects/\n[2] https://git.github.io/General-Microproject-Information/\n[3] https://lore.kernel.org/git\n\"\n\nThat above is relevant to you. Also, if you look at [1] above you will\nsee good issues\nthat are good for the first issue.\n>\n> I'm happy to investigate the relevant code, implement the change, and\n> run the appropriate tests before submitting a patch for review.\n>\n\n"},{"id":"555619","messageId":"CAPSxiM_GysceRRyEukVkUNhzvhsXcCKYsQXYmOyqa9kZO7kx-Q@mail.gmail.com","threadId":"66587","inReplyTo":"CAKA8Uu1P0Mtbf8GciaqN3g-9ttyKn7Gh-3Aa8F2hV1PCbGrvWA@mail.gmail.com","subject":"Re: Outreachy: request for a focused global-state migration task","fromName":"Usman Akinyemi","fromEmail":"usmanakinyemi202@gmail.com","sentAt":"2026-10-20T19:57:26Z","receivedAt":"2026-10-20T19:57:26Z","isPatch":false,"sender":{"key":"usmanakinyemi202@gmail.com","avatar":"https://avatars.githubusercontent.com/u/86585626?v=4"},"body":">\n> Quick question about microprojects\n>\n> Hi Usman,\nHello,\n>\n> Thanks again for your earlier guidance.\n>\n> I’ve submitted my patch to move pack.packsizelimit into the repository configuration as part of my work on the global-state project.\nI cannot find such a patch in the mailing list.\n>\n> I wanted to check whether this would count towards the microproject requirement, or if you’d recommend taking on a separate microproject as well.\n>\n> 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.\n\nGenerally, one microproject is what we requested for. But, previous\nsuccessful applicants\ndo send more patches after their microproject. Git is an opensource\nproject, you can always send\nyour patch.\n\n>\n> Thanks for your time!\n>\nThanks.\n> Best,\n> Joy\n>\n\n"},{"id":"555622","messageId":"CAKA8Uu2WZQ4J8+eaW3EJFQumRuhx25OFVsD1UCkRE6ouVDGBFQ@mail.gmail.com","threadId":"66587","inReplyTo":"CAKA8Uu1R5dUi0OLHA5CWVS40iE7yfkJFN8hbBuAMoYa8eQ7Usw@mail.gmail.com","subject":"Re: Outreachy: request for a focused global-state migration task","fromName":"Joy","fromEmail":"cryptocurrencydiva@gmail.com","sentAt":"2026-10-20T20:15:24Z","receivedAt":"2026-10-20T20:15:24Z","isPatch":false,"sender":{"key":"cryptocurrencydiva@gmail.com","avatar":null},"body":"Hi Usman,\n\nThanks for clarifying!\n\nI submitted my pack.packsizelimit patch through GitGitGadget. Here’s\nthe mailing-list thread:\nhttps://lore.kernel.org/git/pull.2271.git.1792522587065.gitgitgadget@gmail.com\n\nIt moves the pack size limit into the repository configuration as part\nof my work on the global-state project.\n\nWould this count towards the microproject requirement, or would you\nsuggest I work on a separate, smaller microproject first?\n\nI’ll wait for your advice before making any changes to the test-helper\nidea, as I noticed there’s already related work on the mailing list.\n\nThanks again for your help!\n\nBest,\nJoy\n\n\nOn Tue, Oct 20, 2026 at 9:10 PM Joy <cryptocurrencydiva@gmail.com> wrote:\n>\n> Hi Usman,\n>\n> Thanks for clarifying!\n>\n> 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\n>\n> It moves the pack size limit into the repository configuration as part of my work on the global-state project.\n>\n> Would this count towards the microproject requirement, or would you suggest I work on a separate, smaller microproject first?\n>\n> 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.\n>\n> Thanks again for your help!\n>\n> Best,\n> Joy\n>\n>\n> On Tue, Oct 20, 2026 at 8:57 PM Usman Akinyemi <usmanakinyemi202@gmail.com> wrote:\n>>\n>> >\n>> > Quick question about microprojects\n>> >\n>> > Hi Usman,\n>> Hello,\n>> >\n>> > Thanks again for your earlier guidance.\n>> >\n>> > I’ve submitted my patch to move pack.packsizelimit into the repository configuration as part of my work on the global-state project.\n>> I cannot find such a patch in the mailing list.\n>> >\n>> > I wanted to check whether this would count towards the microproject requirement, or if you’d recommend taking on a separate microproject as well.\n>> >\n>> > 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.\n>>\n>> Generally, one microproject is what we requested for. But, previous\n>> successful applicants\n>> do send more patches after their microproject. Git is an opensource\n>> project, you can always send\n>> your patch.\n>>\n>> >\n>> > Thanks for your time!\n>> >\n>> Thanks.\n>> > Best,\n>> > Joy\n>> >\n\n"}]}