{"thread":{"id":"57317","subject":"Git in GSoC 2022?","startedAt":"2022-01-26T18:29:38Z","lastAt":"2022-03-09T19:57:38Z","messageCount":36,"participants":["Kaartic Sivaraam","Taylor Blau","Bagas Sanjaya","Christian Couder","Derrick Stolee","ZheNing Hu","Philip Oakley","Hariom verma","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"446983","messageId":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","threadId":"57317","inReplyTo":null,"subject":"Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-01-26T18:29:16Z","receivedAt":"2022-01-26T18:29:38Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi all,\n\nGSoC 2022 is approaching. The timeline has been released [1].\nMentoring organizations should submit applications between\nFebruary 7 and 21 at 1800 UTC. So, I thought I'll kick off\nthe discussion about our plans for GSoC 2022.\n\nFirst, are we interested in participating in the 2022 round of\nGSoC?\n\nIf we are interested in participating we need:\n\n   - Volunteers who are wiling to act as mentors. I would be\n     willing to be volunteer myself as a mentor for one student.\n  \n   - Microprojects: I believe we could repurpose the Outreachy\n     microproject ideas[2] for GSoC too. If others have suggestions\n     for microproject ideas, please share them.\n\n   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n     but both were picked by GSoC students the previous year. So,\n     we would need new ones this year.\n\n     Taylor showed interest in a bitmap-related project during\n     the Outreachy application period [4]. Taylor, are you still\n     interested in mentoring a bitmap-related project? Would it\n     be possible for you to do so for the upcoming GSoC?\n\n\nAlso, wanted to note that GSoC has some changes in store for\nthis year [5]. Concisely they are:\n\n   - Expanding eligibility: the program is now open to non-students.\n\n   - Multiple Sizes of Projects: In 2021, project size was reduced\n     (~175 hours). This year, both medium sized projects (~175 hours)\n     and large projects (~350 hours) are supported.\n\n     GSoC organizers recommend communities to have both medium _and_\n     large size projects.\n\n   - Increased timing flexibility: rather than a mandatory 12-week\n     program, projects can be extended for up to 22 weeks by the\n     mentor and the contributors.\n\nSee the blog [5] for more details.\n\n\n[ References ]\n\n[1]: https://developers.google.com/open-source/gsoc/timeline\n\n[2]: https://git.github.io/Outreachy-23-Microprojects/\n\n[3]: https://git.github.io/SoC-2021-Ideas/\n\n[4]: https://public-inbox.org/git/YVTM+WQH%2FUyhVeTz@nand.local/\n\n[5]: https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html\n\n-- \nSivaraam\n"},{"id":"446989","messageId":"YfGpjm8mCkWIPM6V@nand.local","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2022-01-26T20:05:34Z","receivedAt":"2022-01-26T20:05:37Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"Hi Kaartic,\n\nThanks for organizing this.\n\nOn Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:\n> First, are we interested in participating in the 2022 round of\n> GSoC?\n\nI think it would be great to participate this year, provided that we can\ncome up with some interesting projects and mentors to help out.\n\n>     Taylor showed interest in a bitmap-related project during\n>     the Outreachy application period [4]. Taylor, are you still\n>     interested in mentoring a bitmap-related project? Would it\n>     be possible for you to do so for the upcoming GSoC?\n\nI'm available and interested in mentoring. I don't think I found many\ninterested folks via Outreachy who wanted to work on bitmaps, but I\nthink it's worth trying again via GSoC. I can rejigger the proposed\nprojects there a bit, too.\n\n(I figured that it would be fun to have an intern with fairly wide\ndiscretion over what they could work on, but it might be better for some\nfolks to have a clearer idea ahead of time.)\n\n> [4]: https://public-inbox.org/git/YVTM+WQH%2FUyhVeTz@nand.local/\n\nThanks,\nTaylor\n"},{"id":"447036","messageId":"9d2e58ab-2d8f-0797-84ed-0c1e8941edaa@gmail.com","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2022-01-27T03:55:08Z","receivedAt":"2022-01-27T03:55:19Z","isPatch":false,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 27/01/22 01.29, Kaartic Sivaraam wrote:\n>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>      but both were picked by GSoC students the previous year. So,\n>      we would need new ones this year.\n\nI have several project ideas:\n\n   - Document the \"binary diff\" format. Right now we have documentation\n     for all diff formats used in Git, except for binary diff. Hint:\n     read `diff.c`\n   - Rewrite `git-request-pull.sh` in C. Currently the shell script\n     implementation hard-codes message template and only outputs to\n     stdout (though can be redirected to a file using shell means).\n     In the C version, message template can be configured (with the\n     default is same as current version) and introduces new\n     `-o/--output` option to specify output file.\n  \n-- \nAn old man doll... just what I always wanted! - Clara\n"},{"id":"447058","messageId":"CAP8UFD1Mqv=MUcdjjhTpOkP0yWpnv9Jr=aB5G+4XmAqWsJBX4g@mail.gmail.com","threadId":"57317","inReplyTo":"YfGpjm8mCkWIPM6V@nand.local","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-01-27T09:32:17Z","receivedAt":"2022-01-27T09:32:30Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:\n>\n> Hi Kaartic,\n>\n> Thanks for organizing this.\n\nYeah, thanks!\n\n> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:\n> > First, are we interested in participating in the 2022 round of\n> > GSoC?\n>\n> I think it would be great to participate this year, provided that we can\n> come up with some interesting projects and mentors to help out.\n\nI agree.\n\n> >     Taylor showed interest in a bitmap-related project during\n> >     the Outreachy application period [4]. Taylor, are you still\n> >     interested in mentoring a bitmap-related project? Would it\n> >     be possible for you to do so for the upcoming GSoC?\n>\n> I'm available and interested in mentoring. I don't think I found many\n> interested folks via Outreachy who wanted to work on bitmaps, but I\n> think it's worth trying again via GSoC. I can rejigger the proposed\n> projects there a bit, too.\n\nI am also available and interested in mentoring and I can reuse a\nproject prepared for the last Outreachy round too.\n"},{"id":"447059","messageId":"CAP8UFD38WDwMKf3tMKGt6hMxmsuZk2JkDRJaOZsXFqHvbVLRLQ@mail.gmail.com","threadId":"57317","inReplyTo":"9d2e58ab-2d8f-0797-84ed-0c1e8941edaa@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-01-27T09:44:09Z","receivedAt":"2022-01-27T09:44:23Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Jan 27, 2022 at 4:55 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:\n>\n> On 27/01/22 01.29, Kaartic Sivaraam wrote:\n> >    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n> >      but both were picked by GSoC students the previous year. So,\n> >      we would need new ones this year.\n>\n> I have several project ideas:\n>\n>    - Document the \"binary diff\" format. Right now we have documentation\n>      for all diff formats used in Git, except for binary diff. Hint:\n>      read `diff.c`\n\nIt seems a bit small as a project idea. Also we usually propose code\nrelated projects. It might be a good one for Google Season of Docs\nthough:\n\nhttps://developers.google.com/season-of-docs/\n\nBut I don't think we have ever participated in it.\n\n>    - Rewrite `git-request-pull.sh` in C. Currently the shell script\n>      implementation hard-codes message template and only outputs to\n>      stdout (though can be redirected to a file using shell means).\n>      In the C version, message template can be configured (with the\n>      default is same as current version) and introduces new\n>      `-o/--output` option to specify output file.\n\nIn https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/\nDscho put this script in the \"Probably better to leave them as shell\nscripts\" category, so you might want to explain a bit more what would\nbe the benefits of converting it. Also would you be interested in\nmentoring or co-mentoring a GSoC student working on this?\n\nThanks!\n"},{"id":"447080","messageId":"ca51848c-d3e1-7f85-0268-ab4c999ea2bd@gmail.com","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2022-01-27T14:39:11Z","receivedAt":"2022-01-27T14:39:19Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 1/26/2022 1:29 PM, Kaartic Sivaraam wrote:\n> If we are interested in participating we need:\n> \n>   - Volunteers who are wiling to act as mentors. I would be\n>     willing to be volunteer myself as a mentor for one student.\n>  \n>   - Microprojects: I believe we could repurpose the Outreachy\n>     microproject ideas[2] for GSoC too. If others have suggestions\n>     for microproject ideas, please share them.\n> \n>   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>     but both were picked by GSoC students the previous year. So,\n>     we would need new ones this year.\n\nOne project that could be interesting for GSoC (and the timing\nshould work out) is to complete the sparse index integrations for\nsome of the less critical commands. Some examples include 'git mv'\nand 'git rm', I think.\n\nThis of course depends on some ongoing work to integrate more of\nthe critical commands that we implemented early in microsoft/git,\nsuch as Victoria's current series which is leading to a 'git stash'\nintegration and a series I have waiting in the wings for a 'git\nsparse-checkout' integration.\n\nHowever, I think we have a decent paved-path for a new contributor\nto jump in and get started on the remaining commands. The granularity\nmeans that the project has multiple milestones that can be hit\nwithout an all-in-one series.\n\n>   - Multiple Sizes of Projects: In 2021, project size was reduced\n>     (~175 hours). This year, both medium sized projects (~175 hours)\n>     and large projects (~350 hours) are supported.\n> \n>     GSoC organizers recommend communities to have both medium _and_\n>     large size projects.\n\nI think this project would fit in the \"medium\" category.\n\nThanks,\n-Stolee\n"},{"id":"447082","messageId":"CAOLTT8QzaM70_jk4bOnBAHFaNjf6d_WSNp4h-qLWr2eJLdErBg@mail.gmail.com","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2022-01-27T15:00:51Z","receivedAt":"2022-01-27T15:01:06Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Hi, all,\n\nKaartic Sivaraam <kaartic.sivaraam@gmail.com> 于2022年1月27日周四 02:29写道：\n>\n> Hi all,\n>\n> GSoC 2022 is approaching. The timeline has been released [1].\n> Mentoring organizations should submit applications between\n> February 7 and 21 at 1800 UTC. So, I thought I'll kick off\n> the discussion about our plans for GSoC 2022.\n>\n> First, are we interested in participating in the 2022 round of\n> GSoC?\n>\n> If we are interested in participating we need:\n>\n>    - Volunteers who are wiling to act as mentors. I would be\n>      willing to be volunteer myself as a mentor for one student.\n>\n>    - Microprojects: I believe we could repurpose the Outreachy\n>      microproject ideas[2] for GSoC too. If others have suggestions\n>      for microproject ideas, please share them.\n>\n>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>      but both were picked by GSoC students the previous year. So,\n>      we would need new ones this year.\n>\n>      Taylor showed interest in a bitmap-related project during\n>      the Outreachy application period [4]. Taylor, are you still\n>      interested in mentoring a bitmap-related project? Would it\n>      be possible for you to do so for the upcoming GSoC?\n>\n>\n\nI've been busy preparing for some internships lately and may not have\nenough time as a mentor to help this year's GSOC students, but I can\noccasionally provide my review for interesting projects this year.\n\nThanks.\n--\nZheNing Hu\n"},{"id":"447283","messageId":"d7000284-0964-e929-681f-a902b2b3b917@gmail.com","threadId":"57317","inReplyTo":"CAOLTT8QzaM70_jk4bOnBAHFaNjf6d_WSNp4h-qLWr2eJLdErBg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-01-29T17:43:20Z","receivedAt":"2022-01-29T17:43:29Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 27/01/22 8:30 pm, ZheNing Hu wrote:\n> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> 于2022年1月27日周四 02:29写道：\n>>\n>> GSoC 2022 is approaching. The timeline has been released [1].\n>> Mentoring organizations should submit applications between\n>> February 7 and 21 at 1800 UTC. So, I thought I'll kick off\n>> the discussion about our plans for GSoC 2022.\n>>\n>> First, are we interested in participating in the 2022 round of\n>> GSoC?\n>>\n>> If we are interested in participating we need:\n>>\n>>     - Volunteers who are wiling to act as mentors. I would be\n>>       willing to be volunteer myself as a mentor for one student.\n>>\n>>     - Microprojects: I believe we could repurpose the Outreachy\n>>       microproject ideas[2] for GSoC too. If others have suggestions\n>>       for microproject ideas, please share them.\n>>\n>>     - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>>       but both were picked by GSoC students the previous year. So,\n>>       we would need new ones this year.\n>>\n>>       Taylor showed interest in a bitmap-related project during\n>>       the Outreachy application period [4]. Taylor, are you still\n>>       interested in mentoring a bitmap-related project? Would it\n>>       be possible for you to do so for the upcoming GSoC?\n>>\n>>\n> \n> I've been busy preparing for some internships lately and may not have\n> enough time as a mentor to help this year's GSOC students, but I can\n> occasionally provide my review for interesting projects this year.\n> \n\nNo worries. Reviews would be great when you're able to find time for them.\nThanks! :-)\n\n-- \nSivaraam\n"},{"id":"447299","messageId":"f850f137-79a2-6fcb-cd2f-de382c314fad@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD1Mqv=MUcdjjhTpOkP0yWpnv9Jr=aB5G+4XmAqWsJBX4g@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-01-29T18:09:26Z","receivedAt":"2022-01-29T18:09:33Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 27/01/22 3:02 pm, Christian Couder wrote:\n> Hi,\n> \n> On Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:\n> \n>> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:\n>>> First, are we interested in participating in the 2022 round of\n>>> GSoC?\n>>\n>> I think it would be great to participate this year, provided that we can\n>> come up with some interesting projects and mentors to help out.\n> \n> I agree.\n> \n\nGreat. :)\n\n>>>      Taylor showed interest in a bitmap-related project during\n>>>      the Outreachy application period [4]. Taylor, are you still\n>>>      interested in mentoring a bitmap-related project? Would it\n>>>      be possible for you to do so for the upcoming GSoC?\n>>\n>> I'm available and interested in mentoring. I don't think I found many\n>> interested folks via Outreachy who wanted to work on bitmaps, but I\n>> think it's worth trying again via GSoC. I can rejigger the proposed\n>> projects there a bit, too.\n> \n> I am also available and interested in mentoring and I can reuse a\n> project prepared for the last Outreachy round too.\n> \n\nThat's nice.\n\nI've opened a PR in the git.github.io repo to create a mostly empty ideas\ndocument for GSoC 2022. Here's the link for reference:\n\n   https://github.com/git/git.github.io/pull/540\n\nOnce that's merged, anyone could feel free to open PRs with their\nideas to this document:\n\n   https://github.com/git/git.github.io/blob/master/SoC-2022-Ideas.md\n\n   (note: currently returns a 404; it should work if the PR is merged)\n\nAlternatively, if you share information about a project idea here, I would\nbe glad to add them to the document. For some motivation, you could see the\nproject ideas page of 2021:\n\n   https://git.github.io/SoC-2021-Ideas/\n\n-- \nSivaraam\n"},{"id":"447302","messageId":"aa324a28-2336-c7b0-c1b7-ca4d440d9ff5@gmail.com","threadId":"57317","inReplyTo":"ca51848c-d3e1-7f85-0268-ab4c999ea2bd@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-01-29T18:19:54Z","receivedAt":"2022-01-29T18:20:02Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 27/01/22 8:09 pm, Derrick Stolee wrote:\n> On 1/26/2022 1:29 PM, Kaartic Sivaraam wrote:\n>> If we are interested in participating we need:\n>>\n>>    - Volunteers who are wiling to act as mentors. I would be\n>>      willing to be volunteer myself as a mentor for one student.\n>>   \n>>    - Microprojects: I believe we could repurpose the Outreachy\n>>      microproject ideas[2] for GSoC too. If others have suggestions\n>>      for microproject ideas, please share them.\n>>\n>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>>      but both were picked by GSoC students the previous year. So,\n>>      we would need new ones this year.\n> \n> One project that could be interesting for GSoC (and the timing\n> should work out) is to complete the sparse index integrations for\n> some of the less critical commands. Some examples include 'git mv'\n> and 'git rm', I think.\n> \n> This of course depends on some ongoing work to integrate more of\n> the critical commands that we implemented early in microsoft/git,\n> such as Victoria's current series which is leading to a 'git stash'\n> integration and a series I have waiting in the wings for a 'git\n> sparse-checkout' integration.\n> \n> However, I think we have a decent paved-path for a new contributor\n> to jump in and get started on the remaining commands. The granularity\n> means that the project has multiple milestones that can be hit\n> without an all-in-one series.\n> \n\nSounds good.\n\nAs I mentioned up thread, you could feel free to share the project\ndescription here or open a PR by adding it directly to this document:\n\n   https://github.com/git/git.github.io/blob/master/SoC-2022-Ideas.md\n\n   (note: currently returns a 404; it should work when the\n    related PR [pr-1] is merged)\n\nJust to be sure, would you be willing to mentor in case a student\npicks this project?\n\n[pr-1]: https://github.com/git/git.github.io/pull/540\n\n>>    - Multiple Sizes of Projects: In 2021, project size was reduced\n>>      (~175 hours). This year, both medium sized projects (~175 hours)\n>>      and large projects (~350 hours) are supported.\n>>\n>>      GSoC organizers recommend communities to have both medium _and_\n>>      large size projects.\n> \n> I think this project would fit in the \"medium\" category.\n>\n\n-- \nSivaraam\n"},{"id":"447303","messageId":"22e484c3-f313-5335-5f34-5df019b7ee98@gmail.com","threadId":"57317","inReplyTo":"nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-01-29T18:36:59Z","receivedAt":"2022-01-29T18:37:05Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Dscho,\n\nOn 28/01/22 4:15 pm, Johannes Schindelin wrote:\n> \n> A project that I would personally find a lot of fun, with a great impact,\n> and never really talked about on this list, would be to offer a good\n> replacement for the `git daemon`: its purpose is to make it easy to stand\n> up an ad-hoc server, to allow developers to clone/fetch (and even push, if\n> that is enabled) via the network, unauthenticated. Now, the git://\n> protocol has served us well in the beginning, but it is increasingly\n> obvious that we should use https:// wherever possible. Wouldn't it be fun\n> to have a `git daemon` that talks https:// by default, maybe even\n> optionally offering a real web UI via gitweb? This is not as huge of a\n> project as it sounds, Jeff Hostetler already did a ton of work to that end\n> over in the Microsoft fork of Git: the `test-gvfs-protocol` helper is used\n> in the regression tests to offer Git repositories via http:// and the\n> biggest task to convert this to an HTTP-speaking `git daemon` would be to\n> rip out the GVFS parts. After that, HTTPS support could be added.\n> \n\nSounds interesting. Would you mind drafting this into a project proposal\nfor GSoC. Then we could add it to the list of ideas document [1].\n\nAlso, would you be willing to mentor a student in case they pick this\nproject? Or would you rather leave it to others?\n\n[1]: https://github.com/git/git.github.io/pull/540\n\n-- \nSivaraam\n"},{"id":"447545","messageId":"356a8f62-9ab7-9c80-6d5f-337a2dc4049a@gmail.com","threadId":"57317","inReplyTo":"aa324a28-2336-c7b0-c1b7-ca4d440d9ff5@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2022-02-02T17:42:18Z","receivedAt":"2022-02-02T17:42:24Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 1/29/2022 1:19 PM, Kaartic Sivaraam wrote:\n> On 27/01/22 8:09 pm, Derrick Stolee wrote:\n>> On 1/26/2022 1:29 PM, Kaartic Sivaraam wrote:\n>>> If we are interested in participating we need:\n>>>\n>>>    - Volunteers who are wiling to act as mentors. I would be\n>>>      willing to be volunteer myself as a mentor for one student.\n>>>      - Microprojects: I believe we could repurpose the Outreachy\n>>>      microproject ideas[2] for GSoC too. If others have suggestions\n>>>      for microproject ideas, please share them.\n>>>\n>>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>>>      but both were picked by GSoC students the previous year. So,\n>>>      we would need new ones this year.\n>>\n>> One project that could be interesting for GSoC (and the timing\n>> should work out) is to complete the sparse index integrations for\n>> some of the less critical commands. Some examples include 'git mv'\n>> and 'git rm', I think.\n>>\n>> This of course depends on some ongoing work to integrate more of\n>> the critical commands that we implemented early in microsoft/git,\n>> such as Victoria's current series which is leading to a 'git stash'\n>> integration and a series I have waiting in the wings for a 'git\n>> sparse-checkout' integration.\n>>\n>> However, I think we have a decent paved-path for a new contributor\n>> to jump in and get started on the remaining commands. The granularity\n>> means that the project has multiple milestones that can be hit\n>> without an all-in-one series.\n>>\n> \n> Sounds good.\n> \n> As I mentioned up thread, you could feel free to share the project\n> description here or open a PR by adding it directly to this document:\n> \n>   https://github.com/git/git.github.io/blob/master/SoC-2022-Ideas.md\n> \n>   (note: currently returns a 404; it should work when the\n>    related PR [pr-1] is merged)\n> \n> Just to be sure, would you be willing to mentor in case a student\n> picks this project?\n\nVictoria Dye and I are willing to co-mentor if a student picks this\nproject.\n\nI'll make a PR that adds a description to the linked doc soon.\n \nThanks,\n-Stolee\n\n"},{"id":"447609","messageId":"730fb307-3bc7-b52f-49c1-d83b5ab55c95@iee.email","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2022-02-03T14:12:13Z","receivedAt":"2022-02-03T14:12:18Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"On 26/01/2022 18:29, Kaartic Sivaraam wrote:\n> If we are interested in participating we need:\n>\n>   - Volunteers who are wiling to act as mentors. I would be\n>     willing to be volunteer myself as a mentor for one student.\n>  \n>   - Microprojects: I believe we could repurpose the Outreachy\n>     microproject ideas[2] for GSoC too. If others have suggestions\n>     for microproject ideas, please share them.\n>\n>   - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>     but both were picked by GSoC students the previous year. So,\n>     we would need new ones this year.\nGit Demonstration Repositories\n=============================\n\nOne idea/concept that I've had that might be suitable for a project\neither here or within the Google Season of Docs is to generate\ndemonstration repositories that match the examples used in the\ndocumentation and parts of the test suite to help users explore and\nunderstand the concepts that are being documented in the man pages.\n\nIt's more than a classic coding problem because it impinges on a lot of\nsubjective and admin areas but should be fairly beneficial for users.\n\nThe two examples that come to mind are the --show-pulls repo [1], and\nthe 'history simplification' repo [2].\n\nUsing the test suite as the repo generator ensures the Demo Repos are\nreproducible/deterministic.\n\nMy latest thinking is that the repos would be held in-tree under\n/Documentation/RepoBundles and have been exported as bundles by an\nexplicit test_export_function. Of key importance in the project is to\nminimise/eliminate any extra maintainer actions, so once a patch with a\nrepo export is accepted, the flow through the delivery process to user\ninstalls is essentially the same as the man pages.\n\nNot sure if that's fleshed out enough, or if it's at the wrong level for\nGSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.\n\n>\n>     Taylor showed interest in a bitmap-related project during\n>     the Outreachy application period [4]. Taylor, are you still\n>     interested in mentoring a bitmap-related project? Would it\n>     be possible for you to do so for the upcoming GSoC?\n--\nPhilip\n[1] Git log --show-pulls\n{the sha1\nhttps://github.com/git/git/commit/8d049e182e2e213a012e2d6839becfe0e2de79db,\n get the t/tnnnn t/t6012-rev-list-simplify.sh,\n get the docs rev-list #L582-707}\n\n[2] git rev list History simplification\n{get the man page #Lnn\nhttps://github.com/git/git/blob/master/Documentation/rev-list-options.txt#L386-L425,\n get the Chuck Li https://github.com/ChuckTest/git-history-test.git,\n get the gfw\nhttps://groups.google.com/d/msgid/git-users/11286f4a-c961-4d12-91a0-f49e34d8691bn%40googlegroups.com}\n"},{"id":"448305","messageId":"3b112eee-8110-baf6-d7e7-cb25b03c32ff@gmail.com","threadId":"57317","inReplyTo":"730fb307-3bc7-b52f-49c1-d83b5ab55c95@iee.email","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-12T18:12:49Z","receivedAt":"2022-02-12T18:13:01Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 03/02/22 7:42 pm, Philip Oakley wrote:\n> On 26/01/2022 18:29, Kaartic Sivaraam wrote:\n>>\n>>    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]\n>>      but both were picked by GSoC students the previous year. So,\n>>      we would need new ones this year.\n> Git Demonstration Repositories\n> =============================\n> \n> One idea/concept that I've had that might be suitable for a project\n> either here or within the Google Season of Docs is to generate\n> demonstration repositories that match the examples used in the\n> documentation and parts of the test suite to help users explore and\n> understand the concepts that are being documented in the man pages.\n> \n> It's more than a classic coding problem because it impinges on a lot of\n> subjective and admin areas but should be fairly beneficial for users.\n> \n\nThis does sound like a good idea.\n\n> The two examples that come to mind are the --show-pulls repo [1], and\n> the 'history simplification' repo [2].\n> \n> Using the test suite as the repo generator ensures the Demo Repos are\n> reproducible/deterministic.\n> \n> My latest thinking is that the repos would be held in-tree under\n> /Documentation/RepoBundles and have been exported as bundles by an\n> explicit test_export_function. Of key importance in the project is to\n> minimise/eliminate any extra maintainer actions, so once a patch with a\n> repo export is accepted, the flow through the delivery process to user\n> installs is essentially the same as the man pages.\n>\n\nWe could possibly include this one in the idea list but I suppose we might\nneed a more concrete idea on what needs to be done as part of this project.\nThat would help very much with guiding the student during the project\nperiod.\n\nWe also need to know if the end result of such a project would be an\nacceptable contribution to the project. What it would take for the contribution\nto be acceptable? etc.\n\nJust to make it clear, I'm trying to think through on what we need to do to\nmake this a GSoC idea proposal.\n  \n> Not sure if that's fleshed out enough, or if it's at the wrong level for\n> GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.\n> \n\nThat's nice. Thanks for volunteering.\n\nOn a related note, the organization registrations are now open for this year.\nThe deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is\nplanning on applying for Git. In case no one else beats me to it, I plan on\napplying for Git around February 15 17:00 UTC.\n\n-- \nSivaraam\n"},{"id":"448340","messageId":"CAP8UFD1BYm-_p=JYw3GELsk1=hR9-o7cxEowtnrKPumi0Gk8kg@mail.gmail.com","threadId":"57317","inReplyTo":"3b112eee-8110-baf6-d7e7-cb25b03c32ff@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-02-13T09:33:17Z","receivedAt":"2022-02-13T09:33:33Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> On 03/02/22 7:42 pm, Philip Oakley wrote:\n\n> > My latest thinking is that the repos would be held in-tree under\n> > /Documentation/RepoBundles and have been exported as bundles by an\n> > explicit test_export_function. Of key importance in the project is to\n> > minimise/eliminate any extra maintainer actions, so once a patch with a\n> > repo export is accepted, the flow through the delivery process to user\n> > installs is essentially the same as the man pages.\n>\n> We could possibly include this one in the idea list but I suppose we might\n> need a more concrete idea on what needs to be done as part of this project.\n> That would help very much with guiding the student during the project\n> period.\n>\n> We also need to know if the end result of such a project would be an\n> acceptable contribution to the project. What it would take for the contribution\n> to be acceptable? etc.\n\nYeah, I think this is the main issue with this idea. We have a section\nnamed \"Note about refactoring projects versus projects that implement\nnew features\" in\nhttps://git.github.io/General-Application-Information/ explaining why\nprojects implementing new things can be a bad idea, and what can be\ndone about it.\n\n> Just to make it clear, I'm trying to think through on what we need to do to\n> make this a GSoC idea proposal.\n>\n> > Not sure if that's fleshed out enough, or if it's at the wrong level for\n> > GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.\n>\n> That's nice. Thanks for volunteering.\n\nYeah, thanks for volunteering anyway!\n\n> On a related note, the organization registrations are now open for this year.\n> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is\n> planning on applying for Git. In case no one else beats me to it, I plan on\n> applying for Git around February 15 17:00 UTC.\n\nI was thinking about applying for Git, but I am glad that you plan to\ndo it. I will try to add some project ideas to SoC-2022-Ideas.md\nbefore February 15.\n\nThanks,\nChristian.\n"},{"id":"448342","messageId":"CAP8UFD2FfJA1ruhxzv3tcxhsssHBeHGCbGFDiz+-fFmpx39Gqg@mail.gmail.com","threadId":"57317","inReplyTo":"CAP8UFD1Mqv=MUcdjjhTpOkP0yWpnv9Jr=aB5G+4XmAqWsJBX4g@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-02-13T13:35:34Z","receivedAt":"2022-02-13T13:35:51Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thu, Jan 27, 2022 at 10:32 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n> On Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:\n\n> > I'm available and interested in mentoring. I don't think I found many\n> > interested folks via Outreachy who wanted to work on bitmaps, but I\n> > think it's worth trying again via GSoC. I can rejigger the proposed\n> > projects there a bit, too.\n\nTaylor, it would be nice if you could add this bitmap project to\nSoC-2022-Ideas.md soon or at least before the February 21 deadline.\n\n> I am also available and interested in mentoring and I can reuse a\n> project prepared for the last Outreachy round too.\n\nI added the \"Unify ref-filter formats with other pretty formats\" to\ncontinue Hariom Verma's work during GSoC 2020. I would be happy to\nco-mentor it if someone is interested to co-mentor it with me.\n"},{"id":"448431","messageId":"f58ad14f-f4bf-0f0a-24ba-98ab80bf0dc5@iee.email","threadId":"57317","inReplyTo":"CAP8UFD1BYm-_p=JYw3GELsk1=hR9-o7cxEowtnrKPumi0Gk8kg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2022-02-15T15:05:08Z","receivedAt":"2022-02-15T15:05:15Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Hi Christian,\n\nOn 13/02/2022 09:33, Christian Couder wrote:\n> On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n>> On 03/02/22 7:42 pm, Philip Oakley wrote:\n>>> My latest thinking is that the repos would be held in-tree under\n>>> /Documentation/RepoBundles and have been exported as bundles by an\n>>> explicit test_export_function. Of key importance in the project is to\n>>> minimise/eliminate any extra maintainer actions, so once a patch with a\n>>> repo export is accepted, the flow through the delivery process to user\n>>> installs is essentially the same as the man pages.\n>> We could possibly include this one in the idea list but I suppose we might\n>> need a more concrete idea on what needs to be done as part of this project.\n>> That would help very much with guiding the student during the project\n>> period.\n>>\n>> We also need to know if the end result of such a project would be an\n>> acceptable contribution to the project. What it would take for the contribution\n>> to be acceptable? etc.\n> Yeah, I think this is the main issue with this idea. We have a section\n> named \"Note about refactoring projects versus projects that implement\n> new features\" in\n> https://git.github.io/General-Application-Information/ explaining why\n> projects implementing new things can be a bad idea, and what can be\n> done about it.\n\nI tend to agree. To me, it has all the hall marks of an allegedly\nsimple  'systems' project. The main issues in the mini-project being to\nensure all stakeholders are aligned so that the final coding is easy. I\nhadn't mentioned the number of go-arounds in my head before I settled on\nusing individual bundles as the likely best chance of success for the\nexample repos.\n\nFor these type of ideas, the 'show me the code' mantra, can easily lead\nto misunderstanding, mistaking the toy implementation for concept (\"map\nis not territory\" ;-).\n\nMaybe we do need a 'mini-projects' category to capture these\nnon-refactoring ideas.\n\n>\n>> Just to make it clear, I'm trying to think through on what we need to do to\n>> make this a GSoC idea proposal.\n>>\n>>> Not sure if that's fleshed out enough, or if it's at the wrong level for\n>>> GSoC, or If I'm right as a Mentor, but I'd be happy to co-mentor.\n>> That's nice. Thanks for volunteering.\n> Yeah, thanks for volunteering anyway!\n\nGiven that I'd suggested the min-project, I thought it worthwhile ;-)\n>\n>> On a related note, the organization registrations are now open for this year.\n>> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is\n>> planning on applying for Git. In case no one else beats me to it, I plan on\n>> applying for Git around February 15 17:00 UTC.\n> I was thinking about applying for Git, but I am glad that you plan to\n> do it. I will try to add some project ideas to SoC-2022-Ideas.md\n> before February 15.\n>\n> Thanks,\n> Christian.\n\nA similar mini-project, could be to add a `git branch\n--show-description` and `git branch --show-all-descriptions` along the\nlines of the aliases:\n    brshow = config --get-regexp 'branch.*.description'\n    brshow1 = !git config --get \"branch.$(git rev-parse --abbrev-ref\nHEAD).description\"\n\nFairly simple coding, if acceptable (with ensuing discussions about\nwhether branch descriptions are useful ..)\n\nPhilip\n"},{"id":"448472","messageId":"65abccbe-eaae-5d68-c738-b7f9a3844bbc@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD1BYm-_p=JYw3GELsk1=hR9-o7cxEowtnrKPumi0Gk8kg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-15T20:32:14Z","receivedAt":"2022-02-15T20:32:22Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 13/02/22 3:03 pm, Christian Couder wrote:\n> On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n> \n>> On a related note, the organization registrations are now open for this year.\n>> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is\n>> planning on applying for Git. In case no one else beats me to it, I plan on\n>> applying for Git around February 15 17:00 UTC.\n> \n> I was thinking about applying for Git, but I am glad that you plan to\n> do it. I will try to add some project ideas to SoC-2022-Ideas.md\n> before February 15.\n\nThanks for adding it! I've applied for Git in GSoC 2022. The application\ninformation could be found here:\n\n   https://git.github.io/SoC-2022-Org-Application/\n\nLet me know in case anything needs to be tweaked. I mentioned that we have\n5 mentors available counting Stolee, Victoria, Christian, Taylor and myself.\nAlso, I've invited Christian as an Org Admin. In case anyone else would like\nto volunteer to be an Org Admin, do let me know.\n\nOn a lighter note, the application structure was a bit different than\nprevious years due to the new website. They say that it supports persisting\nthe organization information which should mean less work while applying for\nGSoC in upcoming years.\n\n-- \nSivaraam\n"},{"id":"448473","messageId":"01183a76-24c5-4308-76e3-953a0b76df67@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD2FfJA1ruhxzv3tcxhsssHBeHGCbGFDiz+-fFmpx39Gqg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-15T20:34:52Z","receivedAt":"2022-02-15T20:34:59Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 13/02/22 7:05 pm, Christian Couder wrote:\n> On Thu, Jan 27, 2022 at 10:32 AM Christian Couder\n> <christian.couder@gmail.com> wrote:\n>> On Wed, Jan 26, 2022 at 9:05 PM Taylor Blau <me@ttaylorr.com> wrote:\n> \n>> I am also available and interested in mentoring and I can reuse a\n>> project prepared for the last Outreachy round too.\n> \n> I added the \"Unify ref-filter formats with other pretty formats\" to\n> continue Hariom Verma's work during GSoC 2020. I would be happy to\n> co-mentor it if someone is interested to co-mentor it with me.\n> \n\nI would be willing to co-mentor it with you. In case anyone else\nprefers to co-mentor this one, that's fine too. I can leave it\nto them :)\n\n-- \nSivaraam\n"},{"id":"448497","messageId":"CA+CkUQ9VTs7n9B+ApH1BYC=Uq4yvrZm0fsG0RJB8PVg_BBSCfw@mail.gmail.com","threadId":"57317","inReplyTo":"CAP8UFD2FfJA1ruhxzv3tcxhsssHBeHGCbGFDiz+-fFmpx39Gqg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Hariom verma","fromEmail":"hariom18599@gmail.com","sentAt":"2022-02-15T23:18:17Z","receivedAt":"2022-02-15T23:18:33Z","isPatch":false,"sender":{"key":"hariom18599@gmail.com","avatar":"https://avatars.githubusercontent.com/u/37576387?v=4"},"body":"Hi,\n\nOn Mon, Feb 14, 2022 at 2:59 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> I added the \"Unify ref-filter formats with other pretty formats\" to\n> continue Hariom Verma's work during GSoC 2020. I would be happy to\n> co-mentor it if someone is interested to co-mentor it with me.\n\nSince I worked on this for quite some time. I maybe am able to provide\nsome insights. If it's not too late, I would like to co-mentor it with\nyou.\n\nThanks,\nHariom\n"},{"id":"448604","messageId":"CAP8UFD0cNLUSbiABnj3UTrAk36DTePNctNWn8U3wrXMGjA6HFg@mail.gmail.com","threadId":"57317","inReplyTo":"CA+CkUQ9VTs7n9B+ApH1BYC=Uq4yvrZm0fsG0RJB8PVg_BBSCfw@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-02-16T15:40:35Z","receivedAt":"2022-02-16T15:40:53Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Wed, Feb 16, 2022 at 12:18 AM Hariom verma <hariom18599@gmail.com> wrote:\n>\n> Hi,\n>\n> On Mon, Feb 14, 2022 at 2:59 PM Christian Couder\n> <christian.couder@gmail.com> wrote:\n> >\n> > I added the \"Unify ref-filter formats with other pretty formats\" to\n> > continue Hariom Verma's work during GSoC 2020. I would be happy to\n> > co-mentor it if someone is interested to co-mentor it with me.\n>\n> Since I worked on this for quite some time. I maybe am able to provide\n> some insights. If it's not too late, I would like to co-mentor it with\n> you.\n\nGreat! I am happy to co-mentor it with you!\n\nKaartic, I hope it's ok for you.\n\nThanks both,\nChristian.\n"},{"id":"448605","messageId":"CAP8UFD3prsevU_8zCXQu_BpZH+NHm+HD04RiBvOXkZkDoi+yjg@mail.gmail.com","threadId":"57317","inReplyTo":"65abccbe-eaae-5d68-c738-b7f9a3844bbc@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-02-16T15:55:30Z","receivedAt":"2022-02-16T15:55:45Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Feb 15, 2022 at 9:32 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> On 13/02/22 3:03 pm, Christian Couder wrote:\n> > On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam\n> > <kaartic.sivaraam@gmail.com> wrote:\n> >\n> >> On a related note, the organization registrations are now open for this year.\n> >> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is\n> >> planning on applying for Git. In case no one else beats me to it, I plan on\n> >> applying for Git around February 15 17:00 UTC.\n> >\n> > I was thinking about applying for Git, but I am glad that you plan to\n> > do it. I will try to add some project ideas to SoC-2022-Ideas.md\n> > before February 15.\n>\n> Thanks for adding it! I've applied for Git in GSoC 2022. The application\n> information could be found here:\n>\n>    https://git.github.io/SoC-2022-Org-Application/\n\nThanks for applying!\n\n> Let me know in case anything needs to be tweaked. I mentioned that we have\n> 5 mentors available counting Stolee, Victoria, Christian, Taylor and myself.\n> Also, I've invited Christian as an Org Admin. In case anyone else would like\n> to volunteer to be an Org Admin, do let me know.\n\nThanks, I accepted the invite!\n\nNot sure we can invite possible mentors yet.\n\n> On a lighter note, the application structure was a bit different than\n> previous years due to the new website. They say that it supports persisting\n> the organization information which should mean less work while applying for\n> GSoC in upcoming years.\n\nNice!\n"},{"id":"448706","messageId":"CA+CkUQ-qweJXpR-mAApMd2-w13uiNMZM4_+=NufYaTsOUjGUqQ@mail.gmail.com","threadId":"57317","inReplyTo":"CAP8UFD0cNLUSbiABnj3UTrAk36DTePNctNWn8U3wrXMGjA6HFg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Hariom verma","fromEmail":"hariom18599@gmail.com","sentAt":"2022-02-17T15:07:45Z","receivedAt":"2022-02-17T15:08:04Z","isPatch":false,"sender":{"key":"hariom18599@gmail.com","avatar":"https://avatars.githubusercontent.com/u/37576387?v=4"},"body":"On Wed, Feb 16, 2022 at 9:10 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> > > I added the \"Unify ref-filter formats with other pretty formats\" to\n> > > continue Hariom Verma's work during GSoC 2020. I would be happy to\n> > > co-mentor it if someone is interested to co-mentor it with me.\n> >\n> > Since I worked on this for quite some time. I maybe am able to provide\n> > some insights. If it's not too late, I would like to co-mentor it with\n> > you.\n>\n> Great! I am happy to co-mentor it with you!\n>\n\nThanks.\n"},{"id":"448719","messageId":"0a29bbcf-5c36-3884-96c6-60f9b930ce5f@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD0cNLUSbiABnj3UTrAk36DTePNctNWn8U3wrXMGjA6HFg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-17T17:18:29Z","receivedAt":"2022-02-17T17:18:41Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 16/02/22 9:10 pm, Christian Couder wrote:\n> Hi,\n> \n> On Wed, Feb 16, 2022 at 12:18 AM Hariom verma <hariom18599@gmail.com> wrote:\n>>\n>> Hi,\n>>\n>> On Mon, Feb 14, 2022 at 2:59 PM Christian Couder\n>> <christian.couder@gmail.com> wrote:\n>>>\n>>> I added the \"Unify ref-filter formats with other pretty formats\" to\n>>> continue Hariom Verma's work during GSoC 2020. I would be happy to\n>>> co-mentor it if someone is interested to co-mentor it with me.\n>>\n>> Since I worked on this for quite some time. I maybe am able to provide\n>> some insights. If it's not too late, I would like to co-mentor it with\n>> you.\n> \n> Great! I am happy to co-mentor it with you!\n> \n\nYeah. That's great! Hariom, would you mind opening a PR to mention yourself\nas a mentor in SoC-2022-Ideas.md [1] ?\n\n> Kaartic, I hope it's ok for you.\n>\n\nNow worries at all. I'm actually glad Hariom volunteered to mentor as he's\nmore appropriate a co-mentor for the project :-)\n\n[1]: https://github.com/git/git.github.io/blob/master/SoC-2022-Ideas.md\n\n-- \nSivaraam\n"},{"id":"448720","messageId":"5193ddc5-91d0-7fa2-dea9-32c28d7f0e2f@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD3prsevU_8zCXQu_BpZH+NHm+HD04RiBvOXkZkDoi+yjg@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-17T17:28:20Z","receivedAt":"2022-02-17T17:28:29Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 16/02/22 9:25 pm, Christian Couder wrote:\n> On Tue, Feb 15, 2022 at 9:32 PM Kaartic Sivaraam\n> \n> Thanks, I accepted the invite!\n> \n> Not sure we can invite possible mentors yet.\n> \n\nYeah. Inviting mentors isn't possible yet. It's possible only after the\norg application has been accepted. We'll know the status of our org\napplication by March 7 - 18:00 UTC [1]\n\n[1]: https://developers.google.com/open-source/gsoc/timeline\n\n-- \nSivaraam\n"},{"id":"448754","messageId":"CA+CkUQ8=uMbzhJ2-mqss17PakJBuqjqpxCXetdZmd+Nd6F41UQ@mail.gmail.com","threadId":"57317","inReplyTo":"0a29bbcf-5c36-3884-96c6-60f9b930ce5f@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Hariom verma","fromEmail":"hariom18599@gmail.com","sentAt":"2022-02-18T02:14:17Z","receivedAt":"2022-02-18T02:14:33Z","isPatch":false,"sender":{"key":"hariom18599@gmail.com","avatar":"https://avatars.githubusercontent.com/u/37576387?v=4"},"body":"On Thu, Feb 17, 2022 at 10:48 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> Yeah. That's great! Hariom, would you mind opening a PR to mention yourself\n> as a mentor in SoC-2022-Ideas.md [1] ?\n>\n\nYeah, sure. Done.\n(https://github.com/git/git.github.io/pull/559)\n\nThanks\nHariom\n"},{"id":"449680","messageId":"742c7455-8f74-ac03-350a-7c3851f2b792@gmail.com","threadId":"57317","inReplyTo":"YfGpjm8mCkWIPM6V@nand.local","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-26T20:29:52Z","receivedAt":"2022-02-26T20:30:12Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Taylor,\n\nOn 27/01/22 1:35 am, Taylor Blau wrote:\n> \n> On Wed, Jan 26, 2022 at 11:59:16PM +0530, Kaartic Sivaraam wrote:\n>> First, are we interested in participating in the 2022 round of\n>> GSoC?\n> \n> I think it would be great to participate this year, provided that we can\n> come up with some interesting projects and mentors to help out.\n> \n>>      Taylor showed interest in a bitmap-related project during\n>>      the Outreachy application period [4]. Taylor, are you still\n>>      interested in mentoring a bitmap-related project? Would it\n>>      be possible for you to do so for the upcoming GSoC?\n> \n> I'm available and interested in mentoring. I don't think I found many\n> interested folks via Outreachy who wanted to work on bitmaps, but I\n> think it's worth trying again via GSoC. I can rejigger the proposed\n> projects there a bit, too.\n> \n\nThanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that\nyou're the only one mentioned as mentor for the idea there. It's usually\ngood to have at least 2 mentors per project. Is anyone else interested\nin co-mentoring with Taylor for the idea?\n\n[1]: https://git.github.io/SoC-2022-Ideas/\n\n-- \nSivaraam\n"},{"id":"449743","messageId":"CAP8UFD1bEjg20Twn0pjVqxmgCU7Nhzkg16O2t6gacSsqCYfXng@mail.gmail.com","threadId":"57317","inReplyTo":"742c7455-8f74-ac03-350a-7c3851f2b792@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-02-28T11:03:15Z","receivedAt":"2022-02-28T11:03:38Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n\n> Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that\n> you're the only one mentioned as mentor for the idea there. It's usually\n> good to have at least 2 mentors per project. Is anyone else interested\n> in co-mentoring with Taylor for the idea?\n\nIf no one else wants to co-mentor with Taylor, I am happy with it.\n"},{"id":"449792","messageId":"CA+ARAtrwt-Ov=b13s2g8AGuATS8fNfk_ohNQPscSjAs3n0y=0w@mail.gmail.com","threadId":"57317","inReplyTo":"CAP8UFD1bEjg20Twn0pjVqxmgCU7Nhzkg16O2t6gacSsqCYfXng@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-02-28T18:02:16Z","receivedAt":"2022-02-28T18:23:38Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi all,\n\nOn Mon, Feb 28, 2022 at 4:33 PM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n>\n> > Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that\n> > you're the only one mentioned as mentor for the idea there. It's usually\n> > good to have at least 2 mentors per project. Is anyone else interested\n> > in co-mentoring with Taylor for the idea?\n>\n> If no one else wants to co-mentor with Taylor, I am happy with it.\n\nIf it's fine, I would be willing to co-mentor with Taylor. In case\nthere are other\npotential mentors who are willing to volunteer, do chime in :-)\n\n-- \nSivaraam\n"},{"id":"449923","messageId":"CAP8UFD1WMn=-6Ais10xpJR70BR28UzEtbTeGSx3uNfkNt2kJ3Q@mail.gmail.com","threadId":"57317","inReplyTo":"CA+ARAtrwt-Ov=b13s2g8AGuATS8fNfk_ohNQPscSjAs3n0y=0w@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-03-01T13:51:56Z","receivedAt":"2022-03-01T13:52:18Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Feb 28, 2022 at 7:02 PM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n\n> On Mon, Feb 28, 2022 at 4:33 PM Christian Couder\n> <christian.couder@gmail.com> wrote:\n> > On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam\n> > <kaartic.sivaraam@gmail.com> wrote:\n> >\n> > > Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that\n> > > you're the only one mentioned as mentor for the idea there. It's usually\n> > > good to have at least 2 mentors per project. Is anyone else interested\n> > > in co-mentoring with Taylor for the idea?\n> >\n> > If no one else wants to co-mentor with Taylor, I am happy with it.\n>\n> If it's fine, I would be willing to co-mentor with Taylor. In case\n> there are other\n> potential mentors who are willing to volunteer, do chime in :-)\n\nGreat! As I already co-mentor another project, I will let you\nco-mentor this one with Taylor.\n\nThanks!\n"},{"id":"450430","messageId":"3849de1a-ef47-1615-128b-b0053cb2f4bf@gmail.com","threadId":"57317","inReplyTo":"CAP8UFD1WMn=-6Ais10xpJR70BR28UzEtbTeGSx3uNfkNt2kJ3Q@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-03-04T18:34:40Z","receivedAt":"2022-03-04T18:36:57Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 01/03/22 7:21 pm, Christian Couder wrote:\n> On Mon, Feb 28, 2022 at 7:02 PM Kaartic Sivaraam\n> <kaartic.sivaraam@gmail.com> wrote:\n> \n>> On Mon, Feb 28, 2022 at 4:33 PM Christian Couder\n>> <christian.couder@gmail.com> wrote:\n>>> On Sat, Feb 26, 2022 at 9:30 PM Kaartic Sivaraam\n>>> <kaartic.sivaraam@gmail.com> wrote:\n>>>\n>>>> Thanks for adding the ideas to the SoC-2022-Ideas[1] list! I noticed that\n>>>> you're the only one mentioned as mentor for the idea there. It's usually\n>>>> good to have at least 2 mentors per project. Is anyone else interested\n>>>> in co-mentoring with Taylor for the idea?\n>>>\n>>> If no one else wants to co-mentor with Taylor, I am happy with it.\n>>\n>> If it's fine, I would be willing to co-mentor with Taylor. In case\n>> there are other\n>> potential mentors who are willing to volunteer, do chime in :-)\n> \n> Great! As I already co-mentor another project, I will let you\n> co-mentor this one with Taylor.\n> \n\nNice. Thanks for the opportunity! I've mentioned myself as a\nco-mentor for the bitmap improvements project [1].\n\nTaylor, do let me know in case you have any concerns about this.\n\n[1]: https://git.github.io/SoC-2022-Ideas/\n\n-- \nSivaraam\n"},{"id":"450635","messageId":"CA+ARAtquQOtcDtc0nCWkxyP2enb_QbxyoK9b3HWf-2JzbaKbkQ@mail.gmail.com","threadId":"57317","inReplyTo":"439ebfba-d493-2cff-434a-b1073e755688@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-03-07T19:38:46Z","receivedAt":"2022-03-07T19:39:01Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi all,\n\nI'm glad to share the news that Git has been accepted as a mentoring\norganization [1] for GSoC!\n\nSince it is possible to invite mentors now, I've invited the mentors who\nhave suggested ideas[2] so far. I've used the e-mail mentioned in the\nideas page to send the invite.\n\nSome upcoming GSoC deadlines for reference:\n\n1. April 4 - 18:00 UTC - GSoC contributor application period begins\n2. April 19 - 18:00 UTC - GSoC contributor application deadline\n3. May 12 - 18:00 UTC - GSoC contributor slot requests due from Org Admins\n4. May 20 - 18:00 UTC - Accepted GSoC contributor projects announced\n\nFull timeline available in [3].\n\nThat said, there's still time to propose new ideas. In case anyone has\nideas that are worth pursuing for GSoC contributors, do feel free to\nshare them.\n\n[1]: https://summerofcode.withgoogle.com/programs/2022/organizations/git\n[2]: https://git.github.io/SoC-2022-Ideas/\n[3]: https://developers.google.com/open-source/gsoc/timeline\n\n-- \nSivaraam\n"},{"id":"450638","messageId":"e1b59df0-2ec2-2854-7c53-b1a57bd157c3@github.com","threadId":"57317","inReplyTo":"CA+ARAtquQOtcDtc0nCWkxyP2enb_QbxyoK9b3HWf-2JzbaKbkQ@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Derrick Stolee","fromEmail":"derrickstolee@github.com","sentAt":"2022-03-07T19:50:53Z","receivedAt":"2022-03-07T19:51:00Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 3/7/2022 2:38 PM, Kaartic Sivaraam wrote:\n> Hi all,\n> \n> I'm glad to share the news that Git has been accepted as a mentoring\n> organization [1] for GSoC!\n\nExcellent news! Thanks for all your hard work on the application.\n \n> Since it is possible to invite mentors now, I've invited the mentors who\n> have suggested ideas[2] so far. I've used the e-mail mentioned in the\n> ideas page to send the invite.\n\nI've submitted the form for mine. Thanks!\n\n-Stolee\n"},{"id":"450666","messageId":"CA+CkUQ93Z7e0iTFMOpiY+a-UyrfQhmvdQXQ-SoDBVUu+GsKshA@mail.gmail.com","threadId":"57317","inReplyTo":"CA+ARAtquQOtcDtc0nCWkxyP2enb_QbxyoK9b3HWf-2JzbaKbkQ@mail.gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Hariom verma","fromEmail":"hariom18599@gmail.com","sentAt":"2022-03-07T22:25:15Z","receivedAt":"2022-03-07T22:25:32Z","isPatch":false,"sender":{"key":"hariom18599@gmail.com","avatar":"https://avatars.githubusercontent.com/u/37576387?v=4"},"body":"On Tue, Mar 8, 2022 at 1:08 AM Kaartic Sivaraam\n<kaartic.sivaraam@gmail.com> wrote:\n>\n> I'm glad to share the news that Git has been accepted as a mentoring\n> organization [1] for GSoC!\n>\n> Since it is possible to invite mentors now, I've invited the mentors who\n> have suggested ideas[2] so far. I've used the e-mail mentioned in the\n> ideas page to send the invite.\n\nGreat. I have accepted the invitation.\n\nThanks,\nHariom\n"},{"id":"450831","messageId":"nycvar.QRO.7.76.6.2203091249060.357@tvgsbejvaqbjf.bet","threadId":"57317","inReplyTo":"22e484c3-f313-5335-5f34-5df019b7ee98@gmail.com","subject":"Re: Git in GSoC 2022?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-03-09T11:49:41Z","receivedAt":"2022-03-09T11:49:54Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Kaartic,\n\nOn Sun, 30 Jan 2022, Kaartic Sivaraam wrote:\n\n> On 28/01/22 4:15 pm, Johannes Schindelin wrote:\n> >\n> > A project that I would personally find a lot of fun, with a great impact,\n> > and never really talked about on this list, would be to offer a good\n> > replacement for the `git daemon`: its purpose is to make it easy to stand\n> > up an ad-hoc server, to allow developers to clone/fetch (and even push, if\n> > that is enabled) via the network, unauthenticated. Now, the git://\n> > protocol has served us well in the beginning, but it is increasingly\n> > obvious that we should use https:// wherever possible. Wouldn't it be fun\n> > to have a `git daemon` that talks https:// by default, maybe even\n> > optionally offering a real web UI via gitweb? This is not as huge of a\n> > project as it sounds, Jeff Hostetler already did a ton of work to that end\n> > over in the Microsoft fork of Git: the `test-gvfs-protocol` helper is used\n> > in the regression tests to offer Git repositories via http:// and the\n> > biggest task to convert this to an HTTP-speaking `git daemon` would be to\n> > rip out the GVFS parts. After that, HTTPS support could be added.\n> >\n>\n> Sounds interesting. Would you mind drafting this into a project proposal\n> for GSoC. Then we could add it to the list of ideas document [1].\n>\n> Also, would you be willing to mentor a student in case they pick this\n> project? Or would you rather leave it to others?\n\nI would _love_ to mentor a student, but my time constraints do not allow\nme to do that.\n\nSorry,\nDscho\n\n>\n> [1]: https://github.com/git/git.github.io/pull/540\n>\n> --\n> Sivaraam\n>\n>\n"},{"id":"450923","messageId":"CA+ARAtqjFhR2W8OjzGgPmtin4g_9M-8jjyJ0XsS1_401uxBrLg@mail.gmail.com","threadId":"57317","inReplyTo":"nycvar.QRO.7.76.6.2203091249060.357@tvgsbejvaqbjf.bet","subject":"Re: Git in GSoC 2022?","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2022-03-09T19:57:23Z","receivedAt":"2022-03-09T19:57:38Z","isPatch":false,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"Hi Dscho,\n\nOn Wed, Mar 9, 2022 at 5:19 PM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n>\n> Hi Kaartic,\n>\n> On Sun, 30 Jan 2022, Kaartic Sivaraam wrote:\n>\n> > On 28/01/22 4:15 pm, Johannes Schindelin wrote:\n> > >\n> > > A project that I would personally find a lot of fun, with a great impact,\n> > > and never really talked about on this list, would be to offer a good\n> > > replacement for the `git daemon`: its purpose is to make it easy to stand\n> > > up an ad-hoc server, to allow developers to clone/fetch (and even push, if\n> > > that is enabled) via the network, unauthenticated. Now, the git://\n> > > protocol has served us well in the beginning, but it is increasingly\n> > > obvious that we should use https:// wherever possible. Wouldn't it be fun\n> > > to have a `git daemon` that talks https:// by default, maybe even\n> > > optionally offering a real web UI via gitweb? This is not as huge of a\n> > > project as it sounds, Jeff Hostetler already did a ton of work to that end\n> > > over in the Microsoft fork of Git: the `test-gvfs-protocol` helper is used\n> > > in the regression tests to offer Git repositories via http:// and the\n> > > biggest task to convert this to an HTTP-speaking `git daemon` would be to\n> > > rip out the GVFS parts. After that, HTTPS support could be added.\n> > >\n> >\n> > Sounds interesting. Would you mind drafting this into a project proposal\n> > for GSoC. Then we could add it to the list of ideas document [1].\n> >\n> > Also, would you be willing to mentor a student in case they pick this\n> > project? Or would you rather leave it to others?\n>\n> I would _love_ to mentor a student, but my time constraints do not allow\n> me to do that.\n>\n\nThat's understandable. Thanks for sharing the project idea!\n\nIn case anyone else is interested to volunteer as a mentor for this project,\ndo chime in. We could then add this one to the ideas list.\n\n--\nSivaraam\n"}]}