{"thread":{"id":"62828","subject":"Git in GSoC 2025","startedAt":"2025-01-19T10:13:45Z","lastAt":"2025-03-21T21:02:09Z","messageCount":52,"participants":["Kaartic Sivaraam","Patrick Steinhardt","Christian Couder","Karthik Nayak","shejialuo","Oswald Buddenhagen","Junio C Hamano","Ghanshyam Thakkar"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"510891","messageId":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","threadId":"62828","inReplyTo":null,"subject":"Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-01-19T10:13:29Z","receivedAt":"2025-01-19T10:13:45Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hello everyone,\n\nIt is that time of year. GSoC Org Applications for 2025 are open now[1].\nThey are due before Tuesday, February 11 at 1800 UTC. It's good to see \nthat few contributors have already started working on microprojects this \nyear :-)\n\nI could help as an Org Admin like previous years. I prefer not to\nvolunteer as a mentor this time owing to other commitments, though.\n\nThere are no noticeable changes to the program this year.\n\nThe GSoC contributor application period is March 24 - April 8, so\n(co-)mentors and org admins are already welcome to volunteer. As usual,\nwe also need project ideas to refresh our idea page from last year\n(https://git.github.io/SoC-2024-Ideas/). Feel free to share your\nthoughts and discuss. It would be great if we could come up with a good \nmix of small, medium and large projects.\n\nDo feel free to ask if there's anything that needs to be clarified.\n\nJust like previous year, there will be a GSoC Meetup in Brussels during\nFOSDEM weekend on Saturday, February 1st in the evening. If you are\naround, interested and haven't received the link to register directly\nfrom Google, let me know so I can send it to you.\n\n[1]: \nhttps://opensource.googleblog.com/2025/01/google-summer-of-code-2025-is-here.html\n\n-- \nSivaraam\n"},{"id":"510924","messageId":"Z432QXJb_TfzNBa2@pks.im","threadId":"62828","inReplyTo":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-20T07:07:53Z","receivedAt":"2025-01-20T07:07:59Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sun, Jan 19, 2025 at 03:43:29PM +0530, Kaartic Sivaraam wrote:\n> Hello everyone,\n> \n> It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> They are due before Tuesday, February 11 at 1800 UTC. It's good to see that\n> few contributors have already started working on microprojects this year :-)\n> \n> I could help as an Org Admin like previous years. I prefer not to\n> volunteer as a mentor this time owing to other commitments, though.\n\nThanks for your work, as usual!\n\n> There are no noticeable changes to the program this year.\n> \n> The GSoC contributor application period is March 24 - April 8, so\n> (co-)mentors and org admins are already welcome to volunteer. As usual,\n> we also need project ideas to refresh our idea page from last year\n> (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> thoughts and discuss. It would be great if we could come up with a good mix\n> of small, medium and large projects.\n> \n> Do feel free to ask if there's anything that needs to be clarified.\n> \n> Just like previous year, there will be a GSoC Meetup in Brussels during\n> FOSDEM weekend on Saturday, February 1st in the evening. If you are\n> around, interested and haven't received the link to register directly\n> from Google, let me know so I can send it to you.\n> \n> [1]: https://opensource.googleblog.com/2025/01/google-summer-of-code-2025-is-here.html\n\nI'd be happy to mentor this year again. A couple of ideas:\n\n - Consolidate ref-related functionality into git-refs(1). This would\n mean that we add new subcommands \"list\", \"get\", \"exists\", \"write\"\n and \"optimize\" to it so that we have a central place to manage refs\n overall. This would replace git-update-ref(1), git-for-each-ref(1)\n git-show-ref(1) as well as git-pack-ref(1), which would of course\n stay around for the foreseeable future.\n\n - Refactor \"environment.c\" such that more of its global state is\n instead stored locally, e.g. as part of `struct repository` or\n `struct repository_settings`.\n\n - Create a new command to query repository-level information,\n potentially making it machine-readable via for example JSON. This\n would move such information out of git-rev-parse(1), which is a\n somewhat weird home for it. It's something I have been thinking\n about quite a bit, but it wasn't ever discussed to the best of my\n knowledge. So maybe not a good fit.\n\nI'll keep on thinking about potential topics.\n\nPatrick\n"},{"id":"510934","messageId":"CAP8UFD3PkyaQBLYPryePk=e54VtsQwjbyvvTsKEBFJnns_jZyg@mail.gmail.com","threadId":"62828","inReplyTo":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-01-20T08:19:53Z","receivedAt":"2025-01-20T08:20:07Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Sun, Jan 19, 2025 at 11:13 AM Kaartic Sivaraam\n wrote:\n>\n> Hello everyone,\n>\n> It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> They are due before Tuesday, February 11 at 1800 UTC. It's good to see\n> that few contributors have already started working on microprojects this\n> year :-)\n>\n> I could help as an Org Admin like previous years. I prefer not to\n> volunteer as a mentor this time owing to other commitments, though.\n\nThanks for volunteering as an Org Admin and for this message!\n\n> There are no noticeable changes to the program this year.\n>\n> The GSoC contributor application period is March 24 - April 8, so\n> (co-)mentors and org admins are already welcome to volunteer.\n\nI am happy to mentor and to be Org Admin this year again.\n\n> As usual,\n> we also need project ideas to refresh our idea page from last year\n> (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> thoughts and discuss. It would be great if we could come up with a good\n> mix of small, medium and large projects.\n\nIt might be nice if we could refresh our microproject idea list too.\nMaybe we could add ideas related to removing the_repository or\ncompiling with -Wsign-compare?\n\n> Do feel free to ask if there's anything that needs to be clarified.\n>\n> Just like previous year, there will be a GSoC Meetup in Brussels during\n> FOSDEM weekend on Saturday, February 1st in the evening. If you are\n> around, interested and haven't received the link to register directly\n> from Google, let me know so I can send it to you.\n\nYeah, there might also be a GSoC Meetup in Madrid, Spain on Wednesday,\nJanuary 29th. People interested should let us know so we can send them\na link to an interest form they would have to complete.\n\nBest,\nChristian.\n"},{"id":"510937","messageId":"CAOLa=ZR4PAche0J+Lju3GRcKBDQYEkte9Zn6M10R5p+jXq53cg@mail.gmail.com","threadId":"62828","inReplyTo":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-01-20T10:12:32Z","receivedAt":"2025-01-20T10:12:35Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hello everyone,\n>\n> It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> They are due before Tuesday, February 11 at 1800 UTC. It's good to see\n> that few contributors have already started working on microprojects this\n> year :-)\n>\n> I could help as an Org Admin like previous years. I prefer not to\n> volunteer as a mentor this time owing to other commitments, though.\n\nThanks for volunteering again :)\n\n> There are no noticeable changes to the program this year.\n>\n> The GSoC contributor application period is March 24 - April 8, so\n> (co-)mentors and org admins are already welcome to volunteer. As usual,\n> we also need project ideas to refresh our idea page from last year\n> (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> thoughts and discuss. It would be great if we could come up with a good\n> mix of small, medium and large projects.\n>\n\nI'd be up for mentoring again this year. I see Patrick has posted some\nprojects already, I'll reply inline if I come up with something!\n\n> Do feel free to ask if there's anything that needs to be clarified.\n>\n> Just like previous year, there will be a GSoC Meetup in Brussels during\n> FOSDEM weekend on Saturday, February 1st in the evening. If you are\n> around, interested and haven't received the link to register directly\n> from Google, let me know so I can send it to you.\n>\n> [1]:\n> https://opensource.googleblog.com/2025/01/google-summer-of-code-2025-is-here.html\n>\n> --\n> Sivaraam\n"},{"id":"510941","messageId":"Z44u7od-mDiKcKVZ@pks.im","threadId":"62828","inReplyTo":"CAP8UFD3PkyaQBLYPryePk=e54VtsQwjbyvvTsKEBFJnns_jZyg@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-20T11:09:34Z","receivedAt":"2025-01-20T11:09:41Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Mon, Jan 20, 2025 at 09:19:53AM +0100, Christian Couder wrote:\n> > As usual,\n> > we also need project ideas to refresh our idea page from last year\n> > (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> > thoughts and discuss. It would be great if we could come up with a good\n> > mix of small, medium and large projects.\n> \n> It might be nice if we could refresh our microproject idea list too.\n> Maybe we could add ideas related to removing the_repository or\n> compiling with -Wsign-compare?\n\nYes, agreed, both of these projects make sense to me.\n\nI was wondering whether it might make sense to also move the list of\nmicroprojects into the Git project itself, e.g. as something like\n\"Documentation/Projects.txt\". This would make it easier for us to update\nthe list of long-running projects whenever a new project is added and\nmakes it easier for people to discover it.\n\nIt would also help to document consensus in the Git project. The file\nwould likely not always be 100% accurate, but it'd probably be more so\ncompared to tracking it out of our tree.\n\nPatrick\n"},{"id":"510947","messageId":"Z45PL3YEfX1NfM6O@ArchLinux","threadId":"62828","inReplyTo":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-01-20T13:27:11Z","receivedAt":"2025-01-20T13:25:53Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Sun, Jan 19, 2025 at 03:43:29PM +0530, Kaartic Sivaraam wrote:\n> Hello everyone,\n> \n> It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> They are due before Tuesday, February 11 at 1800 UTC. It's good to see that\n> few contributors have already started working on microprojects this year :-)\n> \n> I could help as an Org Admin like previous years. I prefer not to\n> volunteer as a mentor this time owing to other commitments, though.\n> \n\nThanks for volunteering again just like previous year.\n\n> There are no noticeable changes to the program this year.\n> \n> The GSoC contributor application period is March 24 - April 8, so\n> (co-)mentors and org admins are already welcome to volunteer. As usual,\n> we also need project ideas to refresh our idea page from last year\n> (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> thoughts and discuss. It would be great if we could come up with a good mix\n> of small, medium and large projects.\n> \n\nI'd like to mentor for GSoC this year. However, I think I could only\nco-mentor with others due to the following two reasons:\n\n1. I am still learning the internal things of Git.\n2. I could mentor the student during my off-work hours.\n\nThanks,\nJialuo\n"},{"id":"510948","messageId":"Z45R3YvA-ITWI9RS@ArchLinux","threadId":"62828","inReplyTo":"Z432QXJb_TfzNBa2@pks.im","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-01-20T13:38:37Z","receivedAt":"2025-01-20T13:37:19Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Mon, Jan 20, 2025 at 08:07:53AM +0100, Patrick Steinhardt wrote:\n> On Sun, Jan 19, 2025 at 03:43:29PM +0530, Kaartic Sivaraam wrote:\n> > Hello everyone,\n> > \n> > It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> > They are due before Tuesday, February 11 at 1800 UTC. It's good to see that\n> > few contributors have already started working on microprojects this year :-)\n> > \n> > I could help as an Org Admin like previous years. I prefer not to\n> > volunteer as a mentor this time owing to other commitments, though.\n> \n> Thanks for your work, as usual!\n> \n> > There are no noticeable changes to the program this year.\n> > \n> > The GSoC contributor application period is March 24 - April 8, so\n> > (co-)mentors and org admins are already welcome to volunteer. As usual,\n> > we also need project ideas to refresh our idea page from last year\n> > (https://git.github.io/SoC-2024-Ideas/). Feel free to share your\n> > thoughts and discuss. It would be great if we could come up with a good mix\n> > of small, medium and large projects.\n> > \n> > Do feel free to ask if there's anything that needs to be clarified.\n> > \n> > Just like previous year, there will be a GSoC Meetup in Brussels during\n> > FOSDEM weekend on Saturday, February 1st in the evening. If you are\n> > around, interested and haven't received the link to register directly\n> > from Google, let me know so I can send it to you.\n> > \n> > [1]: https://opensource.googleblog.com/2025/01/google-summer-of-code-2025-is-here.html\n> \n> I'd be happy to mentor this year again. A couple of ideas:\n> \n> - Consolidate ref-related functionality into git-refs(1). This would\n> mean that we add new subcommands \"list\", \"get\", \"exists\", \"write\"\n> and \"optimize\" to it so that we have a central place to manage refs\n> overall. This would replace git-update-ref(1), git-for-each-ref(1)\n> git-show-ref(1) as well as git-pack-ref(1), which would of course\n> stay around for the foreseeable future.\n> \n> - Refactor \"environment.c\" such that more of its global state is\n> instead stored locally, e.g. as part of `struct repository` or\n> `struct repository_settings`.\n\nI think this is a good project which is not too difficult for a student\nto finish. By refactoring \"environment.c\", we could slowly drop the\nglobal variable \"the_repository\". I'd like to co-mentor with this idea\nif possible.\n\nThanks,\nJialuo\n"},{"id":"510997","messageId":"Z4-JQp9uOP8ALT7R@ugly","threadId":"62828","inReplyTo":"Z432QXJb_TfzNBa2@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Oswald Buddenhagen","fromEmail":"oswald.buddenhagen@gmx.de","sentAt":"2025-01-21T11:47:14Z","receivedAt":"2025-01-21T11:47:19Z","isPatch":false,"sender":{"key":"oswald.buddenhagen@gmx.de","avatar":"https://avatars.githubusercontent.com/u/812380?v=4"},"body":"On Mon, Jan 20, 2025 at 08:07:53AM +0100, Patrick Steinhardt wrote:\n> - Create a new command to query repository-level information,\n\n> potentially making it machine-readable via for example JSON.\n>\nonly optionally, please. the current positional output (each line\ncorresponds to the respective query command) is much easier to deal with\nin shell scripts.\n\n> This\n> would move such information out of git-rev-parse(1), which is a\n> somewhat weird home for it. It's something I have been thinking\n> about quite a bit,\n\n> but it wasn't ever discussed to the best of my knowledge.\n>\nthat depends on what level of engagement counts as \"discussed\".\nhttps://lore.kernel.org/git/ZZbFGTkM8aR7MXQu@tanuki/\n\n\n"},{"id":"511018","messageId":"xmqqr04vzyz9.fsf@gitster.g","threadId":"62828","inReplyTo":"Z44u7od-mDiKcKVZ@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-21T20:35:54Z","receivedAt":"2025-01-21T20:35:57Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt writes:\n\n> I was wondering whether it might make sense to also move the list of\n> microprojects into the Git project itself, e.g. as something like\n> \"Documentation/Projects.txt\". This would make it easier for us to update\n> the list of long-running projects whenever a new project is added and\n> makes it easier for people to discover it.\n>\n> It would also help to document consensus in the Git project. The file\n> would likely not always be 100% accurate, but it'd probably be more so\n> compared to tracking it out of our tree.\n\nI am OK with the general idea, with one condition. Each item in the\nlist should have clear expiration date that makes it automatically\neligible to be dropped from there. Another uncurated list of random\nthings is not what I want to add to and carry in my tree (the other\nuncurated list of random things being the set of topic branches that\ngo stale without hitting 'next').\n\nThanks.\n\n\n"},{"id":"511231","messageId":"Z5c-jFA9OAT9x5s7@pks.im","threadId":"62828","inReplyTo":"CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-27T08:06:36Z","receivedAt":"2025-01-27T08:06:41Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Mon, Jan 27, 2025 at 12:19:26PM +0530, Kaartic Sivaraam wrote:\n> Hi Patrick, Christian, Karthik and Jialuo,\n> \n> Thank you very much for your interest in volunteering as a mentor!\n> \n> On Mon, Jan 20, 2025 at 12:37 PM Patrick Steinhardt wrote:\n> \n> > I'd be happy to mentor this year again. A couple of ideas:\n> >\n> >\n> Thank you for suggesting these ideas, Patrick! I've incorporated them into\n> a draft\n> ideas page for now. You can see them here:\n> \n> https://git.github.io/SoC-2025-Ideas/\n\nGreat, thanks a lot!\n\n> Kindly suggest any corrections to the description, project size /\n> difficulty as necessary.\n> I've mentioned potential mentors based on what I'm aware of so far.\n> \n> Patrick, Christian and Karthik, kindly mention the ideas that you're\n> interested to\n> mentor.\n> \n> While I have not included them as of yet, I wonder if the following ideas\n> which we\n> had last year[1] could still be retained this year:\n> \n> - Implement consistency checks for refs. The idea could be about\n> implementing further ref checks which Jialuo appears to be helping\n> out with. We could leave it if Jialuo prefers to continue working on\n> the same in a flow.\n\nThe biggest omission right now is the reftable backend, but that one I\nplan to work on myself in this release cycle.\n\nI'll leave it to Jialuo to decide whether there's anything else in this\ncontext that would make for a good GSoC project, as he's been the\nprimary driving force here.\n\n> - Refactor git-bisect(1) to make its state self-contained\n\nI'd rather remove that project. It would be nice to have it, but it\nfeels too risky for a GSoC project, and we have better ones.\n\n> - Implement support for reftables in \"dumb\" HTTP transport\n\nI'd be fine mentoring this project.\n\nPatrick\n"},{"id":"511241","messageId":"Z5d_XbPfQQBnwgQf@ArchLinux","threadId":"62828","inReplyTo":"Z5c-jFA9OAT9x5s7@pks.im","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-01-27T12:43:09Z","receivedAt":"2025-01-27T12:41:40Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Mon, Jan 27, 2025 at 09:06:36AM +0100, Patrick Steinhardt wrote:\n> On Mon, Jan 27, 2025 at 12:19:26PM +0530, Kaartic Sivaraam wrote:\n> > Hi Patrick, Christian, Karthik and Jialuo,\n> > \n> > Thank you very much for your interest in volunteering as a mentor!\n> > \n> > On Mon, Jan 20, 2025 at 12:37 PM Patrick Steinhardt wrote:\n> > \n> > > I'd be happy to mentor this year again. A couple of ideas:\n> > >\n> > >\n> > Thank you for suggesting these ideas, Patrick! I've incorporated them into\n> > a draft\n> > ideas page for now. You can see them here:\n> > \n> > https://git.github.io/SoC-2025-Ideas/\n> \n> Great, thanks a lot!\n> \n> > Kindly suggest any corrections to the description, project size /\n> > difficulty as necessary.\n> > I've mentioned potential mentors based on what I'm aware of so far.\n> > \n> > Patrick, Christian and Karthik, kindly mention the ideas that you're\n> > interested to\n> > mentor.\n> > \n> > While I have not included them as of yet, I wonder if the following ideas\n> > which we\n> > had last year[1] could still be retained this year:\n> > \n> > - Implement consistency checks for refs. The idea could be about\n> > implementing further ref checks which Jialuo appears to be helping\n> > out with. We could leave it if Jialuo prefers to continue working on\n> > the same in a flow.\n> \n> The biggest omission right now is the reftable backend, but that one I\n> plan to work on myself in this release cycle.\n> \n\nI am happy to see this. If you plan to work on this in this release\ncycle. I won't touch this. I'll review to learn more knowledge about\nreftable backend.\n\n> I'll leave it to Jialuo to decide whether there's anything else in this\n> context that would make for a good GSoC project, as he's been the\n> primary driving force here.\n> \n\nOne thing I could think about is to clean up \"git-fsck(1)\" to make the\nboundary between the ref checks and object checks clear which means we\nneed to remove unnecessary checks and reorder the program sequence.\nHowever, I think this is a little risky for a GSoC project. So, I'd like\nto implement this later on my own.\n\nThanks,\nJialuo\n"},{"id":"511358","messageId":"c39c5424-71d0-4b6d-90b1-a6a70f2ee61b@gmail.com","threadId":"62828","inReplyTo":"Z432QXJb_TfzNBa2@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-01-28T17:30:40Z","receivedAt":"2025-01-28T17:31:02Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"(Apologies for the delayed re-send. I just noticed that this one\n got dropped by the mailing list. I'll respond to existing replies\n in that thread)\n\nHi Patrick, Christian, Karthik and Jialuo,\n\nThank you very much for your interest in volunteering as a mentor!\n\nOn Mon, Jan 20, 2025 at 12:37 PM Patrick Steinhardt wrote:\n\n > I'd be happy to mentor this year again. A couple of ideas:\n\n\nThank you for suggesting these ideas, Patrick! I've incorporated them \ninto a draft ideas page for now. You can see them here:\n\nhttps://git.github.io/SoC-2025-Ideas/\n\nKindly suggest any corrections to the description, project size /\ndifficulty as necessary. I've mentioned potential mentors based on what\nI'm aware of so far.\n\nPatrick, Christian and Karthik, kindly mention the ideas that you're\ninterested to mentor.\n\nWhile I have not included them as of yet, I wonder if the following\nideas which we had last year[1] could still be retained this year:\n\n- Implement consistency checks for refs. The idea could be about\n implementing further ref checks which Jialuo appears to be helping\n out with. We could leave it if Jialuo prefers to continue working on\n the same in a flow.\n\n- Refactor git-bisect(1) to make its state self-contained\n\n- Implement support for reftables in \"dumb\" HTTP transport\n\nWould these be interesting ones to consider? Is anyone willing to\nmentor these this time around?\n\n\n > I'll keep on thinking about potential topics.\n\n\nSure. That would be great! Others could also chime in with your\npotential ideas. Also, do not hesitate to let us know if you're\ninterested in mentoring.\n\n-- \nSivaraam\n"},{"id":"511362","messageId":"ca0fcde5-72f7-4245-9536-c3b41bbde8a4@gmail.com","threadId":"62828","inReplyTo":"Z5c-jFA9OAT9x5s7@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-01-28T18:20:57Z","receivedAt":"2025-01-28T18:21:18Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Patrick and Jialuo,\n\nOn 27/01/25 13:36, Patrick Steinhardt wrote:\n> On Mon, Jan 27, 2025 at 12:19:26PM +0530, Kaartic Sivaraam wrote:\n>> While I have not included them as of yet, I wonder if the following ideas\n>> which we\n>> had last year[1] could still be retained this year:\n>>\n>> - Implement consistency checks for refs. The idea could be about\n>> implementing further ref checks which Jialuo appears to be helping\n>> out with. We could leave it if Jialuo prefers to continue working on\n>> the same in a flow.\n> \n> The biggest omission right now is the reftable backend, but that one I\n> plan to work on myself in this release cycle.\n> \n> I'll leave it to Jialuo to decide whether there's anything else in this\n> context that would make for a good GSoC project, as he's been the\n> primary driving force here.\n>\n\nGot it.\n\n>> - Refactor git-bisect(1) to make its state self-contained\n> \n> I'd rather remove that project. It would be nice to have it, but it\n> feels too risky for a GSoC project, and we have better ones.\n> \n\nOk. I'll leave it dropped.\n\n>> - Implement support for reftables in \"dumb\" HTTP transport\n> \n> I'd be fine mentoring this project.\n> \n\nSure. I'll include this one. I've retained Karthik as a co-mentor. \nKarthik, let me know in case of any concerns.\n\n\nOn 27/01/25 18:13, shejialuo wrote:\n > One thing I could think about is to clean up \"git-fsck(1)\" to make the\n > boundary between the ref checks and object checks clear which means we\n > need to remove unnecessary checks and reorder the program sequence.\n > However, I think this is a little risky for a GSoC project. So, I'd like\n > to implement this later on my own.\n\nDone. Thank you for your thoughts!\n\n--\nSivaraam\n"},{"id":"511462","messageId":"398978b6-6033-428c-993d-feba69334f8a@gmail.com","threadId":"62828","inReplyTo":"CAP8UFD3PkyaQBLYPryePk=e54VtsQwjbyvvTsKEBFJnns_jZyg@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-01-30T05:39:47Z","receivedAt":"2025-01-30T05:40:08Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Christian,\n\nOn 20/01/25 13:49, Christian Couder wrote:\n> \n> It might be nice if we could refresh our microproject idea list too.\n> Maybe we could add ideas related to removing the_repository or\n> compiling with -Wsign-compare?\n>\n\nThank you for your suggestion! I've incorporated the `-Wsign-compare`\nidea in the new microprojects page that I've created here:\n\n \nhttps://github.com/git/git.github.io/blob/2025-microprojects/SoC-2025-Microprojects.md#ideas-for-microprojects\n\nKindly check it and let me know your thoughts. Would it be possible for\nyou to add the 'the_repository' idea to the same? I could do that if you\ncould elaborate a bit on what we expect out of the microproject.\n\n--\nSivaraam\n"},{"id":"511464","messageId":"b784f612-4b6b-414a-9742-86611c50c55f@gmail.com","threadId":"62828","inReplyTo":"xmqqr04vzyz9.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-01-30T05:44:06Z","receivedAt":"2025-01-30T05:44:28Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Patrick and Junio,\n\nOn 22/01/25 02:05, Junio C Hamano wrote:\n> Patrick Steinhardt writes:\n> \n>> I was wondering whether it might make sense to also move the list of\n>> microprojects into the Git project itself, e.g. as something like\n>> \"Documentation/Projects.txt\". This would make it easier for us to update\n>> the list of long-running projects whenever a new project is added and\n>> makes it easier for people to discover it.\n>>\n>> It would also help to document consensus in the Git project. The file\n>> would likely not always be 100% accurate, but it'd probably be more so\n>> compared to tracking it out of our tree.\n> \n> I am OK with the general idea, with one condition. Each item in the\n> list should have clear expiration date that makes it automatically\n> eligible to be dropped from there. Another uncurated list of random\n> things is not what I want to add to and carry in my tree (the other\n> uncurated list of random things being the set of topic branches that\n> go stale without hitting 'next').\n> \n\nUnderstood. We could certainly curate it from time to time. I wonder how\nwe could set the timeline for a microproject idea, though. Would it make \nsense to fix a rough timeline such as 1 year or so and remove any idea\nwhose age is more than the same?\n\nAlso, the current list of ideas could roughly be seen here:\n\n \nhttps://github.com/git/git.github.io/blob/2025-microprojects/SoC-2025-Microprojects.md#ideas-for-microprojects\n\nThe topics are:\n\n - Fix Sign Comparison Warnings in Git's Codebase\n\n - Modernize Test Path Checking in Git's Test Suite\n\n - Add more builtin patterns for userdiff\n\n - Replace a run_command*() call by direct calls to C functions\n\n - Avoid suppressing git's exit code in test scripts\n\n - Use unsigned integral type for collection of bits.\n\n - Modernize a test script\n\nDo share your thoughts on which of these you find being relevant\ncurrently. That would help in preparing the first version of the in-tree\nproject ideas list.\n\n--\nSivaraam\n"},{"id":"511472","messageId":"Z5srHBSPKQlsuH53@pks.im","threadId":"62828","inReplyTo":"b784f612-4b6b-414a-9742-86611c50c55f@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-30T07:32:44Z","receivedAt":"2025-01-30T07:32:53Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Jan 30, 2025 at 11:14:06AM +0530, Kaartic Sivaraam wrote:\n> Hi Patrick and Junio,\n> \n> On 22/01/25 02:05, Junio C Hamano wrote:\n> > Patrick Steinhardt writes:\n> > \n> > > I was wondering whether it might make sense to also move the list of\n> > > microprojects into the Git project itself, e.g. as something like\n> > > \"Documentation/Projects.txt\". This would make it easier for us to update\n> > > the list of long-running projects whenever a new project is added and\n> > > makes it easier for people to discover it.\n> > > \n> > > It would also help to document consensus in the Git project. The file\n> > > would likely not always be 100% accurate, but it'd probably be more so\n> > > compared to tracking it out of our tree.\n> > \n> > I am OK with the general idea, with one condition. Each item in the\n> > list should have clear expiration date that makes it automatically\n> > eligible to be dropped from there. Another uncurated list of random\n> > things is not what I want to add to and carry in my tree (the other\n> > uncurated list of random things being the set of topic branches that\n> > go stale without hitting 'next').\n> > \n> \n> Understood. We could certainly curate it from time to time. I wonder how\n> we could set the timeline for a microproject idea, though. Would it make\n> sense to fix a rough timeline such as 1 year or so and remove any idea\n> whose age is more than the same?\n\nThat'd be fine with me. Ideas don't necessarily have to get removed\nimmediately, but may get \"refreshed\" in case they are still accurate.\nSo personally I'd frame it less like an expiration date and more like\nthe following:\n\n Every topic added to the list will need to be checked regularly for\n whether it is still accurate so that we can avoid an ever-growing\n list of stale topics. As such, every topic needs to be accompanied\n by a \"best-before\" date that indicates when the next check for this\n topic is due.\n\n It is the responsibility of the owner of the topic to determine\n whether it is still accurate. This check should happen close to the\n noted best-before date and come in the form of a patch that either\n bumps the date in case it _is_ accurate, or alternatively removes\n the topic from the list in case it is _not_ accurate anymore.\n\n In case the topic owner does not send such a patch, contributors\n other than the owner are encouraged to send a patch that removes the\n topic, putting the owner into Cc.\n\nWell... maybe it _is_ an expiration date. I dunno, I don't mind which\nexact term we use for it.\n\nIn any case, my proposal would be to add this paragraph or a variant\nthereof to a preamble explaining the purpose of the document as well as\nhow to use it. This is somewhat similar to how our \"BreakingChanges.txt\"\nlays out expectations, which I think should be an inspiration for the\nnew document, as well.\n\n> Also, the current list of ideas could roughly be seen here:\n> \n> \n> https://github.com/git/git.github.io/blob/2025-microprojects/SoC-2025-Microprojects.md#ideas-for-microprojects\n> \n> The topics are:\n> \n> - Fix Sign Comparison Warnings in Git's Codebase\n> \n> - Modernize Test Path Checking in Git's Test Suite\n> \n> - Add more builtin patterns for userdiff\n\nThis one doesn't feel like a sensible addition to me as it is\nopen-ended.\n\n> - Replace a run_command*() call by direct calls to C functions\n\nThis one, too.\n\n> - Avoid suppressing git's exit code in test scripts\n> \n> - Use unsigned integral type for collection of bits.\n> \n> - Modernize a test script\n> \n> Do share your thoughts on which of these you find being relevant\n> currently. That would help in preparing the first version of the in-tree\n> project ideas list.\n\nAll the other topics are ongoing topics indeed and would be a good fit\nfrom my perspective.\n\nNote that Chris is also preparing such a doc right now, so you might\nwant to coordinate with him.\n\nPatrick\n"},{"id":"511475","messageId":"CAP8UFD0s1nOr5EDx0MW=u7grpmywRTpGzx0v_d4PSjmgJ0ZBbQ@mail.gmail.com","threadId":"62828","inReplyTo":"Z5srHBSPKQlsuH53@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-01-30T08:37:47Z","receivedAt":"2025-01-30T08:38:02Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Jan 30, 2025 at 8:32 AM Patrick Steinhardt wrote:\n>\n> On Thu, Jan 30, 2025 at 11:14:06AM +0530, Kaartic Sivaraam wrote:\n\n> > We could certainly curate it from time to time. I wonder how\n> > we could set the timeline for a microproject idea, though. Would it make\n> > sense to fix a rough timeline such as 1 year or so and remove any idea\n> > whose age is more than the same?\n>\n> That'd be fine with me. Ideas don't necessarily have to get removed\n> immediately, but may get \"refreshed\" in case they are still accurate.\n> So personally I'd frame it less like an expiration date and more like\n> the following:\n>\n> Every topic added to the list will need to be checked regularly for\n> whether it is still accurate so that we can avoid an ever-growing\n> list of stale topics. As such, every topic needs to be accompanied\n> by a \"best-before\" date that indicates when the next check for this\n> topic is due.\n>\n> It is the responsibility of the owner of the topic to determine\n> whether it is still accurate. This check should happen close to the\n> noted best-before date and come in the form of a patch that either\n> bumps the date in case it _is_ accurate, or alternatively removes\n> the topic from the list in case it is _not_ accurate anymore.\n>\n> In case the topic owner does not send such a patch, contributors\n> other than the owner are encouraged to send a patch that removes the\n> topic, putting the owner into Cc.\n\nThanks for this. I will use something similar.\n\n> Well... maybe it _is_ an expiration date. I dunno, I don't mind which\n> exact term we use for it.\n\nI don't mind much either.\n\n> In any case, my proposal would be to add this paragraph or a variant\n> thereof to a preamble explaining the purpose of the document as well as\n> how to use it. This is somewhat similar to how our \"BreakingChanges.txt\"\n> lays out expectations, which I think should be an inspiration for the\n> new document, as well.\n\nSure.\n\n> > Also, the current list of ideas could roughly be seen here:\n> >\n> >\n> > https://github.com/git/git.github.io/blob/2025-microprojects/SoC-2025-Microprojects.md#ideas-for-microprojects\n> >\n> > The topics are:\n> >\n> > - Fix Sign Comparison Warnings in Git's Codebase\n> >\n> > - Modernize Test Path Checking in Git's Test Suite\n> >\n> > - Add more builtin patterns for userdiff\n>\n> This one doesn't feel like a sensible addition to me as it is\n> open-ended.\n>\n> > - Replace a run_command*() call by direct calls to C functions\n>\n> This one, too.\n\nWe could put those two in a section for projects that are a bit larger\nthan microprojects though. It might help those who have already worked\non a microproject and want to do something a bit more involved.\n\nIt happens more and more often that people who want to apply to the\nGSoC or Outreachy start getting involved early, which is nice. They\noften have time, after their microproject and before working on their\napplication, to work on something a bit more involved. So it would be\nnice if they could easily find something else to work on like those\ntwo ideas and others similar to them.\n\n> > - Avoid suppressing git's exit code in test scripts\n> >\n> > - Use unsigned integral type for collection of bits.\n> >\n> > - Modernize a test script\n> >\n> > Do share your thoughts on which of these you find being relevant\n> > currently. That would help in preparing the first version of the in-tree\n> > project ideas list.\n>\n> All the other topics are ongoing topics indeed and would be a good fit\n> from my perspective.\n\nI agree.\n\n> Note that Chris is also preparing such a doc right now, so you might\n> want to coordinate with him.\n\nYeah, I need to prepare a draft for the next Git Rev News edition\nfirst, but I will work on this really soon after.\n\nThanks.\n"},{"id":"511486","messageId":"Z5ta1wJ1NQ1EdLJD@pks.im","threadId":"62828","inReplyTo":"CAP8UFD0s1nOr5EDx0MW=u7grpmywRTpGzx0v_d4PSjmgJ0ZBbQ@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-30T10:56:23Z","receivedAt":"2025-01-30T10:56:28Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Jan 30, 2025 at 09:37:47AM +0100, Christian Couder wrote:\n> On Thu, Jan 30, 2025 at 8:32 AM Patrick Steinhardt wrote:\n> > This one doesn't feel like a sensible addition to me as it is\n> > open-ended.\n> >\n> > > - Replace a run_command*() call by direct calls to C functions\n> >\n> > This one, too.\n> \n> We could put those two in a section for projects that are a bit larger\n> than microprojects though. It might help those who have already worked\n> on a microproject and want to do something a bit more involved.\n> \n> It happens more and more often that people who want to apply to the\n> GSoC or Outreachy start getting involved early, which is nice. They\n> often have time, after their microproject and before working on their\n> application, to work on something a bit more involved. So it would be\n> nice if they could easily find something else to work on like those\n> two ideas and others similar to them.\n\nThe issue I have with these is less about the project size, but more\nabout them not being clearly defined. There is no easy way to identify\nsites that can be adapted, and neither is there a common understanding\nin the project that this is even something we want to do. So personally\nI'd leave them out of a first iteration so that we only have a set of\n\"trivial\" projects that are commonly accepted, which allows us to focus\non the form of the new document instead of bikeshedding the proposed\nprojects.\n\nWhich doesn't mean that we shouldn't discuss adding these projects at\nall. But I'd rather think that should be left for another iteration so\nthat we can discuss their scope and merit more in depth.\n\nPatrick\n"},{"id":"511519","messageId":"xmqqjzaccdpn.fsf@gitster.g","threadId":"62828","inReplyTo":"Z5srHBSPKQlsuH53@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-30T19:18:44Z","receivedAt":"2025-01-30T19:18:47Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt writes:\n\n> It is the responsibility of the owner of the topic to determine\n> whether it is still accurate. This check should happen close to the\n> noted best-before date and come in the form of a patch that either\n> bumps the date in case it _is_ accurate, or alternatively removes\n> the topic from the list in case it is _not_ accurate anymore.\n>\n> In case the topic owner does not send such a patch, contributors\n> other than the owner are encouraged to send a patch that removes the\n> topic, putting the owner into Cc.\n>\n> Well... maybe it _is_ an expiration date. I dunno, I don't mind which\n> exact term we use for it.\n\nI do not mind either word, either, but I have two small issues to\nraise:\n\n - Is each topic \"owned\" by some specific person? Would an owner\n retires from the project, would the leftover bits go away with\n the owner?\n\n - \"relevant\" may be a more appropriate adjective than \"accurate\".\n An item in the list may still accurately expresses somebody's\n wish, but because a better alternative has been implemented in\n the meantime, the feature-wish may no longer relevant.\n\n>> - Fix Sign Comparison Warnings in Git's Codebase\n\nThis one I am not sure if it is even something we want more of; a\ncareless \"-Wsign-compare\" squelching often makes the resulting code\nworse.\n\n>> - Add more builtin patterns for userdiff\n>\n> This one doesn't feel like a sensible addition to me as it is\n> open-ended.\n\nIf you add a list of missing types of documents and curate that\nlist, then it can evolve over time. Cobol may be on that list\nforever, while other minor languages may come and go.\n\n>> - Replace a run_command*() call by direct calls to C functions\n>\n> This one, too.\n\nThis one, too.\n"},{"id":"511525","messageId":"xmqqr04kaufo.fsf@gitster.g","threadId":"62828","inReplyTo":"xmqqjzaccdpn.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-30T21:00:27Z","receivedAt":"2025-01-30T21:00:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano writes:\n\n> I do not mind either word, either, but I have two small issues to\n> raise:\n>\n> - Is each topic \"owned\" by some specific person? Would an owner\n> retires from the project, would the leftover bits go away with\n> the owner?\n\nI obviously meant \"When an owner retires\", but more importantly, I\nshould have offered an alternative here, instead of just raising it\nas an issue.\n\nHow about making the rule a lot simpler?\n\n The expiration date kicks in _mechanically_, i.e. stale entries\n are unconditionally dropped at the date, based solely on the\n comparison between the timestamp and the wall clock.\n\nPeople are free to advocate for its continued existence, and when\nsuch an effort achieves a concensus among then-active members of the\ncommunity by the stated expiration date, a patch to update the\nentry's expiration date may be accepted, thereby prolonging its\nshelf life. Unless such a thing happens before the expiration date\ncomes, we will mechanically drop the entry.\n\nOf course people _can_ resurrect an expired entry later as a new\none when it seems appropriate.\n\nThat makes the decision to expire things from the list easy to make.\n\nThis is a tangent, perhaps we should adopt the same \"drop\nmechanically purely based on timestamp, but allow resuscitation\"\nrule for topic branches that take forever to hit 'next'. It would\nmake my life a little bit simpler ;-).\n\nThanks.\n\n"},{"id":"511534","messageId":"Z5xWLVFZhjUwcN16@pks.im","threadId":"62828","inReplyTo":"xmqqjzaccdpn.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-31T04:48:45Z","receivedAt":"2025-01-31T04:48:51Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Jan 30, 2025 at 11:18:44AM -0800, Junio C Hamano wrote:\n> Patrick Steinhardt writes:\n> > It is the responsibility of the owner of the topic to determine\n> > whether it is still accurate. This check should happen close to the\n> > noted best-before date and come in the form of a patch that either\n> > bumps the date in case it _is_ accurate, or alternatively removes\n> > the topic from the list in case it is _not_ accurate anymore.\n> >\n> > In case the topic owner does not send such a patch, contributors\n> > other than the owner are encouraged to send a patch that removes the\n> > topic, putting the owner into Cc.\n> >\n> > Well... maybe it _is_ an expiration date. I dunno, I don't mind which\n> > exact term we use for it.\n> \n> I do not mind either word, either, but I have two small issues to\n> raise:\n> \n> - Is each topic \"owned\" by some specific person? Would an owner\n> retires from the project, would the leftover bits go away with\n> the owner?\n\nGood point. \"Owner\" to me rather indicates who is the primary contact\nfor a specific topic. It doesn't mean that nobody else is allowed to\ncontribute to it, and neither does it say that the person has any kind\nof authority over it. So if that person doesn't care about the topic\nanymore due to whatever reason it's also fair to change the primary\ncontact to somebody else.\n\n> - \"relevant\" may be a more appropriate adjective than \"accurate\".\n> An item in the list may still accurately expresses somebody's\n> wish, but because a better alternative has been implemented in\n> the meantime, the feature-wish may no longer relevant.\n\nAgreed.\n\n> >> - Fix Sign Comparison Warnings in Git's Codebase\n> \n> This one I am not sure if it is even something we want more of; a\n> careless \"-Wsign-compare\" squelching often makes the resulting code\n> worse.\n\nThat's a fair remark indeed. We could add it, but add a warning that\nthese refactorings are non-trivial?\n\nPatrick\n"},{"id":"511535","messageId":"Z5xW57fsOCNcGViY@pks.im","threadId":"62828","inReplyTo":"xmqqr04kaufo.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-31T04:51:51Z","receivedAt":"2025-01-31T04:51:55Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Jan 30, 2025 at 01:00:27PM -0800, Junio C Hamano wrote:\n> Junio C Hamano writes:\n> \n> > I do not mind either word, either, but I have two small issues to\n> > raise:\n> >\n> > - Is each topic \"owned\" by some specific person? Would an owner\n> > retires from the project, would the leftover bits go away with\n> > the owner?\n> \n> I obviously meant \"When an owner retires\", but more importantly, I\n> should have offered an alternative here, instead of just raising it\n> as an issue.\n> \n> How about making the rule a lot simpler?\n> \n> The expiration date kicks in _mechanically_, i.e. stale entries\n> are unconditionally dropped at the date, based solely on the\n> comparison between the timestamp and the wall clock.\n> \n> People are free to advocate for its continued existence, and when\n> such an effort achieves a concensus among then-active members of the\n> community by the stated expiration date, a patch to update the\n> entry's expiration date may be accepted, thereby prolonging its\n> shelf life. Unless such a thing happens before the expiration date\n> comes, we will mechanically drop the entry.\n> \n> Of course people _can_ resurrect an expired entry later as a new\n> one when it seems appropriate.\n> \n> That makes the decision to expire things from the list easy to make.\n\nWorks for me. Ideally, as any other topic, the retirement should be sent\nto the mailing list as a normal patch series so that people may chime in\non the retirement and state reasons why they don't think that is a good\nidea.\n\nPatrick\n"},{"id":"511574","messageId":"xmqqtt9f9d8a.fsf@gitster.g","threadId":"62828","inReplyTo":"Z5xW57fsOCNcGViY@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-31T16:09:41Z","receivedAt":"2025-01-31T16:09:44Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt writes:\n\n>> How about making the rule a lot simpler?\n>> \n>> The expiration date kicks in _mechanically_, i.e. stale entries\n>> are unconditionally dropped at the date, based solely on the\n>> comparison between the timestamp and the wall clock.\n>> \n>> People are free to advocate for its continued existence, and when\n>> such an effort achieves a concensus among then-active members of the\n>> community by the stated expiration date, a patch to update the\n>> entry's expiration date may be accepted, thereby prolonging its\n>> shelf life. Unless such a thing happens before the expiration date\n>> comes, we will mechanically drop the entry.\n>> \n>> Of course people _can_ resurrect an expired entry later as a new\n>> one when it seems appropriate.\n>> \n>> That makes the decision to expire things from the list easy to make.\n>\n> Works for me. Ideally, as any other topic, the retirement should be sent\n> to the mailing list as a normal patch series so that people may chime in\n> on the retirement and state reasons why they don't think that is a good\n> idea.\n\nThat is the complete opposite of the ideal from my point of view.\nThe whole point of making the list items expire by default is that\nthe onus is on those who want to have them on list to justify why\nthese items must remain on the list. A patch to remove an item that\nhasn't had anybody advocating for its retention shouldn't have to be\nchimed in to be supported. There shouldn't even have to be a patch;\nthat is what I mean by \"stale entries expire mechanically by default\".\n\nThanks.\n\n\n"},{"id":"511657","messageId":"cd90cf17-6113-4634-a774-6df707b73e95@gmail.com","threadId":"62828","inReplyTo":"c39c5424-71d0-4b6d-90b1-a6a70f2ee61b@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-02T11:52:05Z","receivedAt":"2025-02-02T11:52:30Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hello Christian, Karthik, Jialuo, Patrick and all,\n\nOn 28/01/25 23:00, Kaartic Sivaraam wrote:\n> \n> Thank you for suggesting these ideas, Patrick! I've incorporated them \n> into a draft ideas page for now. You can see them here:\n> \n> https://git.github.io/SoC-2025-Ideas/\n> \n> Kindly suggest any corrections to the description, project size /\n> difficulty as necessary. I've mentioned potential mentors based on what\n> I'm aware of so far.\n> \n> Patrick, Christian and Karthik, kindly mention the ideas that you're\n> interested to mentor.\n> \n\nGentle reminder that the ideas list needs completion. Specifically, the\nfollowing ideas only list Patrick as a potential mentor:\n\n - Refactoring in order to reduce Git’s global state\n\n - Machine-Readable Repository Information Query Tool\n\nThe following idea mentions Karthik and Patrick as potential\nmentors.\n\n - Implement support for reftables in “dumb” HTTP transport\n\nThe following idea mentions Jialuo and Patrick as potential\nmentors.\n\n - Consolidate ref-related functionality into git-refs\n\nIt would helpful if you all could chime in to let me know if the\nexisting allocation is fine and to what other projects you need\nto be mentioned as potential mentors.\n\n--\nSivaraam\n"},{"id":"511722","messageId":"Z6CCNrNgatFMbMee@pks.im","threadId":"62828","inReplyTo":"cd90cf17-6113-4634-a774-6df707b73e95@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-02-03T08:45:42Z","receivedAt":"2025-02-03T08:45:48Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sun, Feb 02, 2025 at 05:22:05PM +0530, Kaartic Sivaraam wrote:\n> Hello Christian, Karthik, Jialuo, Patrick and all,\n> \n> On 28/01/25 23:00, Kaartic Sivaraam wrote:\n> > \n> > Thank you for suggesting these ideas, Patrick! I've incorporated them\n> > into a draft ideas page for now. You can see them here:\n> > \n> > https://git.github.io/SoC-2025-Ideas/\n> > \n> > Kindly suggest any corrections to the description, project size /\n> > difficulty as necessary. I've mentioned potential mentors based on what\n> > I'm aware of so far.\n> > \n> > Patrick, Christian and Karthik, kindly mention the ideas that you're\n> > interested to mentor.\n> > \n> \n> Gentle reminder that the ideas list needs completion. Specifically, the\n> following ideas only list Patrick as a potential mentor:\n\nThanks for the reminder!\n\n> - Refactoring in order to reduce Git’s global state\n> \n> - Machine-Readable Repository Information Query Tool\n\nI'll definitely need a co-mentor as I'll be out of office for two weeks\nin May. Otherwise we'll have to drop these two projects if nobody else\nwants to mentor them with me.\n\n> The following idea mentions Karthik and Patrick as potential\n> mentors.\n> \n> - Implement support for reftables in “dumb” HTTP transport\n> \n> The following idea mentions Jialuo and Patrick as potential\n> mentors.\n> \n> - Consolidate ref-related functionality into git-refs\n\nOverall it would also be nice if I wasn't mentoring in all projects :)\nI'm fine with being mentor in one project and co-mentor in another, but\ndon't think that I'll have the capacity to do more than that.\n\nPatrick\n"},{"id":"511723","messageId":"Z6CDFwtSRNz0OaM_@pks.im","threadId":"62828","inReplyTo":"xmqqtt9f9d8a.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-02-03T08:49:27Z","receivedAt":"2025-02-03T08:49:31Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Jan 31, 2025 at 08:09:41AM -0800, Junio C Hamano wrote:\n> Patrick Steinhardt writes:\n> \n> >> How about making the rule a lot simpler?\n> >> \n> >> The expiration date kicks in _mechanically_, i.e. stale entries\n> >> are unconditionally dropped at the date, based solely on the\n> >> comparison between the timestamp and the wall clock.\n> >> \n> >> People are free to advocate for its continued existence, and when\n> >> such an effort achieves a concensus among then-active members of the\n> >> community by the stated expiration date, a patch to update the\n> >> entry's expiration date may be accepted, thereby prolonging its\n> >> shelf life. Unless such a thing happens before the expiration date\n> >> comes, we will mechanically drop the entry.\n> >> \n> >> Of course people _can_ resurrect an expired entry later as a new\n> >> one when it seems appropriate.\n> >> \n> >> That makes the decision to expire things from the list easy to make.\n> >\n> > Works for me. Ideally, as any other topic, the retirement should be sent\n> > to the mailing list as a normal patch series so that people may chime in\n> > on the retirement and state reasons why they don't think that is a good\n> > idea.\n> \n> That is the complete opposite of the ideal from my point of view.\n> The whole point of making the list items expire by default is that\n> the onus is on those who want to have them on list to justify why\n> these items must remain on the list. A patch to remove an item that\n> hasn't had anybody advocating for its retention shouldn't have to be\n> chimed in to be supported. There shouldn't even have to be a patch;\n> that is what I mean by \"stale entries expire mechanically by default\".\n\nI completely agree, we were simply talking past one another :) Retiring\nan item from the list doesn't need any additional reason other than the\nexpiry date. But people can try to advocate for _keeping_ the item and\nextend the expiry date in case they have a good reason.\n\nPatrick\n"},{"id":"511728","messageId":"CAOLa=ZT7gOH-eu9gKDRyYJvzSDQ8pmMYqBxXFRdxbNN4iKZWvw@mail.gmail.com","threadId":"62828","inReplyTo":"cd90cf17-6113-4634-a774-6df707b73e95@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-02-03T11:53:45Z","receivedAt":"2025-02-03T11:53:46Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hello Christian, Karthik, Jialuo, Patrick and all,\n>\n> On 28/01/25 23:00, Kaartic Sivaraam wrote:\n>>\n>> Thank you for suggesting these ideas, Patrick! I've incorporated them\n>> into a draft ideas page for now. You can see them here:\n>>\n>> https://git.github.io/SoC-2025-Ideas/\n>>\n>> Kindly suggest any corrections to the description, project size /\n>> difficulty as necessary. I've mentioned potential mentors based on what\n>> I'm aware of so far.\n>>\n>> Patrick, Christian and Karthik, kindly mention the ideas that you're\n>> interested to mentor.\n>>\n>\n> Gentle reminder that the ideas list needs completion. Specifically, the\n> following ideas only list Patrick as a potential mentor:\n>\n\nSorry for the delay here, was OOO for a bit. Thanks for following up :)\n\n> - Refactoring in order to reduce Git’s global state\n>\n\nI've worked a bit on this and would be happy to mentor or co-mentor\nhere.\n\n> - Machine-Readable Repository Information Query Tool\n>\n\nHere too, I'm happy to co-mentor or mentor here.\n\nSo I could co-mentor one of these with Patrick, as I can cover when he's\nOOO.\n\n> The following idea mentions Karthik and Patrick as potential\n> mentors.\n>\n> - Implement support for reftables in “dumb” HTTP transport\n>\n\nI don't have a bunch of knowledge here, so I could co-mentor but not\nmentor by myself.\n\n> The following idea mentions Jialuo and Patrick as potential\n> mentors.\n>\n> - Consolidate ref-related functionality into git-refs\n>\n> It would helpful if you all could chime in to let me know if the\n> existing allocation is fine and to what other projects you need\n> to be mentioned as potential mentors.\n>\n> --\n> Sivaraam\n\nOverall, I should be able to cover a maximum of 2 projects (with at\nleast one as a co-mentor).\n\nThanks for putting this together.\n\nKarthik\n"},{"id":"511732","messageId":"xmqqtt9byxia.fsf@gitster.g","threadId":"62828","inReplyTo":"Z44u7od-mDiKcKVZ@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-02-03T13:21:33Z","receivedAt":"2025-02-03T13:21:36Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt writes:\n\n> I was wondering whether it might make sense to also move the list of\n> microprojects into the Git project itself, e.g. as something like\n> \"Documentation/Projects.txt\". This would make it easier for us to update\n> the list of long-running projects whenever a new project is added and\n> makes it easier for people to discover it.\n\nI am starting to have a second thought on this.\n\nStepping back a bit, if we were to do this, it is very likely that\nI'll let the patches (to add or update entries) sit on the mailing\nlist until the discussion beats the horse to death and then apply\nthe final version _directly_ on 'master', as such a document is\nreally not worth spending our usual \"cook in 'next' for a week to\nshake out problems\" mode of operation that eats quite a lot of\nbraincycles out of the maintainer and to a smaller degree, other\nauthors that make overlapping contributions. And this thing, being\na single document, is *DESIGNED* to force all authors to make\noverlapping contributions (and an \"easy to enter\" contributions at\nthat) that will cause conflicts.\n\nBut if we are to have a single document that records a list\ndiscussion consensus *after* the consensus is reached, it does not\nreally have to be _me_ the maintainer to do the record-keeper. And\npushing as much busywork as possible out of my plate would be a good\nthing to ensure that the project scales. Even today, we have a lot\nmore folks who generate patches than those who can process patches\nby vetting, polishing, finding problems in, making sure they play\nwell with other topics, etc.\n\nI wonder if this is better managed as either a separate tree (like\nthe 'todo' branch that houses \"What's cooking\" reports among other\nthings) with history disjoint from the main project, or even a\nseparate Wiki?\n\nThanks.\n\n\n"},{"id":"511776","messageId":"Z6F7ntBsp1CSflkL@ArchLinux","threadId":"62828","inReplyTo":"cd90cf17-6113-4634-a774-6df707b73e95@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-02-04T02:29:50Z","receivedAt":"2025-02-04T02:28:11Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Sun, Feb 02, 2025 at 05:22:05PM +0530, Kaartic Sivaraam wrote:\n> Hello Christian, Karthik, Jialuo, Patrick and all,\n> \n> On 28/01/25 23:00, Kaartic Sivaraam wrote:\n> > \n> > Thank you for suggesting these ideas, Patrick! I've incorporated them\n> > into a draft ideas page for now. You can see them here:\n> > \n> > https://git.github.io/SoC-2025-Ideas/\n> > \n> > Kindly suggest any corrections to the description, project size /\n> > difficulty as necessary. I've mentioned potential mentors based on what\n> > I'm aware of so far.\n> > \n> > Patrick, Christian and Karthik, kindly mention the ideas that you're\n> > interested to mentor.\n> > \n> \n> Gentle reminder that the ideas list needs completion. Specifically, the\n> following ideas only list Patrick as a potential mentor:\n> \n\nThanks for the reminder.\n\n> - Refactoring in order to reduce Git’s global state\n> \n\nAlthough I never code for this, I have reviewed a lot of patches others\nwork on. So, I think I could co-mentor this.\n\n> - Machine-Readable Repository Information Query Tool\n> \n> The following idea mentions Karthik and Patrick as potential\n> mentors.\n> \n> - Implement support for reftables in “dumb” HTTP transport\n> \n> The following idea mentions Jialuo and Patrick as potential\n> mentors.\n> \n> - Consolidate ref-related functionality into git-refs\n> \n\nI am OK wth this.\n\n> It would helpful if you all could chime in to let me know if the\n> existing allocation is fine and to what other projects you need\n> to be mentioned as potential mentors.\n> \n\nIn conclusion, I could cover two projects as a co-mentor.\n\nThanks,\nJialuo\n\n> --\n> Sivaraam\n"},{"id":"511822","messageId":"d5cba1a9-fe51-4f3f-970b-3ef8a7a2e459@gmail.com","threadId":"62828","inReplyTo":"cd90cf17-6113-4634-a774-6df707b73e95@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-04T18:33:34Z","receivedAt":"2025-02-04T18:33:59Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Patrick, Karthik, Jialuo and all,\n\nOn 02/02/25 17:22, Kaartic Sivaraam wrote:\n> \n> Gentle reminder that the ideas list needs completion. \n\nThank you for your responses! The updated assignment is as\nfollows:\n\n- Consolidate ref-related functionality into git-refs\n\n Possible mentors:\n * Patrick Steinhardt\n * Jialuo She\n\n- Refactoring in order to reduce Git's global state\n\n Possible mentors:\n * Patrick Steinhardt\n * Karthik Nayak\n * Jialuo She\n\n- Machine-Readable Repository Information Query Tool\n\n Possible mentors:\n * Patrick Steinhardt\n * Karthik Nayak\n\n- Implement support for reftables in \"dumb\" HTTP transport\n\n Possible mentors:\n * Patrick Steinhardt\n * Karthik Nayak\n\nNote that I haven't assigned any mentors / co-mentors for each project. \nI suppose we could assign that based on the applications we receive and \nthe ideas that we end up selecting.\n\nBased on Christian's inputs, we should be able to distribute\nprojects among mentors well.\n\n--\nSivaraam\n"},{"id":"511823","messageId":"cde4132d-fd6f-4f83-adb4-7ea124b6f09f@gmail.com","threadId":"62828","inReplyTo":"xmqqtt9byxia.fsf@gitster.g","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-04T18:36:32Z","receivedAt":"2025-02-04T18:36:56Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 03/02/25 18:51, Junio C Hamano wrote:\n> Patrick Steinhardt writes:\n> \n>> I was wondering whether it might make sense to also move the list of\n>> microprojects into the Git project itself, e.g. as something like\n>> \"Documentation/Projects.txt\". This would make it easier for us to update\n>> the list of long-running projects whenever a new project is added and\n>> makes it easier for people to discover it.\n> \n> I wonder if this is better managed as either a separate tree (like\n> the 'todo' branch that houses \"What's cooking\" reports among other\n> things) with history disjoint from the main project, or even a\n> separate Wiki?\n>\n\nJust to cross-check this, isn't the current home for this file,\nhttp://git.github.io, already a separate wiki of sorts? The site's\ndescription literally says something along the same lines:\n\n > These pages are intended to be edited collaboratively (i.e., it is an\n > alternative to us having a wiki, but one that is edited entirely via\n > Git pushes. The repository could be found on GitHub.\n\nSo, do you think if it would be fine to leave it where it currently is?\n\n\n[[ References ]]\n\n[1]: https://git.github.io/\n\n--\nSivaraam\n\n"},{"id":"511871","messageId":"CAP8UFD0GEmsJDFzVAV1bgBNeD6K3auH4paWEKE6=f0=_E6gifA@mail.gmail.com","threadId":"62828","inReplyTo":"d5cba1a9-fe51-4f3f-970b-3ef8a7a2e459@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-02-05T13:20:00Z","receivedAt":"2025-02-05T13:20:14Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Kaartic and all,\n\nOn Tue, Feb 4, 2025 at 7:33 PM Kaartic Sivaraam\n wrote:\n\n> - Consolidate ref-related functionality into git-refs\n>\n> Possible mentors:\n> * Patrick Steinhardt\n> * Jialuo She\n\nI have just added myself as a possible mentor. If possible I'd like to\njust co-mentor this project and someone else to be the main mentor for\nthis project.\n\n> - Refactoring in order to reduce Git's global state\n>\n> Possible mentors:\n> * Patrick Steinhardt\n> * Karthik Nayak\n> * Jialuo She\n\nI have just added myself as a possible mentor. If possible I'd like to\nbe the main mentor for this project.\n\n> Note that I haven't assigned any mentors / co-mentors for each project.\n> I suppose we could assign that based on the applications we receive and\n> the ideas that we end up selecting.\n>\n> Based on Christian's inputs, we should be able to distribute\n> projects among mentors well.\n\nYeah, I hope it will be possible to distribute projects among mentors well.\n\nThanks for working on this!\n"},{"id":"512037","messageId":"a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com","threadId":"62828","inReplyTo":"CAP8UFD0GEmsJDFzVAV1bgBNeD6K3auH4paWEKE6=f0=_E6gifA@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-07T07:32:25Z","receivedAt":"2025-02-07T07:32:51Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Christian, Karthik, Patrick, Jialuo and all,\n\nOn 05/02/25 18:50, Christian Couder wrote:\n> Hi Kaartic and all,\n> \n> On Tue, Feb 4, 2025 at 7:33 PM Kaartic Sivaraam\n> wrote:\n> \n> I have just added myself as a possible mentor. If possible I'd like to\n> just co-mentor this project and someone else to be the main mentor for\n> this project.\n> \n > ...\n> \n> I have just added myself as a possible mentor. If possible I'd like to\n> be the main mentor for this project.\n> \n\nThank you for adding yourself as a potential mentor!\n\nWith this, it seems to me like we could at the max. accept 3 students\n\n>> Note that I haven't assigned any mentors / co-mentors for each project.\n>> I suppose we could assign that based on the applications we receive and\n>> the ideas that we end up selecting.\n>>\n>> Based on Christian's inputs, we should be able to distribute\n>> projects among mentors well.\n> \n> Yeah, I hope it will be possible to distribute projects among mentors well.\n>\n\nIndeed. From all of your inputs I was able to come to the following\nallocation of mentor / co-mentor.\n\n-- 8< --\n\nConsolidate ref-related functionality into git-refs\n\n- Mentor: Patrick\n- Co-mentor: Jialuo / Christian\n\nRefactoring in order to reduce Git’s global state\n\n- Mentor: Christian\n- Co-mentor: Karthik / Jialuo\n\nMachine-Readable Repository Information Query Tool\n\n- Mentor: Karthik\n- Co-mentor: Patrick\n\nImplement support for reftables in “dumb” HTTP transport\n\n- Mentor: Patrick\n- Co-mentor: Karthik\n\n-- >8 --\n\nLet me know if this sounds fine to all of you. So, I suppose we could\npick a maximum of 3 projects but we cannot pick both \"Consolidate\nref-related functionality into git-refs\" and \"Implement support\nfor reftables in “dumb” HTTP transport\" at the same time as Patrick\nonly prefers to be mentor in one project.\n\nBased on this, I'll tweak the ideas page to mention that we could\npick a max of 3 candidates.\n\n\nBTW, I've just submitted Git's application for GSoC. We should know\nby February 26 about the selection result.\n\n--\nSivaraam\n"},{"id":"512045","messageId":"CAP8UFD3YPSFT8izveGmNZ0a3YsNiqQt5tm11tHW4Ld0rJj+FwA@mail.gmail.com","threadId":"62828","inReplyTo":"a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-02-07T08:07:10Z","receivedAt":"2025-02-07T08:07:23Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Kaartic,\n\nOn Fri, Feb 7, 2025 at 8:32 AM Kaartic Sivaraam\n wrote:\n\n> -- 8< --\n>\n> Consolidate ref-related functionality into git-refs\n>\n> - Mentor: Patrick\n> - Co-mentor: Jialuo / Christian\n>\n> Refactoring in order to reduce Git’s global state\n>\n> - Mentor: Christian\n> - Co-mentor: Karthik / Jialuo\n>\n> Machine-Readable Repository Information Query Tool\n>\n> - Mentor: Karthik\n> - Co-mentor: Patrick\n>\n> Implement support for reftables in “dumb” HTTP transport\n>\n> - Mentor: Patrick\n> - Co-mentor: Karthik\n>\n> -- >8 --\n>\n> Let me know if this sounds fine to all of you.\n\nFine for me. Thanks!\n\n> So, I suppose we could\n> pick a maximum of 3 projects but we cannot pick both \"Consolidate\n> ref-related functionality into git-refs\" and \"Implement support\n> for reftables in “dumb” HTTP transport\" at the same time as Patrick\n> only prefers to be mentor in one project.\n\nYeah, but we have time to decide on this. It seems to me that we can\nstill come up with new project ideas and possibly new mentors or\nco-mentors until it's time for applicants to send their.application.\n\n> Based on this, I'll tweak the ideas page to mention that we could\n> pick a max of 3 candidates.\n\nThanks!\n\n> BTW, I've just submitted Git's application for GSoC. We should know\n> by February 26 about the selection result.\n\nThanks again!\n"},{"id":"512052","messageId":"Z6Xmrfut7jdsVAfg@pks.im","threadId":"62828","inReplyTo":"a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-02-07T10:55:41Z","receivedAt":"2025-02-07T10:55:46Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Feb 07, 2025 at 01:02:25PM +0530, Kaartic Sivaraam wrote:\n> Consolidate ref-related functionality into git-refs\n> \n> - Mentor: Patrick\n> - Co-mentor: Jialuo / Christian\n> \n> Refactoring in order to reduce Git’s global state\n> \n> - Mentor: Christian\n> - Co-mentor: Karthik / Jialuo\n> \n> Machine-Readable Repository Information Query Tool\n> \n> - Mentor: Karthik\n> - Co-mentor: Patrick\n> \n> Implement support for reftables in “dumb” HTTP transport\n> \n> - Mentor: Patrick\n> - Co-mentor: Karthik\n> \n> -- >8 --\n> \n> Let me know if this sounds fine to all of you. So, I suppose we could\n> pick a maximum of 3 projects but we cannot pick both \"Consolidate\n> ref-related functionality into git-refs\" and \"Implement support\n> for reftables in “dumb” HTTP transport\" at the same time as Patrick\n> only prefers to be mentor in one project.\n\nThis all looks fine to me.\n\nOne thought: From my point of view I'd strongly favor extending\ngit-refs(1) over reftable support in the dumb HTTP transport. So if I\nhad two applications, one for each topic, I'd lean towards applications\nfor the former topic. That might easily cause unfairness in case\nstudents aren't aware of that.\n\nSo unless somebody else wants to be main-mentor in that project, I think\nwe should either drop the HTTP transport tropic, or communicate our\npriorities clearly.\n\n> Based on this, I'll tweak the ideas page to mention that we could\n> pick a max of 3 candidates.\n> \n> BTW, I've just submitted Git's application for GSoC. We should know\n> by February 26 about the selection result.\n\nGreat! Thanks again for handling all of this.\n\nPatrick\n"},{"id":"512134","messageId":"Z6d5hCrTwChJ0PVu@ArchLinux","threadId":"62828","inReplyTo":"a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-02-08T15:34:28Z","receivedAt":"2025-02-08T15:32:43Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Fri, Feb 07, 2025 at 01:02:25PM +0530, Kaartic Sivaraam wrote:\n> \n> Indeed. From all of your inputs I was able to come to the following\n> allocation of mentor / co-mentor.\n> \n> -- 8< --\n> \n> Consolidate ref-related functionality into git-refs\n> \n> - Mentor: Patrick\n> - Co-mentor: Jialuo / Christian\n> \n> Refactoring in order to reduce Git’s global state\n> \n> - Mentor: Christian\n> - Co-mentor: Karthik / Jialuo\n> \n> Machine-Readable Repository Information Query Tool\n> \n> - Mentor: Karthik\n> - Co-mentor: Patrick\n> \n> Implement support for reftables in “dumb” HTTP transport\n> \n> - Mentor: Patrick\n> - Co-mentor: Karthik\n> \n> -- >8 --\n> \n> Let me know if this sounds fine to all of you. So, I suppose we could\n> pick a maximum of 3 projects but we cannot pick both \"Consolidate\n> ref-related functionality into git-refs\" and \"Implement support\n> for reftables in “dumb” HTTP transport\" at the same time as Patrick\n> only prefers to be mentor in one project.\n> \n\nI am OK with this.\n\n> Based on this, I'll tweak the ideas page to mention that we could\n> pick a max of 3 candidates.\n> \n> \n> BTW, I've just submitted Git's application for GSoC. We should know\n> by February 26 about the selection result.\n> \n\nThanks for working on this.\n\n> --\n> Sivaraam\n\nJialuo\n"},{"id":"512185","messageId":"CAOLa=ZQZmq2YYe4iV0UMa+CaKkQh9v+h5oDuxHd0R1AfceLTrA@mail.gmail.com","threadId":"62828","inReplyTo":"a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-02-10T17:00:13Z","receivedAt":"2025-02-10T17:00:15Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hi Christian, Karthik, Patrick, Jialuo and all,\n>\n> On 05/02/25 18:50, Christian Couder wrote:\n>> Hi Kaartic and all,\n>>\n>> On Tue, Feb 4, 2025 at 7:33 PM Kaartic Sivaraam\n>> wrote:\n>>\n>> I have just added myself as a possible mentor. If possible I'd like to\n>> just co-mentor this project and someone else to be the main mentor for\n>> this project.\n>>\n> > ...\n>>\n>> I have just added myself as a possible mentor. If possible I'd like to\n>> be the main mentor for this project.\n>>\n>\n> Thank you for adding yourself as a potential mentor!\n>\n> With this, it seems to me like we could at the max. accept 3 students\n>\n>>> Note that I haven't assigned any mentors / co-mentors for each project.\n>>> I suppose we could assign that based on the applications we receive and\n>>> the ideas that we end up selecting.\n>>>\n>>> Based on Christian's inputs, we should be able to distribute\n>>> projects among mentors well.\n>>\n>> Yeah, I hope it will be possible to distribute projects among mentors well.\n>>\n>\n> Indeed. From all of your inputs I was able to come to the following\n> allocation of mentor / co-mentor.\n>\n> -- 8< --\n>\n> Consolidate ref-related functionality into git-refs\n>\n> - Mentor: Patrick\n> - Co-mentor: Jialuo / Christian\n>\n> Refactoring in order to reduce Git’s global state\n>\n> - Mentor: Christian\n> - Co-mentor: Karthik / Jialuo\n>\n> Machine-Readable Repository Information Query Tool\n>\n> - Mentor: Karthik\n> - Co-mentor: Patrick\n>\n> Implement support for reftables in “dumb” HTTP transport\n>\n> - Mentor: Patrick\n> - Co-mentor: Karthik\n>\n> -- >8 --\n>\n> Let me know if this sounds fine to all of you. So, I suppose we could\n> pick a maximum of 3 projects but we cannot pick both \"Consolidate\n> ref-related functionality into git-refs\" and \"Implement support\n> for reftables in “dumb” HTTP transport\" at the same time as Patrick\n> only prefers to be mentor in one project.\n>\n\nThis looks great to me, thanks for putting it together. Once the\napplications start coming in, we can finalize on which combination works\nout for us.\n\n>\n> Based on this, I'll tweak the ideas page to mention that we could\n> pick a max of 3 candidates.\n>\n>\n> BTW, I've just submitted Git's application for GSoC. We should know\n> by February 26 about the selection result.\n>\n\nAgain, thanks for all the work here!\n\n> --\n> Sivaraam\n"},{"id":"512206","messageId":"fa9ad3c6-3b3c-4f3c-89c6-101ed1b51eb6@gmail.com","threadId":"62828","inReplyTo":"Z6Xmrfut7jdsVAfg@pks.im","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-11T05:18:22Z","receivedAt":"2025-02-11T05:18:51Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Patrick, Christian and all,\n\nOn 07/02/25 16:25, Patrick Steinhardt wrote:\n> One thought: From my point of view I'd strongly favor extending\n> git-refs(1) over reftable support in the dumb HTTP transport. So if I\n> had two applications, one for each topic, I'd lean towards applications\n> for the former topic. That might easily cause unfairness in case\n> students aren't aware of that.\n> \n> So unless somebody else wants to be main-mentor in that project, I think\n> we should either drop the HTTP transport tropic, or communicate our\n> priorities clearly.\n\nThat makes sense. I've added a note to convey this clearly. Kindly check \nif the change in the following PR looks fine.\n\n https://github.com/git/git.github.io/pull/750/files\n\n\nOn 07/02/25 13:37, Christian Couder wrote:\n > Yeah, but we have time to decide on this. It seems to me that we can\n > still come up with new project ideas and possibly new mentors or\n > co-mentors until it's time for applicants to send their.application.\n\nIndeed. More volunteer mentors and ideas are always welcome :-)\n\n--\nSivaraam\n"},{"id":"512482","messageId":"D7TVXVKVWRS8.S2BJN32QHZ0O@gmail.com","threadId":"62828","inReplyTo":"fa9ad3c6-3b3c-4f3c-89c6-101ed1b51eb6@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Ghanshyam Thakkar","fromEmail":"shyamthakkar001@gmail.com","sentAt":"2025-02-16T12:56:46Z","receivedAt":"2025-02-16T12:56:53Z","isPatch":false,"sender":{"key":"shyamthakkar001@gmail.com","avatar":"https://avatars.githubusercontent.com/u/72698233?v=4"},"body":"On Tue Feb 11, 2025 at 10:48 AM IST, Kaartic Sivaraam wrote:\n> Hi Patrick, Christian and all,\n>\n> On 07/02/25 16:25, Patrick Steinhardt wrote:\n> > One thought: From my point of view I'd strongly favor extending\n> > git-refs(1) over reftable support in the dumb HTTP transport. So if I\n> > had two applications, one for each topic, I'd lean towards applications\n> > for the former topic. That might easily cause unfairness in case\n> > students aren't aware of that.\n> > \n> > So unless somebody else wants to be main-mentor in that project, I think\n> > we should either drop the HTTP transport tropic, or communicate our\n> > priorities clearly.\n>\n> That makes sense. I've added a note to convey this clearly. Kindly check \n> if the change in the following PR looks fine.\n>\n> https://github.com/git/git.github.io/pull/750/files\n>\n>\n> On 07/02/25 13:37, Christian Couder wrote:\n> > Yeah, but we have time to decide on this. It seems to me that we can\n> > still come up with new project ideas and possibly new mentors or\n> > co-mentors until it's time for applicants to send their.application.\n>\n> Indeed. More volunteer mentors and ideas are always welcome :-)\n\nHi,\n\nI can co-mentor this summer. The 'Machine-Readable Repository Information\nQuery Tool' project seems interesting to me, although I'm up for co-mentoring\nin other projects as well. Let me know if you need any help with\nanything else.\n\nThanks.\n"},{"id":"512483","messageId":"59004310-f270-468d-a248-c83c97de4a1f@gmail.com","threadId":"62828","inReplyTo":"D7TVXVKVWRS8.S2BJN32QHZ0O@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-16T13:53:02Z","receivedAt":"2025-02-16T13:53:31Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Ghanshyam,\n\nOn 16/02/25 18:26, Ghanshyam Thakkar wrote:\n> \n> I can co-mentor this summer. The 'Machine-Readable Repository Information\n> Query Tool' project seems interesting to me, although I'm up for co-mentoring\n> in other projects as well. Let me know if you need any help with\n> anything else.\n>\n\nThat's great to hear! Thank you for volunteering. I've added you as\na potential co-mentor for the project that you've mentioned. We\ncould discuss about the allocation to other projects based on the\napplications that we receive. Feel free to let me know if there are\nspecific projects you wish to co-mentor in.\n\nAlso, feel free to share if you have any other ideas that we could have\nfor this GSoC.\n\n--\nSivaraam\n\n"},{"id":"512490","messageId":"xmqqikp9zspe.fsf@gitster.g","threadId":"62828","inReplyTo":"59004310-f270-468d-a248-c83c97de4a1f@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-02-16T17:48:29Z","receivedAt":"2025-02-16T17:48:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hi Ghanshyam,\n>\n> On 16/02/25 18:26, Ghanshyam Thakkar wrote:\n>> I can co-mentor this summer. The 'Machine-Readable Repository\n>> Information\n>> Query Tool' project seems interesting to me, although I'm up for co-mentoring\n>> in other projects as well. Let me know if you need any help with\n>> anything else.\n>>\n>\n> That's great to hear! Thank you for volunteering. I've added you as\n> a potential co-mentor for the project that you've mentioned. We\n> could discuss about the allocation to other projects based on the\n> applications that we receive. Feel free to let me know if there are\n> specific projects you wish to co-mentor in.\n>\n> Also, feel free to share if you have any other ideas that we could have\n> for this GSoC.\n\nIt is great to see that old timers who have been dormant for a\nwhile, as well as newcomers who have been around for less than a\nyear, to be running and volunteering these mentoring programs.\n\nPlease keep the community thriving with more of both old and new\nblood.\n\nThanks.\n"},{"id":"512516","messageId":"D7UTMXEUFQS8.15HJN6CTDM16S@gmail.com","threadId":"62828","inReplyTo":"59004310-f270-468d-a248-c83c97de4a1f@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Ghanshyam Thakkar","fromEmail":"shyamthakkar001@gmail.com","sentAt":"2025-02-17T15:21:06Z","receivedAt":"2025-02-17T15:21:13Z","isPatch":false,"sender":{"key":"shyamthakkar001@gmail.com","avatar":"https://avatars.githubusercontent.com/u/72698233?v=4"},"body":"On Sun Feb 16, 2025 at 7:23 PM IST, Kaartic Sivaraam wrote:\n> Hi Ghanshyam,\n>\n> On 16/02/25 18:26, Ghanshyam Thakkar wrote:\n> > \n> > I can co-mentor this summer. The 'Machine-Readable Repository Information\n> > Query Tool' project seems interesting to me, although I'm up for co-mentoring\n> > in other projects as well. Let me know if you need any help with\n> > anything else.\n> >\n>\n> That's great to hear! Thank you for volunteering. I've added you as\n> a potential co-mentor for the project that you've mentioned. We\n> could discuss about the allocation to other projects based on the\n> applications that we receive. Feel free to let me know if there are\n> specific projects you wish to co-mentor in.\n\nSure, I can co-mentor either of the \"Consolidate ref-related functionality\ninto git-refs\" or \"Refactoring in order to reduce Git’s global state\"\nprojects as well, if needed.\n\n> Also, feel free to share if you have any other ideas that we could have\n> for this GSoC.\n\nSure thing!\n\nThanks.\n"},{"id":"513218","messageId":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","threadId":"62828","inReplyTo":"8c8e8797-8de9-4684-94a0-f6c17a592dc5@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-02-28T03:03:38Z","receivedAt":"2025-02-28T03:03:40Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,\n\n\nOn 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam wrote:\n>Hello everyone,\n>\n>It is that time of year. GSoC Org Applications for 2025 are open now[1].\n>They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)\n>\n\nI'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!\n\nChristian, Patrick and Karthik,\n\nAs you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n\nGhanshyam and Jialuo,\n\nAs you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n\nLet's look forward towards for a great summer this year! :-)\n\n[[ References ]]\n\n[1]: https://summerofcode.withgoogle.com/programs/2025/organizations/git\n\n-- \nSivaraam\n\nSent from my Android device with K-9 Mail. Please excuse my brevity.\n"},{"id":"513224","messageId":"Z8FEaIzK60EDMEFn@ArchLinux","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"shejialuo","fromEmail":"shejialuo@gmail.com","sentAt":"2025-02-28T05:06:48Z","receivedAt":"2025-02-28T05:06:38Z","isPatch":false,"sender":{"key":"shejialuo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56911263?v=4"},"body":"On Fri, Feb 28, 2025 at 08:33:38AM +0530, Kaartic Sivaraam wrote:\n> Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,\n> \n> \n> On 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam wrote:\n> >Hello everyone,\n> >\n> >It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> >They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)\n> >\n> \n> I'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!\n> \n\nThanks for working on this.\n\n> Christian, Patrick and Karthik,\n> \n> As you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n> \n> Ghanshyam and Jialuo,\n> \n> As you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n> \n\nI have already signed up and accepted the agreement.\n\n> Let's look forward towards for a great summer this year! :-)\n> \n\nYes, that would be a great journey.\n\nThanks,\nJialuo\n"},{"id":"513227","messageId":"Z8FUsPOcg9ht65Bp@pks.im","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-02-28T06:16:16Z","receivedAt":"2025-02-28T06:16:26Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Feb 28, 2025 at 08:33:38AM +0530, Kaartic Sivaraam wrote:\n> Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,\n> \n> \n> On 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam wrote:\n> >Hello everyone,\n> >\n> >It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> >They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)\n> >\n> \n> I'm glad to announce that we've successfully been selected as a\n> mentoring organization for GSoC this year[1]!\n\nYay!\n\n> Christian, Patrick and Karthik,\n> \n> As you're already members of the organization kindly log in to the\n> GSoC portal to read and accept this year's Program Rules and Org\n> Member agreement. Let me know once that's done. I could then add you\n> to this year's program.\n\nThanks, I've accepted the docs.\n\nPatrick\n"},{"id":"513235","messageId":"CAP8UFD0Tos_3kF+FBfQWiL=69M2bZKcisYCT=5p_Qgt9hv+dJQ@mail.gmail.com","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-02-28T07:56:47Z","receivedAt":"2025-02-28T07:57:01Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Feb 28, 2025 at 4:03 AM Kaartic Sivaraam\n wrote:\n\n> I'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!\n\nNice! Thanks for your work on this and for reporting it!\n\n> Christian, Patrick and Karthik,\n>\n> As you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n\nDone.\n\n> Let's look forward towards for a great summer this year! :-)\n\nSure :-)\n"},{"id":"513269","messageId":"D83ZYCF2FK80.31D5JQKVVP069@gmail.com","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Ghanshyam Thakkar","fromEmail":"shyamthakkar001@gmail.com","sentAt":"2025-02-28T10:12:07Z","receivedAt":"2025-02-28T10:12:15Z","isPatch":false,"sender":{"key":"shyamthakkar001@gmail.com","avatar":"https://avatars.githubusercontent.com/u/72698233?v=4"},"body":"On Fri Feb 28, 2025 at 8:33 AM IST, Kaartic Sivaraam wrote:\n> Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,\n>\n>\n> On 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam wrote:\n> >Hello everyone,\n> >\n> >It is that time of year. GSoC Org Applications for 2025 are open now[1].\n> >They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)\n> >\n>\n> I'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!\n\nNice!\n\n> As you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n\nI'e signed up and accepted the Program Rules and Org Member agreement.\nThanks for managing the process!\n\n>\n> Let's look forward towards for a great summer this year! :-)\n\nLooking forward to it!\n"},{"id":"513317","messageId":"F59FB3BE-59D7-4233-A75D-F756678ED9E7@gmail.com","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-03-01T00:47:55Z","receivedAt":"2025-03-01T00:47:59Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"\n\nOn 28 February 2025 8:33:38 am IST, Kaartic Sivaraam wrote:\n>\n>Christian, Patrick and Karthik,\n>\n>As you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n>\n>Ghanshyam and Jialuo,\n>\n>As you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n>\n\nNice. I've added all of you to the 2025 program. You should be able to access this year's program page at:\n\n https://summerofcode.withgoogle.com/organizations/git/programs/2025/\n\n-- \nSivaraam\n\nSent from my Android device with K-9 Mail. Please excuse my brevity.\n"},{"id":"513391","messageId":"CAOLa=ZSHETyzEyyJvP-VT9CbvrJt_jV65nEyCOzR3YGRgFNkrQ@mail.gmail.com","threadId":"62828","inReplyTo":"6C29409D-691B-471F-B08C-83E14D35EE13@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-03-03T10:00:45Z","receivedAt":"2025-03-03T10:00:47Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hi Christian, Patrick, Ghanshyam, Karthik, Jialuo and all,\n>\n>\n> On 19 January 2025 3:43:29 pm IST, Kaartic Sivaraam wrote:\n>>Hello everyone,\n>>\n>>It is that time of year. GSoC Org Applications for 2025 are open now[1].\n>>They are due before Tuesday, February 11 at 1800 UTC. It's good to see that few contributors have already started working on microprojects this year :-)\n>>\n>\n> I'm glad to announce that we've successfully been selected as a mentoring organization for GSoC this year[1]!\n>\n> Christian, Patrick and Karthik,\n>\n> As you're already members of the organization kindly log in to the GSoC portal to read and accept this year's Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n>\n\nThat's amazing news. I've signed up. Thanks for handling all of this!\n\n>\n> Ghanshyam and Jialuo,\n>\n> As you're new to the program, I've sent you an invite. You should've got an e-mail about it. Kindly sign up via the same to read an accept the Program Rules and Org Member agreement. Let me know once that's done. I could then add you to this year's program.\n>\n> Let's look forward towards for a great summer this year! :-)\n>\n> [[ References ]]\n>\n> [1]: https://summerofcode.withgoogle.com/programs/2025/organizations/git\n>\n> --\n> Sivaraam\n>\n> Sent from my Android device with K-9 Mail. Please excuse my brevity.\n"},{"id":"513740","messageId":"CAOLa=ZRM3bLcR3s6nE8nXFv32zX8-mL6fSh1vbsVetJcp9KFhw@mail.gmail.com","threadId":"62828","inReplyTo":"59004310-f270-468d-a248-c83c97de4a1f@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-03-07T10:01:24Z","receivedAt":"2025-03-07T10:01:26Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hi Ghanshyam,\n>\n> On 16/02/25 18:26, Ghanshyam Thakkar wrote:\n>>\n>> I can co-mentor this summer. The 'Machine-Readable Repository Information\n>> Query Tool' project seems interesting to me, although I'm up for co-mentoring\n>> in other projects as well. Let me know if you need any help with\n>> anything else.\n>>\n>\n> That's great to hear! Thank you for volunteering. I've added you as\n> a potential co-mentor for the project that you've mentioned. We\n> could discuss about the allocation to other projects based on the\n> applications that we receive. Feel free to let me know if there are\n> specific projects you wish to co-mentor in.\n>\n> Also, feel free to share if you have any other ideas that we could have\n> for this GSoC.\n>\n\nI wonder if with Ghanshyam also mentoring, if this statement still\nholds true\n\n Note about limit of project selection\n\n Kindly note that considering the bandwidth of available mentors, the\n Git project would only mentor up to 3 contributors this year.\n\nMaybe we can do 4 projects this year?\n\n> --\n> Sivaraam\n"},{"id":"514781","messageId":"ffefdd01-ec80-4af4-b011-723ad1260f68@gmail.com","threadId":"62828","inReplyTo":"CAOLa=ZRM3bLcR3s6nE8nXFv32zX8-mL6fSh1vbsVetJcp9KFhw@mail.gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2025-03-20T17:50:02Z","receivedAt":"2025-03-20T17:50:14Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Karthik,\n\nSorry for the delayed response! I kind of missed to respond unintentionally.\n\nOn 07/03/25 15:31, Karthik Nayak wrote:\n> \n> I wonder if with Ghanshyam also mentoring, if this statement still\n> holds true\n> \n> Note about limit of project selection\n> \n> Kindly note that considering the bandwidth of available mentors, the\n> Git project would only mentor up to 3 contributors this year.\n> \n> Maybe we can do 4 projects this year?\n> \n\nWhile we do have 5 volunteers for mentoring students this year, we only \nhave 3 candidates who could play the role of the primary mentor. \nGhanshyam and Jialuo only prefer to co-mentor as far as I could \nunderstand. So, that still gives us a limit of 3 projects doesn't it?\n\nKindly correct me in case I'm missing anything.\n\n--\nSivaraam\n"},{"id":"514842","messageId":"CAOLa=ZTsp-N3h5bbquFjEY_XSBV=GqCwDWUDCykBfERbxg8PNg@mail.gmail.com","threadId":"62828","inReplyTo":"ffefdd01-ec80-4af4-b011-723ad1260f68@gmail.com","subject":"Re: Git in GSoC 2025","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2025-03-21T21:02:07Z","receivedAt":"2025-03-21T21:02:09Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Kaartic Sivaraam writes:\n\n> Hi Karthik,\n>\n> Sorry for the delayed response! I kind of missed to respond unintentionally.\n>\n> On 07/03/25 15:31, Karthik Nayak wrote:\n>>\n>> I wonder if with Ghanshyam also mentoring, if this statement still\n>> holds true\n>>\n>> Note about limit of project selection\n>>\n>> Kindly note that considering the bandwidth of available mentors, the\n>> Git project would only mentor up to 3 contributors this year.\n>>\n>> Maybe we can do 4 projects this year?\n>>\n>\n> While we do have 5 volunteers for mentoring students this year, we only\n> have 3 candidates who could play the role of the primary mentor.\n> Ghanshyam and Jialuo only prefer to co-mentor as far as I could\n> understand. So, that still gives us a limit of 3 projects doesn't it?\n>\n> Kindly correct me in case I'm missing anything.\n>\n\nYou're right, I didn't think of that :)\n\n> --\n> Sivaraam\n"}]}