{"thread":{"id":"66223","subject":"Participating in Outreachy's December 2026 cohort","startedAt":"2026-08-26T10:55:34Z","lastAt":"2026-10-05T18:19:08Z","messageCount":14,"participants":["Christian Couder","Usman Akinyemi","Kaartic Sivaraam","Pablo Sabater","Siddharth Asthana"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"551281","messageId":"CAP8UFD367UD=AomNVHEBnhY-2DQmqTNRcBX6NW7YZywWgOmxTQ@mail.gmail.com","threadId":"66223","inReplyTo":null,"subject":"Participating in Outreachy's December 2026 cohort","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-08-26T10:55:19Z","receivedAt":"2026-08-26T10:55:34Z","isPatch":false,"body":"Hi everyone,\n\nOpen Source communities have until September 11, 2026, at 4 pm UTC to\nsign up to participate as mentoring organizations in Outreachy's\nDecember 2026 cohort (see\nhttps://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).\nAnd (co)mentors have until that same time to submit project\ndescriptions.\n\nLast year the Git community mentored a single intern. For a long time\nGitHub or GitLab used to sponsor Outreachy interns working on Git, but\nlast year both declined to do it, so the intern was sponsored by the\nGit project itself.\n\nLet us know if you want to help as a (co)mentor or an Org Admin, if\nyou know a company that would sponsor an intern, if you have ideas for\nprojects that we could propose, or if you have an opinion on Git\nparticipating again this year, or on how we should select interns,\netc.\n\nI am likely to mentor and help as an Org Admin again this year unless\nwe decide not to participate.\n\nThanks.\n"},{"id":"551282","messageId":"CAPSxiM8Jet5+4YvgSwCTK92fTmqLMj73nupY1eskWWO8i08fvw@mail.gmail.com","threadId":"66223","inReplyTo":"CAP8UFD367UD=AomNVHEBnhY-2DQmqTNRcBX6NW7YZywWgOmxTQ@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Usman Akinyemi","fromEmail":"usmanakinyemi202@gmail.com","sentAt":"2026-08-26T11:39:39Z","receivedAt":"2026-08-26T11:39:51Z","isPatch":false,"body":"On Wed, Aug 26, 2026 at 4:29 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> Hi everyone,\nHello\n>\n> Open Source communities have until September 11, 2026, at 4 pm UTC to\n> sign up to participate as mentoring organizations in Outreachy's\n> December 2026 cohort (see\n> https://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).\n> And (co)mentors have until that same time to submit project\n> descriptions.\nI was already waiting for this.\n>\n> Last year the Git community mentored a single intern. For a long time\nAnd to add to this, the intern later went on to co-mentor a GSOC\nintern this year.\nAnd also will be presenting his project in the coming Git conference.\nI was also a previous\nOutreachy intern myself. Because of this, I believe the program is\nvery much valuable to the community.\n> GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n> last year both declined to do it, so the intern was sponsored by the\n> Git project itself.\n>\n> Let us know if you want to help as a (co)mentor or an Org Admin, if\n> you know a company that would sponsor an intern, if you have ideas for\n> projects that we could propose, or if you have an opinion on Git\n> participating again this year, or on how we should select interns,\n> etc.\nI will like to be a co-mentor again this year.\n>\n> I am likely to mentor and help as an Org Admin again this year unless\n> we decide not to participate.\n>\n> Thanks.\nThanks.\n>\n"},{"id":"551752","messageId":"4de9645c-f067-45bb-8168-1f660e11eb8d@gmail.com","threadId":"66223","inReplyTo":"CAP8UFD367UD=AomNVHEBnhY-2DQmqTNRcBX6NW7YZywWgOmxTQ@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-09-02T13:20:42Z","receivedAt":"2026-09-02T13:20:46Z","isPatch":false,"body":"Hi Christian,\n\nOn 8/26/26 16:25, Christian Couder wrote:\n> Hi everyone,\n> \n> Open Source communities have until September 11, 2026, at 4 pm UTC to\n> sign up to participate as mentoring organizations in Outreachy's\n> December 2026 cohort (see\n> https://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).\n> And (co)mentors have until that same time to submit project\n> descriptions.\n> \n> Last year the Git community mentored a single intern. For a long time\n> GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n> last year both declined to do it, so the intern was sponsored by the\n> Git project itself.\n> \n> Let us know if you want to help as a (co)mentor or an Org Admin, if\n> you know a company that would sponsor an intern, if you have ideas for\n> projects that we could propose, or if you have an opinion on Git\n> participating again this year, or on how we should select interns,\n> etc.\n> \n\nI too believe it would be great if Git could participate in Outreachy \nthis year.\n\nI would be willing to co-mentor a project this year. I could also help\nas an org admin if needed.\n\nAlso, Pablo was interested to volunteer as a co-mentor for Outreachy. \nI've added him in Cc.\n\n--\nSivaraam\n\n"},{"id":"551855","messageId":"DL5LWRORZMGW.P7YH0PPIJW93@gmail.com","threadId":"66223","inReplyTo":"4de9645c-f067-45bb-8168-1f660e11eb8d@gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Pablo Sabater","fromEmail":"pabloosabaterr@gmail.com","sentAt":"2026-09-03T10:24:48Z","receivedAt":"2026-09-03T10:24:54Z","isPatch":false,"body":"On Wed Sep 2, 2026 at 2:20 PM WEST, Kaartic Sivaraam wrote:\n> Hi Christian,\n>\n> On 8/26/26 16:25, Christian Couder wrote:\n>> Hi everyone,\n>> \n>> Open Source communities have until September 11, 2026, at 4 pm UTC to\n>> sign up to participate as mentoring organizations in Outreachy's\n>> December 2026 cohort (see\n>> https://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).\n>> And (co)mentors have until that same time to submit project\n>> descriptions.\n>> \n>> Last year the Git community mentored a single intern. For a long time\n>> GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n>> last year both declined to do it, so the intern was sponsored by the\n>> Git project itself.\n>> \n>> Let us know if you want to help as a (co)mentor or an Org Admin, if\n>> you know a company that would sponsor an intern, if you have ideas for\n>> projects that we could propose, or if you have an opinion on Git\n>> participating again this year, or on how we should select interns,\n>> etc.\n>> \n>\n> I too believe it would be great if Git could participate in Outreachy \n> this year.\n>\n> I would be willing to co-mentor a project this year. I could also help\n> as an org admin if needed.\n>\n> Also, Pablo was interested to volunteer as a co-mentor for Outreachy. \n> I've added him in Cc.\n>\n> --\n> Sivaraam\n\nHello,\n\nYes, I'd also like to volunteer as a co-mentor for Outreachy this year.\n\nAlthough I won't have as much time available as I did during the summer,\nnow that the university semester has started, I believe I can still make\nenough time to review and mentor.\n\nI do have exams in October and January, but they shouldn't make me \nunavailable for a whole week, so I don't expect them to be a problem.\n\nRegards,\nPablo\n"},{"id":"552024","messageId":"CAP8UFD0oYnoXgQ84wHbGg3+QhX78Ucn_CXXYOe8uFpReb7X1Ng@mail.gmail.com","threadId":"66223","inReplyTo":"CAP8UFD367UD=AomNVHEBnhY-2DQmqTNRcBX6NW7YZywWgOmxTQ@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-09-05T08:26:34Z","receivedAt":"2026-09-05T08:26:47Z","isPatch":false,"body":"On Wed, Aug 26, 2026 at 12:55 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n\n> Open Source communities have until September 11, 2026, at 4 pm UTC to\n> sign up to participate as mentoring organizations in Outreachy's\n> December 2026 cohort (see\n> https://www.outreachy.org/blog/2026-02-06/may-2026-call-for-mentoring-organizations/).\n> And (co)mentors have until that same time to submit project\n> descriptions.\n\nThank you Usman, Kaartic and Pablo for volunteering to co-mentor!\n\nAs no one objected to Git participating in Outreachy, I will submit a\nCommunity Application for Git very soon.\n\nWe will still have to sign up as mentors and find and submit projects\nfor interns to work on soon. We have until September 11, 2026, at 4 pm\nUTC, which is less than one week from now.\n\nI have been thinking about the following projects:\n\n1. Continue removing global state (and perhaps start libifying some\nparts of the code base).\n\nI think Tian Yuchen said there is not much work left related to\n\"environment.{c,h}\". So maybe we need to adjust the project compared\nto its previous description or maybe make it about actually libifying\nsome parts of the code base.\n\n2. Improve how command arguments and options are scanned and parsed.\n\nThere are still a number of places in the code base where command\narguments are scanned or parsed using ad hoc hand-rolled code instead\nof an existing API like the parse-options API or the early-scan API I\nrecently proposed in\nhttps://lore.kernel.org/git/20260902161047.476753-1-christian.couder@gmail.com/.\nThose pieces of ad hoc parsing or scanning code are often buggy and\ndifficult to maintain. I think porting them to an API while improving\nthat API if necessary can be an interesting project and bring a lot of\nlong term benefits to the project. As the parse-options API is already\nquite feature-full, there are likely some areas where porting the\nparsing code to it should be relatively easy which is newcomer\nfriendly.\n\nLet me know your opinion about these and if you have other project ideas.\n\n> Last year the Git community mentored a single intern. For a long time\n> GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n> last year both declined to do it, so the intern was sponsored by the\n> Git project itself.\n\nI will start poking people at GitLab about this, but it would be nice\nif we could get some kind of help with this regarding other companies\ntoo.\n\nThanks,\nChristian.\n"},{"id":"552307","messageId":"CAP8UFD1hAjtPuWL8asZ2LzEMJKHGh2oO73n_tsUSADtEHh9b-g@mail.gmail.com","threadId":"66223","inReplyTo":"CAP8UFD0oYnoXgQ84wHbGg3+QhX78Ucn_CXXYOe8uFpReb7X1Ng@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-09-09T09:12:03Z","receivedAt":"2026-09-09T09:12:16Z","isPatch":false,"body":"On Sat, Sep 5, 2026 at 10:26 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n\n> Thank you Usman, Kaartic and Pablo for volunteering to co-mentor!\n>\n> As no one objected to Git participating in Outreachy, I will submit a\n> Community Application for Git very soon.\n\nI have submitted a Community Application for Git, see:\n\nhttps://www.outreachy.org/communities/cfp/git/\n\nIt says that we are willing to mentor and sponsor 2 interns. Hopefully\nwe can have two (co-)mentors for each intern.\n\n> We will still have to sign up as mentors and find and submit projects\n> for interns to work on soon. We have until September 11, 2026, at 4 pm\n> UTC, which is less than one week from now.\n>\n> I have been thinking about the following projects:\n>\n> 1. Continue removing global state (and perhaps start libifying some\n> parts of the code base).\n>\n> I think Tian Yuchen said there is not much work left related to\n> \"environment.{c,h}\". So maybe we need to adjust the project compared\n> to its previous description or maybe make it about actually libifying\n> some parts of the code base.\n>\n> 2. Improve how command arguments and options are scanned and parsed.\n>\n> There are still a number of places in the code base where command\n> arguments are scanned or parsed using ad hoc hand-rolled code instead\n> of an existing API like the parse-options API or the early-scan API I\n> recently proposed in\n> https://lore.kernel.org/git/20260902161047.476753-1-christian.couder@gmail.com/.\n> Those pieces of ad hoc parsing or scanning code are often buggy and\n> difficult to maintain. I think porting them to an API while improving\n> that API if necessary can be an interesting project and bring a lot of\n> long term benefits to the project. As the parse-options API is already\n> quite feature-full, there are likely some areas where porting the\n> parsing code to it should be relatively easy which is newcomer\n> friendly.\n>\n> Let me know your opinion about these and if you have other project ideas.\n\nAs no other project ideas were suggested, I submitted the project\nideas I mentioned above. You can see them in the \"Approved Projects\nfor Git\" section of the above mentioned page\n(https://www.outreachy.org/communities/cfp/git/) as:\n\n- Improve how command arguments and options are scanned and parsed\n(https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#improve-how-command-arguments-and-options-are-scan)\n- Reduce Git’s global state to enable Git's libification\n(https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#reduce-gits-global-state-to-enable-gits-libificati)\n\nThe links to these projects are currently only available to approved\nmentors and coordinators. I applied to mentor both of these projects\nas this was required to submit the projects, but I am very much\nwilling to remove myself from mentoring one of these projects.\n\nSo please apply to (co-)mentor one of these projects, or submit other\nprojects you are willing to mentor if you prefer.\n\nAlso let me know if you see things that could be improved in these\nprojects or the Community Application for Git.\n\n> > Last year the Git community mentored a single intern. For a long time\n> > GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n> > last year both declined to do it, so the intern was sponsored by the\n> > Git project itself.\n>\n> I will start poking people at GitLab about this, but it would be nice\n> if we could get some kind of help with this regarding other companies\n> too.\n\nI have mentioned GitLab, GitHub and OpenAI as organizations that could\npotentially sponsor Outreachy interns. I have also proposed an\n\"Outreachy sponsoring\" topic to be discussed at the Git Contributor's\nSummit 2026 next week.\n\nThanks.\n"},{"id":"552668","messageId":"080f0485-3cf7-481a-8c39-c69afc81fbd8@gmail.com","threadId":"66223","inReplyTo":"CAP8UFD1hAjtPuWL8asZ2LzEMJKHGh2oO73n_tsUSADtEHh9b-g@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2026-09-14T06:38:54Z","receivedAt":"2026-09-14T06:39:00Z","isPatch":false,"body":"\n\nOn 09/09/26 14:42, Christian Couder wrote:\n> On Sat, Sep 5, 2026 at 10:26 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n> \n>> Thank you Usman, Kaartic and Pablo for volunteering to co-mentor!\n>>\n>> As no one objected to Git participating in Outreachy, I will submit a\n>> Community Application for Git very soon.\n> \n> I have submitted a Community Application for Git, see:\n> \n> https://www.outreachy.org/communities/cfp/git/\n> \n> It says that we are willing to mentor and sponsor 2 interns. Hopefully\n> we can have two (co-)mentors for each intern.\n> \n>> We will still have to sign up as mentors and find and submit projects\n>> for interns to work on soon. We have until September 11, 2026, at 4 pm\n>> UTC, which is less than one week from now.\n>>\n>> I have been thinking about the following projects:\n>>\n>> 1. Continue removing global state (and perhaps start libifying some\n>> parts of the code base).\n>>\n>> I think Tian Yuchen said there is not much work left related to\n>> \"environment.{c,h}\". So maybe we need to adjust the project compared\n>> to its previous description or maybe make it about actually libifying\n>> some parts of the code base.\n>>\n>> 2. Improve how command arguments and options are scanned and parsed.\n>>\n>> There are still a number of places in the code base where command\n>> arguments are scanned or parsed using ad hoc hand-rolled code instead\n>> of an existing API like the parse-options API or the early-scan API I\n>> recently proposed in\n>> https://lore.kernel.org/git/20260902161047.476753-1-christian.couder@gmail.com/.\n>> Those pieces of ad hoc parsing or scanning code are often buggy and\n>> difficult to maintain. I think porting them to an API while improving\n>> that API if necessary can be an interesting project and bring a lot of\n>> long term benefits to the project. As the parse-options API is already\n>> quite feature-full, there are likely some areas where porting the\n>> parsing code to it should be relatively easy which is newcomer\n>> friendly.\n>>\n>> Let me know your opinion about these and if you have other project ideas.\n> \n> As no other project ideas were suggested, I submitted the project\n> ideas I mentioned above. You can see them in the \"Approved Projects\n> for Git\" section of the above mentioned page\n> (https://www.outreachy.org/communities/cfp/git/) as:\n> \n> - Improve how command arguments and options are scanned and parsed\n> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#improve-how-command-arguments-and-options-are-scan)\n> - Reduce Git’s global state to enable Git's libification\n> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#reduce-gits-global-state-to-enable-gits-libificati)\n> \n> The links to these projects are currently only available to approved\n> mentors and coordinators. I applied to mentor both of these projects\n> as this was required to submit the projects, but I am very much\n> willing to remove myself from mentoring one of these projects.\n> \n> So please apply to (co-)mentor one of these projects, or submit other\n> projects you are willing to mentor if you prefer.\n\n\nApplied as co-mentor on the parse-options / early-scan one.\n\nThanks,\nSiddharth\n\n\n> \n> Also let me know if you see things that could be improved in these\n> projects or the Community Application for Git.\n> \n>>> Last year the Git community mentored a single intern. For a long time\n>>> GitHub or GitLab used to sponsor Outreachy interns working on Git, but\n>>> last year both declined to do it, so the intern was sponsored by the\n>>> Git project itself.\n>>\n>> I will start poking people at GitLab about this, but it would be nice\n>> if we could get some kind of help with this regarding other companies\n>> too.\n> \n> I have mentioned GitLab, GitHub and OpenAI as organizations that could\n> potentially sponsor Outreachy interns. I have also proposed an\n> \"Outreachy sponsoring\" topic to be discussed at the Git Contributor's\n> Summit 2026 next week.\n> \n> Thanks.\n\n"},{"id":"552682","messageId":"f2c1a858-e259-4e9f-a48f-f553f4d43153@gmail.com","threadId":"66223","inReplyTo":"080f0485-3cf7-481a-8c39-c69afc81fbd8@gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-09-14T08:24:44Z","receivedAt":"2026-09-14T08:24:50Z","isPatch":false,"body":"Hi Siddarth,\n\nOn 9/14/26 12:08, Siddharth Asthana wrote:\n>>\n>> The links to these projects are currently only available to approved\n>> mentors and coordinators. I applied to mentor both of these projects\n>> as this was required to submit the projects, but I am very much\n>> willing to remove myself from mentoring one of these projects.\n>>\n>> So please apply to (co-)mentor one of these projects, or submit other\n>> projects you are willing to mentor if you prefer.\n> \n> \n> Applied as co-mentor on the parse-options / early-scan one.\n> \n\nThank you for volunteering! I've approved you as a mentor for that project.\n\n-- \nSivaraam\n\n"},{"id":"552683","messageId":"DLEWITFIKFFK.NSANTRY5XBCB@gmail.com","threadId":"66223","inReplyTo":"CAP8UFD1hAjtPuWL8asZ2LzEMJKHGh2oO73n_tsUSADtEHh9b-g@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Pablo Sabater","fromEmail":"pabloosabaterr@gmail.com","sentAt":"2026-09-14T08:37:46Z","receivedAt":"2026-09-14T08:37:50Z","isPatch":false,"body":"On Wed Sep 9, 2026 at 10:12 AM WEST, Christian Couder wrote:\n> On Sat, Sep 5, 2026 at 10:26 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n>\n>> Let me know your opinion about these and if you have other project ideas.\n>\n> As no other project ideas were suggested, I submitted the project\n> ideas I mentioned above. You can see them in the \"Approved Projects\n> for Git\" section of the above mentioned page\n> (https://www.outreachy.org/communities/cfp/git/) as:\n>\n> - Improve how command arguments and options are scanned and parsed\n> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#improve-how-command-arguments-and-options-are-scan)\n> - Reduce Git’s global state to enable Git's libification\n> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#reduce-gits-global-state-to-enable-gits-libificati)\n>\n> The links to these projects are currently only available to approved\n> mentors and coordinators. I applied to mentor both of these projects\n> as this was required to submit the projects, but I am very much\n> willing to remove myself from mentoring one of these projects.\n>\n> So please apply to (co-)mentor one of these projects, or submit other\n> projects you are willing to mentor if you prefer.\n>\n> Also let me know if you see things that could be improved in these\n> projects or the Community Application for Git.\n>\n\nHello,\n\nI've applied as co-mentor for the libification one, this way we have at\nleast one mentor for each project.\n\nRegards,\nPablo\n"},{"id":"552688","messageId":"1b904e64-e681-4744-b83e-690f3ca94ea1@gmail.com","threadId":"66223","inReplyTo":"DLEWITFIKFFK.NSANTRY5XBCB@gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-09-14T09:41:07Z","receivedAt":"2026-09-14T09:41:13Z","isPatch":false,"body":"On 9/14/26 14:07, Pablo Sabater wrote:\n> \n> I've applied as co-mentor for the libification one, this way we have at\n> least one mentor for each project.\n>\n\nCool, Pablo. I've approved your application and also Usman's. Right now \nwe appear to have 2 mentors per project:\n\n   - Reduce Git’s global state to enable Git's libification\n\n     - Usman Akinyemi\n     - Pablo Sabater\n\n   - Improve how command arguments and options are scanned and parsed\n\n     - Christian Couder\n     - Siddarth Asthana\n\nGiven that we already have enough mentors for both the projects and I \nhave some bandwidth, I wonder if it would make sense to also propose the \nprojects that we proposed for GSoC but were not actually taken up by \nanyone. The following are the projects:\n\n   - Implement promisor remote fetch ordering\n\n   - Enhance promisor-remote protocol for better-connected remotes\n\nMore details regarding the project can be found here: \nhttps://git.github.io/SoC-2026-Ideas/\n\nThoughts?\n\n-- \nSivaraam\n\n"},{"id":"552800","messageId":"CAP8UFD3kd=6QHp2oB+t+g-2D8bY-Oe5+_Vk+RJeaCa_xhxGrsA@mail.gmail.com","threadId":"66223","inReplyTo":"1b904e64-e681-4744-b83e-690f3ca94ea1@gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-09-16T20:58:11Z","receivedAt":"2026-09-16T20:58:28Z","isPatch":false,"body":"On Mon, Sep 14, 2026 at 11:41 AM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> On 9/14/26 14:07, Pablo Sabater wrote:\n> >\n> > I've applied as co-mentor for the libification one, this way we have at\n> > least one mentor for each project.\n> >\n>\n> Cool, Pablo. I've approved your application and also Usman's. Right now\n> we appear to have 2 mentors per project:\n>\n>    - Reduce Git’s global state to enable Git's libification\n>\n>      - Usman Akinyemi\n>      - Pablo Sabater\n>\n>    - Improve how command arguments and options are scanned and parsed\n>\n>      - Christian Couder\n>      - Siddarth Asthana\n\nGreat, thanks!\n\n> Given that we already have enough mentors for both the projects and I\n> have some bandwidth, I wonder if it would make sense to also propose the\n> projects that we proposed for GSoC but were not actually taken up by\n> anyone. The following are the projects:\n>\n>    - Implement promisor remote fetch ordering\n\nI think it's indeed a good idea to propose this project, even if it\nseems more difficult than the other projects we already propose.\n\n>    - Enhance promisor-remote protocol for better-connected remotes\n\nThis one seems even more risky and difficult to me. I would suggest\nonly proposing the previous one.\n\nAnyway as you will mentor it, feel free to propose the project you prefer.\n\nThanks,\nChristian.\n"},{"id":"552809","messageId":"fbed7a60-57ab-439b-a550-2d2b76ff24c0@gmail.com","threadId":"66223","inReplyTo":"CAP8UFD3kd=6QHp2oB+t+g-2D8bY-Oe5+_Vk+RJeaCa_xhxGrsA@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-09-17T11:07:33Z","receivedAt":"2026-09-17T11:07:40Z","isPatch":false,"body":"On 9/17/26 02:28, Christian Couder wrote:\n> On Mon, Sep 14, 2026 at 11:41 AM Kaartic Sivaraam\n>>> I've applied as co-mentor for the libification one, this way we have at\n>>> least one mentor for each project.\n>>>\n>>\n>> Cool, Pablo. I've approved your application and also Usman's. Right now\n>> we appear to have 2 mentors per project:\n>>\n>>     - Reduce Git’s global state to enable Git's libification\n>>\n>>       - Usman Akinyemi\n>>       - Pablo Sabater\n>>\n>>     - Improve how command arguments and options are scanned and parsed\n>>\n>>       - Christian Couder\n>>       - Siddarth Asthana\n> \n> Great, thanks!\n> \n\nJust for clarity, this is tentative mentor allocation. We may need to \nshuffle it a little bit based on the applications we receive. We'll see \nhow it goes.\n\n>> Given that we already have enough mentors for both the projects and I\n>> have some bandwidth, I wonder if it would make sense to also propose the\n>> projects that we proposed for GSoC but were not actually taken up by\n>> anyone. The following are the projects:\n>>\n>>     - Implement promisor remote fetch ordering\n> \n> I think it's indeed a good idea to propose this project, even if it\n> seems more difficult than the other projects we already propose.\n>\n\nThank you, Christian! I have proposed the project. Kindly check and \napprove it at your convenience. We have until Oct. 5, 2026 at 4pm UTC to \napprove it.\n\nIf anyone is willing to co-mentor it, please chime in.\n\n>>     - Enhance promisor-remote protocol for better-connected remotes\n> \n> This one seems even more risky and difficult to me. I would suggest\n> only proposing the previous one.\n> \n\nCool. I've skipped it for now.\n\n> Anyway as you will mentor it, feel free to propose the project you prefer.\n>\n\nI will mentor it but may need some help / guidance from you as you have \na more experience with this area of the code. I hope that's fine.\n\n-- \nSivaraam\n\n"},{"id":"552879","messageId":"CAP8UFD2VutDBA54c1e5uiCjFB8v3Y6yS3MTtY2P6sM5+Z9y7PA@mail.gmail.com","threadId":"66223","inReplyTo":"fbed7a60-57ab-439b-a550-2d2b76ff24c0@gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-09-19T13:43:45Z","receivedAt":"2026-09-19T13:43:57Z","isPatch":false,"body":"On Thu, Sep 17, 2026 at 1:07 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n\n> Just for clarity, this is tentative mentor allocation. We may need to\n> shuffle it a little bit based on the applications we receive. We'll see\n> how it goes.\n\nYeah, let's see later how it goes.\n\n> >> Given that we already have enough mentors for both the projects and I\n> >> have some bandwidth, I wonder if it would make sense to also propose the\n> >> projects that we proposed for GSoC but were not actually taken up by\n> >> anyone. The following are the projects:\n> >>\n> >>     - Implement promisor remote fetch ordering\n> >\n> > I think it's indeed a good idea to propose this project, even if it\n> > seems more difficult than the other projects we already propose.\n> >\n>\n> Thank you, Christian! I have proposed the project. Kindly check and\n> approve it at your convenience. We have until Oct. 5, 2026 at 4pm UTC to\n> approve it.\n\nI have just approved it. Thanks again for proposing it.\n\n> If anyone is willing to co-mentor it, please chime in.\n\nSure, it would be nice if we could get another co-mentor.\n\n> I will mentor it but may need some help / guidance from you as you have\n> a more experience with this area of the code. I hope that's fine.\n\nYeah, I will definitely help, and I can probably even co-mentor, but\nlet's see if someone else is interested first.\n"},{"id":"554209","messageId":"DLX41DP10SBK.3JNC50ICRW1RO@gmail.com","threadId":"66223","inReplyTo":"CAP8UFD2VutDBA54c1e5uiCjFB8v3Y6yS3MTtY2P6sM5+Z9y7PA@mail.gmail.com","subject":"Re: Participating in Outreachy's December 2026 cohort","fromName":"Pablo Sabater","fromEmail":"pabloosabaterr@gmail.com","sentAt":"2026-10-05T18:19:08Z","receivedAt":"2026-10-05T18:19:08Z","isPatch":false,"body":"On Sat Sep 19, 2026 at 2:43 PM WEST, Christian Couder wrote:\n> On Thu, Sep 17, 2026 at 1:07 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n>\n\n[...]\n\nHi all,\n\nI wanted to let you know that I'm no longer sure I'll have the time\nneeded to properly co-mentor, and I'm worried about ruining an\nintern's experience.\n\nI'll still try to review patches and help where I can, but I think\nit's better if I'm not an official co-mentor.\n\nI'll wait before withdrawing on the Outreachy site, in case you'd like \nto reorganize things first.\n\nSorry for the change.\n\nRegards,\nPablo\n\n"}]}