{"thread":{"id":"64818","subject":"Git project and GSoC 2026","startedAt":"2026-01-16T11:06:28Z","lastAt":"2026-02-22T18:40:28Z","messageCount":19,"participants":["Christian Couder","Lucas Seiki Oshiro","Kaartic Sivaraam","Chandra Pratap","Karthik Nayak"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"534026","messageId":"CAP8UFD11txMWSfMTvDtcBJuuZA5mKffo6XUyR9LWk2d_N0RRtA@mail.gmail.com","threadId":"64818","inReplyTo":null,"subject":"Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-01-16T11:06:13Z","receivedAt":"2026-01-16T11:06:28Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi everyone,\n\nThe application period for mentoring organizations to participate in\nGSoC 2026 is from January 19 to February 3. Let's try to anticipate a\nbit and decide soon if the Git project wants to participate.\n\nIf we want to participate, we need (co-)mentors, org-admins, projects\nand micro-projects ideas, and we need to update existing pages or\ncreate new ones on the Git Developer Pages (git.github.io) website (or\non git-scm.org if we want to switch this to it now). Please chime in\nif you are interested.\n\nAbout (co-)mentors and org-admins, Karthik, Justin, Siddharth and me\nhave already expressed their interest in (co-)mentoring in internal\nGitLab discussions. I am willing to be an org-admin too.\n\nThe Git team at GitLab is also willing to manage Slack discussions\nchannels for (co-)mentors, org-admins and helpers, and then for\naccepted contributors too, in the same way as for GSoC 2025.\n\nThanks,\nChristian.\n"},{"id":"534156","messageId":"29682837-D2F2-47B7-B1A4-5CED32FCCA49@gmail.com","threadId":"64818","inReplyTo":"CAP8UFD11txMWSfMTvDtcBJuuZA5mKffo6XUyR9LWk2d_N0RRtA@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Lucas Seiki Oshiro","fromEmail":"lucasseikioshiro@gmail.com","sentAt":"2026-01-19T00:44:08Z","receivedAt":"2026-01-19T00:44:26Z","isPatch":false,"sender":{"key":"lucasseikioshiro@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12701580?v=4"},"body":"\n> Hi everyone,\n\nHi, Christian!\n\n> Please chime in if you are interested.\n\nI've just finished my master's and I still don't know what I'll be\ndoing in the rest of this year, so I can't guarantee that I'll be\nable to be a co-mentor. But I'll be glad to help in the Developer\nPages.\n\n> About (co-)mentors and org-admins, Karthik, Justin, Siddharth and me\n> have already expressed their interest in (co-)mentoring in internal\n> GitLab discussions. I am willing to be an org-admin too.\n\nA really good team!\n\n> Thanks,\n> Christian.\n\nThanks!\n"},{"id":"534176","messageId":"CAP8UFD2LOpmXxF0kjbLO1V4YS3ti8Dqj1w8Pu6-JSz3y=fXWpg@mail.gmail.com","threadId":"64818","inReplyTo":"29682837-D2F2-47B7-B1A4-5CED32FCCA49@gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-01-19T08:34:47Z","receivedAt":"2026-01-19T08:34:59Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Lucas,\n\nOn Mon, Jan 19, 2026 at 1:44 AM Lucas Seiki Oshiro\n wrote:\n\n> I've just finished my master's and I still don't know what I'll be\n> doing in the rest of this year, so I can't guarantee that I'll be\n> able to be a co-mentor. But I'll be glad to help in the Developer\n> Pages.\n\nThanks, I will add you to the Slack channel.\n"},{"id":"534352","messageId":"CAP8UFD12hQCp+=aVkUjDuiTJ6r5BM6RaBkz0oLPbdqzaTjCgxg@mail.gmail.com","threadId":"64818","inReplyTo":"CAE7as+ZX8n4b5GypTACNCd9dWzNZTVf7fmH+5wfmEvDwEUXX6A@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-01-21T14:41:53Z","receivedAt":"2026-01-21T14:42:06Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Ayush,\n\nOn Wed, Jan 21, 2026 at 11:39 AM Ayush Chandekar\n wrote:\n> On Fri, Jan 16, 2026 at 4:36 PM Christian Couder wrote:\n\n> > If we want to participate, we need (co-)mentors, org-admins, projects\n> > and micro-projects ideas, and we need to update existing pages or\n> > create new ones on the Git Developer Pages (git.github.io) website (or\n> > on git-scm.org if we want to switch this to it now). Please chime in\n> > if you are interested.\n>\n> Yes, I am interested in co-mentoring for the GSoC 2026. I will also help in updating the Developer Pages.\n\nThanks, I will add you to the Slack channel.\n"},{"id":"534425","messageId":"35E56A79-FD65-4CBF-9A35-BCFB9A169BFA@gmail.com","threadId":"64818","inReplyTo":"CAP8UFD11txMWSfMTvDtcBJuuZA5mKffo6XUyR9LWk2d_N0RRtA@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-01-22T05:08:29Z","receivedAt":"2026-01-22T05:08:36Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Christian,\n\nThank you for initiating the discussion.\n\nOn 16/01/26 16:36, Christian Couder wrote:\n> \n> The application period for mentoring organizations to participate in\n> GSoC 2026 is from January 19 to February 3. Let's try to anticipate a\n> bit and decide soon if the Git project wants to participate.\n>\n\nIndeed.\n\n> If we want to participate, we need (co-)mentors, org-admins, projects\n> and micro-projects ideas, and we need to update existing pages or\n> create new ones on the Git Developer Pages (git.github.io) website (or\n> on git-scm.org if we want to switch this to it now). Please chime in\n> if you are interested.\n>\n\nI would be glad to help as an org-Admin this year too. I could act as a fallback mentor in case any mentor / co-mentor becomes unavailable during a particular period of the program.\n\nI also Cc-ed Chandra Pratap as they expressed interest to be a co-mentor before. \n\n> About (co-)mentors and org-admins, Karthik, Justin, Siddharth and me\n> have already expressed their interest in (co-)mentoring in internal\n> GitLab discussions. I am willing to be an org-admin too.\n>\n\nWonderful to see that we already have 5 potential mentors! Keep them coming! Also, it would be nice to hear potential idea suggestions too. The more the merrier :-)\n\n> The Git team at GitLab is also willing to manage Slack discussions\n> channels for (co-)mentors, org-admins and helpers, and then for\n> accepted contributors too, in the same way as for GSoC 2025.\n>\n\nCool!\n\n--\nSivaraam\n"},{"id":"534429","messageId":"CAP8UFD0kEATc6sU4r2pVq9k2X737Tk+_VXrxXx8K=M6=ciL=vQ@mail.gmail.com","threadId":"64818","inReplyTo":"35E56A79-FD65-4CBF-9A35-BCFB9A169BFA@gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-01-22T07:33:26Z","receivedAt":"2026-01-22T07:33:39Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Kaartic,\n\nOn Thu, Jan 22, 2026 at 6:08 AM Kaartic Sivaraam\n wrote:\n> On 16/01/26 16:36, Christian Couder wrote:\n\n> > If we want to participate, we need (co-)mentors, org-admins, projects\n> > and micro-projects ideas, and we need to update existing pages or\n> > create new ones on the Git Developer Pages (git.github.io) website (or\n> > on git-scm.org if we want to switch this to it now). Please chime in\n> > if you are interested.\n>\n> I would be glad to help as an org-Admin this year too. I could act as a fallback mentor in case any mentor / co-mentor becomes unavailable during a particular period of the program.\n>\n> I also Cc-ed Chandra Pratap as they expressed interest to be a co-mentor before.\n\nGreat, thanks! I will add you to the Slack channel.\n\n> > About (co-)mentors and org-admins, Karthik, Justin, Siddharth and me\n> > have already expressed their interest in (co-)mentoring in internal\n> > GitLab discussions. I am willing to be an org-admin too.\n> >\n>\n> Wonderful to see that we already have 5 potential mentors! Keep them coming! Also, it would be nice to hear potential idea suggestions too. The more the merrier :-)\n\nYeah, project idea suggestions are very welcome.\n"},{"id":"534453","messageId":"CA+J6zkSo1LuFUdTU8m6z4vANrJ2r88EV6RDDC_0ZW3bWec2v2Q@mail.gmail.com","threadId":"64818","inReplyTo":"35E56A79-FD65-4CBF-9A35-BCFB9A169BFA@gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Chandra Pratap","fromEmail":"chandrapratap3519@gmail.com","sentAt":"2026-01-22T14:43:27Z","receivedAt":"2026-01-22T14:43:55Z","isPatch":false,"sender":{"key":"chandrapratap3519@gmail.com","avatar":null},"body":"Hey all!\n\nOn Thu, 22 Jan 2026, 10:38 Kaartic Sivaraam, wrote:\n>\n> Hi Christian,\n>\n> Thank you for initiating the discussion.\n>\n> On 16/01/26 16:36, Christian Couder wrote:\n> >\n> > The application period for mentoring organizations to participate in\n> > GSoC 2026 is from January 19 to February 3. Let's try to anticipate a\n> > bit and decide soon if the Git project wants to participate.\n> >\n>\n> Indeed.\n>\n> > If we want to participate, we need (co-)mentors, org-admins, projects\n> > and micro-projects ideas, and we need to update existing pages or\n> > create new ones on the Git Developer Pages (git.github.io) website (or\n> > on git-scm.org if we want to switch this to it now). Please chime in\n> > if you are interested.\n> >\n>\n> I would be glad to help as an org-Admin this year too. I could act as a fallback mentor in case any mentor / co-mentor becomes unavailable during a particular period of the program.\n>\n> I also Cc-ed Chandra Pratap as they expressed interest to be a co-mentor before.\n\nI'd be glad to help as a co-mentor. I think I'd be able to best help\nwith project ideas related to reftable or testing, seeing how I worked\non reftable tests in my GSoC project, but please let me know if I can\nhelp with anything else as well!\n"},{"id":"534772","messageId":"BAD29E01-C358-456F-8E31-058AC0AED0C8@gmail.com","threadId":"64818","inReplyTo":"CAP8UFD0kEATc6sU4r2pVq9k2X737Tk+_VXrxXx8K=M6=ciL=vQ@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-01-28T20:28:52Z","receivedAt":"2026-01-28T20:28:57Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi all,\n\n\nOn 22 January 2026 1:03:26 pm IST, Christian Couder wrote:\n>>\n>> Wonderful to see that we already have 5 potential mentors! Keep them coming! Also, it would be nice to hear potential idea suggestions too. The more the merrier :-)\n>\n>Yeah, project idea suggestions are very welcome.\n\nJust a gentle nudge for the project ideas. The deadline to apply for GSoC is Feb 3 18:00 UTC. We need the ideas page ready a couple of days before it at least.\n\nFeel free to chime in to suggest ideas that would be achievable by someone new-ish to the community. If you're doubtful whether an idea would be relevant for GSoC, feel free to share the same and we can discuss it.\n\nThe same goes for micro project suggestions. Feel free to share new ones that could be added to the following microprojects page:\n\n\n\n-- \nSivaraam\n\nSent from my Android device with K-9 Mail. Please excuse my brevity.\n"},{"id":"534802","messageId":"CAP8UFD29LtG2dRRB4f6mZAHNGqDmDxUV4ULYw3w3OYg15ZBBYg@mail.gmail.com","threadId":"64818","inReplyTo":"BAD29E01-C358-456F-8E31-058AC0AED0C8@gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-01-29T10:20:41Z","receivedAt":"2026-01-29T10:20:54Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Wed, Jan 28, 2026 at 9:28 PM Kaartic Sivaraam\n wrote:\n\n> Just a gentle nudge for the project ideas. The deadline to apply for GSoC is Feb 3 18:00 UTC. We need the ideas page ready a couple of days before it at least.\n\nThanks for the nudge!\n\n> Feel free to chime in to suggest ideas that would be achievable by someone new-ish to the community. If you're doubtful whether an idea would be relevant for GSoC, feel free to share the same and we can discuss it.\n\nHere are ideas I came up with:\n\n1) Continue the current work on removing global variables.\n\n2) Finish, and then maybe improve, some work Eric Ju started a long\ntime ago on `git cat-file`.\n\n3) Improve git-backfill, or maybe a different command, so it can\nremove large local blobs when they are available on a promisor remote\n(for clients who want to get back disk space).\n\n4) Implement some kind of fetch order when more than 1 promisor remote\nis configured (this order could be passed from servers to clients\nthrough the promisor-remote protocol to make sure the fetches happen\nin the optimal order).\n\n5) Make the promisor-remote protocol useful when the server wants to\nadvertise \"better-connected\" remotes (not just remotes the server\nuses) as Junio suggested some time ago (see\nDocumentation/gitprotocol-v2.adoc).\n\n6) Improve `git repo info` so it can show more information than now.\n\n7) Improve `git repo structure` so it can show more stats than now.\n\n8) Improve fast-export/fast-import and maybe git-repo-filter regarding\ncommit and/or tag signatures. This might conflict with GitLab people\n(including me) possibly working on that soon though.\n\nI would be willing to mentor any of them, but I don't have much\nknowledge on `git repo`, so I think it makes more sense for me to\navoid 6) and 7).\n"},{"id":"534837","messageId":"21D9FA76-F382-483E-817F-C3947C939D16@gmail.com","threadId":"64818","inReplyTo":"CAP8UFD29LtG2dRRB4f6mZAHNGqDmDxUV4ULYw3w3OYg15ZBBYg@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Lucas Seiki Oshiro","fromEmail":"lucasseikioshiro@gmail.com","sentAt":"2026-01-29T20:41:19Z","receivedAt":"2026-01-29T20:41:37Z","isPatch":false,"sender":{"key":"lucasseikioshiro@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12701580?v=4"},"body":"\n> 6) Improve `git repo info` so it can show more information than now.\n\nFrom my side, I have these features in my local backlog:\n\n- remove the dependency on `the_repository`\n- use the category as key\n- add the path-related values (copied from git-rev-parse \"Options for\n Files\"):\n - git-dir\n - common-dir\n - toplevel\n - superproject-working-tree\n- add more values currently obtained through\n`git rev-parse --git-path`:\n - grafts file\n - index file\n - objects directory\n - hooks directory\n - git-prefix\n - other paths that are adjusted by update_common_dir()\n\nI already started to add those path-related values [1], but I think\nthat the major problem is deciding whether we should use relative or\nabsolute paths.\n\nI also think that we have room for other information that we retrieve\nthrough commands other than git-rev-parse.\n\n> 7) Improve `git repo structure` so it can show more stats than now.\n\nI don't know Justin's future plans for this command, but the idea\nwas to bring some functionality from git-sizer [2] to Git.\n\n> I would be willing to mentor any of them, but I don't have much\n> knowledge on `git repo`, so I think it makes more sense for me to\n> avoid 6) and 7).\n\nIf you want, I can share with you some information about\ngit-repo-info.\n\nI really appreciate initiatives like git-repo-structure and\ngit-history that bring features from other tools that make Git\neasier to use. This week, I was talked independently with two\nfriends about how git-blame can be misleading sometimes since it\nonly shows the last change in a line. One of them really likes\n`git log -S` for \"blaming\" strings and thinks that it's a too\npowerful feature that is hidden inside git-log. The other one\nshowed me Cregit [3], a tool for blaming based on tokens\ninstead of lines. A \"string blame\" or a \"token blame\" could be\na nice GSoC project (but maybe for future editions).\n\n\n[1] https://github.com/lucasoshiro/git/compare/master...repo-info-path/\n[2] https://github.com/github/git-sizer\n[3] https://github.com/cregit/cregit"},{"id":"534857","messageId":"CAOLa=ZTK-PdJAYfDVPW3qLN+nBCe71Q=E8xohJzbFK=EH8sNkA@mail.gmail.com","threadId":"64818","inReplyTo":"CAP8UFD29LtG2dRRB4f6mZAHNGqDmDxUV4ULYw3w3OYg15ZBBYg@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Karthik Nayak","fromEmail":"karthik.188@gmail.com","sentAt":"2026-01-30T09:32:14Z","receivedAt":"2026-01-30T09:32:16Z","isPatch":false,"sender":{"key":"karthik.188@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1786334?v=4"},"body":"Christian Couder writes:\n\n> Hi,\n>\n> On Wed, Jan 28, 2026 at 9:28 PM Kaartic Sivaraam\n> wrote:\n>\n>> Just a gentle nudge for the project ideas. The deadline to apply for GSoC is Feb 3 18:00 UTC. We need the ideas page ready a couple of days before it at least.\n>\n> Thanks for the nudge!\n>\n>> Feel free to chime in to suggest ideas that would be achievable by someone new-ish to the community. If you're doubtful whether an idea would be relevant for GSoC, feel free to share the same and we can discuss it.\n>\n> Here are ideas I came up with:\n\nThanks Chris for leading this effort!\n\n>\n> 1) Continue the current work on removing global variables.\n>\n> 2) Finish, and then maybe improve, some work Eric Ju started a long\n> time ago on `git cat-file`.\n>\n> 3) Improve git-backfill, or maybe a different command, so it can\n> remove large local blobs when they are available on a promisor remote\n> (for clients who want to get back disk space).\n>\n> 4) Implement some kind of fetch order when more than 1 promisor remote\n> is configured (this order could be passed from servers to clients\n> through the promisor-remote protocol to make sure the fetches happen\n> in the optimal order).\n>\n> 5) Make the promisor-remote protocol useful when the server wants to\n> advertise \"better-connected\" remotes (not just remotes the server\n> uses) as Junio suggested some time ago (see\n> Documentation/gitprotocol-v2.adoc).\n>\n> 6) Improve `git repo info` so it can show more information than now.\n>\n> 7) Improve `git repo structure` so it can show more stats than now.\n>\n> 8) Improve fast-export/fast-import and maybe git-repo-filter regarding\n> commit and/or tag signatures. This might conflict with GitLab people\n> (including me) possibly working on that soon though.\n>\n> I would be willing to mentor any of them, but I don't have much\n> knowledge on `git repo`, so I think it makes more sense for me to\n> avoid 6) and 7).\n\nI'd be willing to mentor any of the projects listed. I have a little\ncontext in all of these, but that's a good reason to understand more :)\n\nMaybe we can also decide how many projects we are willing to mentor this\nyear?\n\nKarthik\n"},{"id":"535040","messageId":"CAP8UFD0qtn_1VAA1SiAMjGVF7Qv9qC1GdDmsbkK1xvq=SFxTaQ@mail.gmail.com","threadId":"64818","inReplyTo":"21D9FA76-F382-483E-817F-C3947C939D16@gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T09:37:09Z","receivedAt":"2026-02-03T09:37:21Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Lucas and everyone,\n\nOn Thu, Jan 29, 2026 at 9:41 PM Lucas Seiki Oshiro\n wrote:\n>\n>\n> > 6) Improve `git repo info` so it can show more information than now.\n>\n> From my side, I have these features in my local backlog:\n>\n> - remove the dependency on `the_repository`\n> - use the category as key\n> - add the path-related values (copied from git-rev-parse \"Options for\n> Files\"):\n> - git-dir\n> - common-dir\n> - toplevel\n> - superproject-working-tree\n> - add more values currently obtained through\n> `git rev-parse --git-path`:\n> - grafts file\n> - index file\n> - objects directory\n> - hooks directory\n> - git-prefix\n> - other paths that are adjusted by update_common_dir()\n>\n> I already started to add those path-related values [1], but I think\n> that the major problem is deciding whether we should use relative or\n> absolute paths.\n>\n> I also think that we have room for other information that we retrieve\n> through commands other than git-rev-parse.\n\nThanks a lot for this. I have used it in the new SoC-2026-Ideas page I\njust added:\n\nhttps://git.github.io/SoC-2026-Ideas/\n\nIt contains the 3 following projects:\n\n1) Refactoring in order to reduce Git's global state\n\n2) Improve the new `git repo` command\n\n3) Complete and extend the `remote-object-info` command for `git cat-file`\n\nI have removed myself from the potential mentors of project 2), where\nI used material from your email.\n\nOtherwise everyone who said they were interested in (co-)mentoring\nshould be listed as a potential mentor of each of these projects. Feel\nfree to send MRs or just email requests and I will remove you.\n\nWe can still add more projects (and potential (co-)mentors) or maybe\nsplit project 2) into 2 separate projects (one for `git repo info` and\nthe other one for `git repo structure`). We can also refine the\nprojects.\n\nFeel free to send PRs or patches!\n\n> > I would be willing to mentor any of them, but I don't have much\n> > knowledge on `git repo`, so I think it makes more sense for me to\n> > avoid 6) and 7).\n>\n> If you want, I can share with you some information about\n> git-repo-info.\n\nThanks but I prefer to plan to mentor another project for now.\n\n> I really appreciate initiatives like git-repo-structure and\n> git-history that bring features from other tools that make Git\n> easier to use. This week, I was talked independently with two\n> friends about how git-blame can be misleading sometimes since it\n> only shows the last change in a line. One of them really likes\n> `git log -S` for \"blaming\" strings and thinks that it's a too\n> powerful feature that is hidden inside git-log. The other one\n> showed me Cregit [3], a tool for blaming based on tokens\n> instead of lines. A \"string blame\" or a \"token blame\" could be\n> a nice GSoC project (but maybe for future editions).\n\nI think it's too much work and too risky at this point for a SGoC. It\ncould require a lot of discussions on the mailing list before there is\nsome consensus on the command and the way it should be implemented.\n\nIf there was already some kind of consensus about a new command and\nhow it should work my opinion could be different, but for this year,\nyeah, let's just pass on this one.\n\nThanks.\n"},{"id":"535041","messageId":"CAP8UFD3BM1TOK+KUPp-BztCH-vOi8aqjNDN2hXO8bogG_cnWsg@mail.gmail.com","threadId":"64818","inReplyTo":"CAOLa=ZTK-PdJAYfDVPW3qLN+nBCe71Q=E8xohJzbFK=EH8sNkA@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T09:46:41Z","receivedAt":"2026-02-03T09:46:53Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Karthik,\n\nOn Fri, Jan 30, 2026 at 10:32 AM Karthik Nayak wrote:\n\n> I'd be willing to mentor any of the projects listed. I have a little\n> context in all of these, but that's a good reason to understand more :)\n\nThanks for being willing to mentor any of the projects. It will likely\nhelp us better manage the different possibilities.\n\n> Maybe we can also decide how many projects we are willing to mentor this\n> year?\n\nI don't think we need to decide right now. Let's wait until everyone\nhas stated their preferences. It might happen that other projects get\nproposed or that some mentors agree on (co-)mentoring more than one\nproject.\n"},{"id":"535046","messageId":"CAP8UFD07yEVibYL-DwmRj4AQtdbE600LwQDR3Nf5j9FxnQ+mnQ@mail.gmail.com","threadId":"64818","inReplyTo":"CAP8UFD0qtn_1VAA1SiAMjGVF7Qv9qC1GdDmsbkK1xvq=SFxTaQ@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T10:08:43Z","receivedAt":"2026-02-03T10:08:56Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Feb 3, 2026 at 10:37 AM Christian Couder\n wrote:\n\n> Otherwise everyone who said they were interested in (co-)mentoring\n> should be listed as a potential mentor of each of these projects.\n\nLucas, Justin, Siddharth, Ayush and Chandra,\n\nI have also invited you as \"Mentor\" into the Git org on the GSoC\nwebsite. Let me know if you haven't received the invite or if you have\nissues with it.\n\nKaartic, and Karthik,\n\nYou should still be Org Admin and Mentor respectively for the Git org\non the GSoC website.\n\nI have removed everyone else, but please let me know if you still want\nto participate.\n"},{"id":"535054","messageId":"CAP8UFD3Bf9y-sKfFXBXmq54MQ7AAgJ+5B5O0Yak==s2vUUXruw@mail.gmail.com","threadId":"64818","inReplyTo":"CAP8UFD07yEVibYL-DwmRj4AQtdbE600LwQDR3Nf5j9FxnQ+mnQ@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T10:22:52Z","receivedAt":"2026-02-03T10:23:05Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Feb 3, 2026 at 11:08 AM Christian Couder\n wrote:\n>\n> On Tue, Feb 3, 2026 at 10:37 AM Christian Couder\n> wrote:\n>\n> > Otherwise everyone who said they were interested in (co-)mentoring\n> > should be listed as a potential mentor of each of these projects.\n>\n> Lucas, Justin, Siddharth, Ayush and Chandra,\n>\n> I have also invited you as \"Mentor\" into the Git org on the GSoC\n> website. Let me know if you haven't received the invite or if you have\n> issues with it.\n>\n> Kaartic, and Karthik,\n>\n> You should still be Org Admin and Mentor respectively for the Git org\n> on the GSoC website.\n>\n> I have removed everyone else, but please let me know if you still want\n> to participate.\n\nI have also applied for the Git project as a GSoC 2026 Organization as\nthe deadline was today at 18:00 UTC.\n"},{"id":"535056","messageId":"CAP8UFD15Fkx0t4DYcWjK+WgeZBOzfYNyOePQXGU46Fyf4+pFgA@mail.gmail.com","threadId":"64818","inReplyTo":"CA+J6zkSo1LuFUdTU8m6z4vANrJ2r88EV6RDDC_0ZW3bWec2v2Q@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T10:32:57Z","receivedAt":"2026-02-03T10:33:10Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Chandra,\n\nOn Thu, Jan 22, 2026 at 3:43 PM Chandra Pratap\n wrote:\n> On Thu, 22 Jan 2026, 10:38 Kaartic Sivaraam, wrote:\n\n> > I would be glad to help as an org-Admin this year too. I could act as a fallback mentor in case any mentor / co-mentor becomes unavailable during a particular period of the program.\n> >\n> > I also Cc-ed Chandra Pratap as they expressed interest to be a co-mentor before.\n>\n> I'd be glad to help as a co-mentor. I think I'd be able to best help\n> with project ideas related to reftable or testing, seeing how I worked\n> on reftable tests in my GSoC project, but please let me know if I can\n> help with anything else as well!\n\nThanks for volunteering!\n\nWe don't have project ideas related to reftable or testing in our idea\nlist, but we could add some. If you have preferences among the\nprojects listed there, let us know though.\n"},{"id":"535061","messageId":"CA+J6zkR0tvv1b7db+jQ_XW4ft3_p07bCJOm96B30VKx1abpF0w@mail.gmail.com","threadId":"64818","inReplyTo":"CAP8UFD15Fkx0t4DYcWjK+WgeZBOzfYNyOePQXGU46Fyf4+pFgA@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Chandra Pratap","fromEmail":"chandrapratap3519@gmail.com","sentAt":"2026-02-03T14:15:21Z","receivedAt":"2026-02-03T14:15:48Z","isPatch":false,"sender":{"key":"chandrapratap3519@gmail.com","avatar":null},"body":"On Tue, 3 Feb 2026 at 16:03, Christian Couder\n wrote:\n>\n> Hi Chandra,\n>\n> On Thu, Jan 22, 2026 at 3:43 PM Chandra Pratap\n> wrote:\n> > On Thu, 22 Jan 2026, 10:38 Kaartic Sivaraam, wrote:\n>\n> > > I would be glad to help as an org-Admin this year too. I could act as a fallback mentor in case any mentor / co-mentor becomes unavailable during a particular period of the program.\n> > >\n> > > I also Cc-ed Chandra Pratap as they expressed interest to be a co-mentor before.\n> >\n> > I'd be glad to help as a co-mentor. I think I'd be able to best help\n> > with project ideas related to reftable or testing, seeing how I worked\n> > on reftable tests in my GSoC project, but please let me know if I can\n> > help with anything else as well!\n>\n> Thanks for volunteering!\n>\n> We don't have project ideas related to reftable or testing in our idea\n> list, but we could add some. If you have preferences among the\n> projects listed there, let us know though.\n\nAmong the present ideas, I think I will be best able to help with \"Complete\nand extend the remote-object-info command for git cat-file\". I could help\nwith the other projects as well but I think my co-mentor(s) would have to\npick up too much slack in that case.\n\nP.S: I did not receive the \"mentorship invite\" that you talked of earlier.\n\nThanks,\nChandra.\n"},{"id":"535089","messageId":"CAP8UFD0oPL1e1wcy5_q_kmrEv-3YkJHVXutgdFHsZ+hLtb+JvA@mail.gmail.com","threadId":"64818","inReplyTo":"CA+J6zkR0tvv1b7db+jQ_XW4ft3_p07bCJOm96B30VKx1abpF0w@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2026-02-03T19:30:33Z","receivedAt":"2026-02-03T19:30:46Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Feb 3, 2026 at 3:15 PM Chandra Pratap\n wrote:\n>\n> On Tue, 3 Feb 2026 at 16:03, Christian Couder\n> wrote:\n\n> > We don't have project ideas related to reftable or testing in our idea\n> > list, but we could add some. If you have preferences among the\n> > projects listed there, let us know though.\n>\n> Among the present ideas, I think I will be best able to help with \"Complete\n> and extend the remote-object-info command for git cat-file\". I could help\n> with the other projects as well but I think my co-mentor(s) would have to\n> pick up too much slack in that case.\n\nFine, I have removed you as a possible mentor for the two other projects then.\n"},{"id":"536659","messageId":"A01D97A5-48EC-4633-B0BE-8C1541156C2A@gmail.com","threadId":"64818","inReplyTo":"CAP8UFD11txMWSfMTvDtcBJuuZA5mKffo6XUyR9LWk2d_N0RRtA@mail.gmail.com","subject":"Re: Git project and GSoC 2026","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-02-22T18:40:19Z","receivedAt":"2026-02-22T18:40:28Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi everyone,\n\n\nOn 16 January 2026 4:36:13 pm IST, Christian Couder wrote:\n>\n>The application period for mentoring organizations to participate in\n>GSoC 2026 is from January 19 to February 3. Let's try to anticipate a\n>bit and decide soon if the Git project wants to participate.\n>\n\nJust to keep this thread updated. Git has been successfuly accepted as a mentoring organization for 2026. Thank you to Christian for organizing. Also, thank you to our community members who've volunteered to mentor students this year: Karthik Nayak, Justin Tobler, Siddharth Asthana, Chandra Pratap and Ayush Chandekar\n\nLet us look forward towards a good summer of code experience for the new contributors who could potentially become long-term members of the community.\n \n\nIt's good to see GSoC related contributions in the list already. Similarly, we'll be seeing more candidates participating by sending out their micro-projects. Let's give them a good guidance :-)\n\nThat said, we have the ideas listed in our ideas page. Feel free to suggest more ideas if you have any.\n\n \n\nVolunteer mentors willing to mentor students are always welcome. Let us know if you're interested.\n\n-- \nSivaraam\n\nSent from my Android device with K-9 Mail. Please excuse my brevity.\n"}]}