{"thread":{"id":"63181","subject":"[GSOC] Machine-Readable Repository Information Query Tool","startedAt":"2025-03-23T14:50:30Z","lastAt":"2025-03-24T13:18:11Z","messageCount":3,"participants":["JAYATHEERTH K","Patrick Steinhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"514876","messageId":"CA+rGoLdvY+JdgdzgE04EJoF9KGUpd39+2S_AgpFyucP38mdFgA@mail.gmail.com","threadId":"63181","inReplyTo":null,"subject":"[GSOC] Machine-Readable Repository Information Query Tool","fromName":"JAYATHEERTH K","fromEmail":"jayatheerthkulkarni2005@gmail.com","sentAt":"2025-03-23T14:50:18Z","receivedAt":"2025-03-23T14:50:30Z","isPatch":false,"sender":{"key":"jayatheerthkulkarni2005@gmail.com","avatar":"https://avatars.githubusercontent.com/u/148841023?v=4"},"body":"With GSoC proposal submissions starting tomorrow, I’d like to\nunderstand more about the procedure.\n\nAs part of my microproject, I worked on modifying tutorials where we\ncreate new Git commands[1]. I also have strong experience with C and\nShell Scripting and would like to contribute by developing a dedicated\ncommand to fulfill what git-rev-parse was originally intended for.\n\nCould you provide more details on how to proceed?\n\n[1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u\n\nThank you,\nJay\n"},{"id":"514915","messageId":"Z-FIkHiyGc0jnHX1@pks.im","threadId":"63181","inReplyTo":"CA+rGoLdvY+JdgdzgE04EJoF9KGUpd39+2S_AgpFyucP38mdFgA@mail.gmail.com","subject":"Re: [GSOC] Machine-Readable Repository Information Query Tool","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-03-24T11:57:04Z","receivedAt":"2025-03-24T11:57:08Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi Jayatheerth,\n\nOn Sun, Mar 23, 2025 at 08:20:18PM +0530, JAYATHEERTH K wrote:\n> With GSoC proposal submissions starting tomorrow, I’d like to\n> understand more about the procedure.\n> \n> As part of my microproject, I worked on modifying tutorials where we\n> create new Git commands[1]. I also have strong experience with C and\n> Shell Scripting and would like to contribute by developing a dedicated\n> command to fulfill what git-rev-parse was originally intended for.\n> \n> Could you provide more details on how to proceed?\n> \n> [1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u\n\nall requirements and steps should be listed in [1]. There are two\nmandatory steps:\n\n    - Finishing a microproject. You have already started on a\n      microproject, but as far as I can see there is still feedback from\n      Junio that hasn't been addressed.\n\n    - Writing your application. This would be the next step once the\n      microproject has been accepted.\n\nAs spelled out in the document, you can optionally also help out on the\nmailing list by reviewing other patches. This is not a strict\nrequirement, but getting more involved with the community is a good way\nto increase your chances of getting accepted. You are of course also\nfree to do another microproject or search for any other areas that you\nwant to propose a patch for.\n\nThanks!\n\nPatrick\n\n[1]: https://git.github.io/General-Application-Information/\n"},{"id":"514929","messageId":"CA+rGoLf81GjsFfxVfwAXeTJ278wcH2nj8HgrHQJcDhZwyK9m-Q@mail.gmail.com","threadId":"63181","inReplyTo":"Z-FIkHiyGc0jnHX1@pks.im","subject":"Re: [GSOC] Machine-Readable Repository Information Query Tool","fromName":"JAYATHEERTH K","fromEmail":"jayatheerthkulkarni2005@gmail.com","sentAt":"2025-03-24T13:17:57Z","receivedAt":"2025-03-24T13:18:11Z","isPatch":false,"sender":{"key":"jayatheerthkulkarni2005@gmail.com","avatar":"https://avatars.githubusercontent.com/u/148841023?v=4"},"body":"Hey Patrick,\n\nOn Mon, Mar 24, 2025 at 5:27 PM Patrick Steinhardt <ps@pks.im> wrote:\n>\n> Hi Jayatheerth,\n>\n> On Sun, Mar 23, 2025 at 08:20:18PM +0530, JAYATHEERTH K wrote:\n> > With GSoC proposal submissions starting tomorrow, I’d like to\n> > understand more about the procedure.\n> >\n> > As part of my microproject, I worked on modifying tutorials where we\n> > create new Git commands[1]. I also have strong experience with C and\n> > Shell Scripting and would like to contribute by developing a dedicated\n> > command to fulfill what git-rev-parse was originally intended for.\n> >\n> > Could you provide more details on how to proceed?\n> >\n> > [1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u\n>\n> all requirements and steps should be listed in [1]. There are two\n> mandatory steps:\n>\n>     - Finishing a microproject. You have already started on a\n>       microproject, but as far as I can see there is still feedback from\n>       Junio that hasn't been addressed.\n\nYes, I have a series of examinations going on making things slow from\nmy end, but I have addressed the feedback and will do if there are any\nmore further down the line.\n>\n>     - Writing your application. This would be the next step once the\n>       microproject has been accepted.\n>\n\nGot it.\n\n> As spelled out in the document, you can optionally also help out on the\n> mailing list by reviewing other patches. This is not a strict\n> requirement, but getting more involved with the community is a good way\n> to increase your chances of getting accepted. You are of course also\n> free to do another microproject or search for any other areas that you\n> want to propose a patch for.\n>\n\nOnce my microproject is finished I would love to help review other\npatches and work on many other microprojects,\nAs I previously said I would love to remain as a part of Git even after GSOC.\n\n> Thanks!\n>\n> Patrick\n>\n> [1]: https://git.github.io/General-Application-Information/\n\nThanks for the guidance! helps a lot\n\nJay\n"}]}