threads / discuss / 63181

[GSOC] Machine-Readable Repository Information Query Tool

Subject: [GSOC] Machine-Readable Repository Information Query Tool

## tl;dr

3 messages between Mar 23, 2025 and Mar 24, 2025.

replies: 2people: 2as markdown or json

JAYATHEERTH K· Mar 23, 2025, 14:50 UTC · lore

With GSoC proposal submissions starting tomorrow, I’d like to understand more about the procedure.

As part of my microproject, I worked on modifying tutorials where we create new Git commands[1]. I also have strong experience with C and Shell Scripting and would like to contribute by developing a dedicated command to fulfill what git-rev-parse was originally intended for.

Could you provide more details on how to proceed?
[1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u

Thank you, Jay

Patrick Steinhardt· Mar 24, 2025, 11:57 UTC · re: JAYATHEERTH K · lore

Re: [GSOC] Machine-Readable Repository Information Query Tool

Hi Jayatheerth,
On Sun, Mar 23, 2025 at 08:20:18PM +0530, JAYATHEERTH K wrote:
Show 11 quoted lines
> With GSoC proposal submissions starting tomorrow, I’d like to
> understand more about the procedure.
> 
> As part of my microproject, I worked on modifying tutorials where we
> create new Git commands[1]. I also have strong experience with C and
> Shell Scripting and would like to contribute by developing a dedicated
> command to fulfill what git-rev-parse was originally intended for.
> 
> Could you provide more details on how to proceed?
> 
> [1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u

all requirements and steps should be listed in [1]. There are two mandatory steps:

    - Finishing a microproject. You have already started on a
      microproject, but as far as I can see there is still feedback from
      Junio that hasn't been addressed.
    - Writing your application. This would be the next step once the
      microproject has been accepted.

As spelled out in the document, you can optionally also help out on the mailing list by reviewing other patches. This is not a strict requirement, but getting more involved with the community is a good way to increase your chances of getting accepted. You are of course also free to do another microproject or search for any other areas that you want to propose a patch for.

Thanks!
Patrick
[1]: https://git.github.io/General-Application-Information/
JAYATHEERTH K· Mar 24, 2025, 13:17 UTC · re: Patrick Steinhardt · lore

Re: [GSOC] Machine-Readable Repository Information Query Tool

Hey Patrick,
On Mon, Mar 24, 2025 at 5:27 PM Patrick Steinhardt <ps@pks.im> wrote:
Show 22 quoted lines
>
> Hi Jayatheerth,
>
> On Sun, Mar 23, 2025 at 08:20:18PM +0530, JAYATHEERTH K wrote:
> > With GSoC proposal submissions starting tomorrow, I’d like to
> > understand more about the procedure.
> >
> > As part of my microproject, I worked on modifying tutorials where we
> > create new Git commands[1]. I also have strong experience with C and
> > Shell Scripting and would like to contribute by developing a dedicated
> > command to fulfill what git-rev-parse was originally intended for.
> >
> > Could you provide more details on how to proceed?
> >
> > [1] - https://lore.kernel.org/git/20250321143022.5406-1-jayatheerthkulkarni2005@gmail.com/T/#u
>
> all requirements and steps should be listed in [1]. There are two
> mandatory steps:
>
>     - Finishing a microproject. You have already started on a
>       microproject, but as far as I can see there is still feedback from
>       Junio that hasn't been addressed.

Yes, I have a series of examinations going on making things slow from my end, but I have addressed the feedback and will do if there are any more further down the line.

>
>     - Writing your application. This would be the next step once the
>       microproject has been accepted.
>
Got it.
Show 7 quoted lines
> As spelled out in the document, you can optionally also help out on the
> mailing list by reviewing other patches. This is not a strict
> requirement, but getting more involved with the community is a good way
> to increase your chances of getting accepted. You are of course also
> free to do another microproject or search for any other areas that you
> want to propose a patch for.
>

Once my microproject is finished I would love to help review other patches and work on many other microprojects, As I previously said I would love to remain as a part of Git even after GSOC.

Show 5 quoted lines
> Thanks!
>
> Patrick
>
> [1]: https://git.github.io/General-Application-Information/
Thanks for the guidance! helps a lot
Jay

← back to recent threads