From: JAYATHEERTH K <jayatheerthkulkarni2005@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [GSOC] Machine-Readable Repository Information Query Tool
Date: Mon, 24 Mar 2025 18:47:57 +0530 [thread overview]
Message-ID: <CA+rGoLf81GjsFfxVfwAXeTJ278wcH2nj8HgrHQJcDhZwyK9m-Q@mail.gmail.com> (raw)
In-Reply-To: <Z-FIkHiyGc0jnHX1@pks.im>
Hey Patrick,
On Mon, Mar 24, 2025 at 5:27 PM Patrick Steinhardt <ps@pks.im> wrote:
>
> 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.
> 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.
> Thanks!
>
> Patrick
>
> [1]: https://git.github.io/General-Application-Information/
Thanks for the guidance! helps a lot
Jay
prev parent reply other threads:[~2025-03-24 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 14:50 [GSOC] Machine-Readable Repository Information Query Tool JAYATHEERTH K
2025-03-24 11:57 ` Patrick Steinhardt
2025-03-24 13:17 ` JAYATHEERTH K [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+rGoLf81GjsFfxVfwAXeTJ278wcH2nj8HgrHQJcDhZwyK9m-Q@mail.gmail.com \
--to=jayatheerthkulkarni2005@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).