From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: vk <g@vkabc.me>, git@vger.kernel.org
Subject: Re: [GSoC] Microproject help
Date: Mon, 25 Mar 2024 14:23:29 -0700 [thread overview]
Message-ID: <xmqq1q7yhupa.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cRLUra6RObK82nvm1S_goK8q2CXe3A7EeCFA7xqhJCdMg@mail.gmail.com> (Eric Sunshine's message of "Mon, 25 Mar 2024 16:51:55 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Mon, Mar 25, 2024 at 11:40 AM vk <g@vkabc.me> wrote:
>> For the microproject, I have looked into the lists for 2024 and it seems
>> that all the projects have been taken except for `Replace a
>> run_command*() call by direct calls to C functions`. However, it seems
>> that the issue has been solved. The command I ran to search throughout
>> the repo is `git grep 'run_command*('` and the search result returns
>> run_command functions which I assume are essential.
>>
>> If there is any low hanging fruits that you can suggest to me for the
>> microproject, that will be great. I will also be searching throughout
>> the mailing list to see if there are any potential microproject to work
>> on.
>
> Searching the mailing list for "#leftoverbits"[1] can be a good way to
> discover little tasks which may be suitable for a GSoC microproject.
>
> [1]: https://lore.kernel.org/git/?q=%23leftoverbits
True, but with a caveat that they may range from "low hanging fruit"
to "too hard, let's punt". After seeing the anonymous questioners'
question, I did go to that query page (actually I qualified the
query further to list only the ones I gave the mark) and decided not
to suggest it because I found that many recent ones are harder than
"trivial changes suitable for a practice material to go through the
review cycles" X-<.
Thanks.
next prev parent reply other threads:[~2024-03-25 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:10 [GSoC] Microproject help vk
2024-03-25 18:25 ` Karthik Nayak
2024-03-26 11:56 ` vk
2024-03-27 6:36 ` Patrick Steinhardt
2024-03-29 3:57 ` vk
2024-04-02 10:35 ` Patrick Steinhardt
2024-03-29 5:46 ` Junio C Hamano
2024-04-02 9:52 ` Patrick Steinhardt
2024-03-25 20:51 ` Eric Sunshine
2024-03-25 21:23 ` Junio C Hamano [this message]
2024-03-25 21:37 ` Eric Sunshine
2024-03-25 21:58 ` Junio C Hamano
2024-03-26 2:59 ` Eric Sunshine
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=xmqq1q7yhupa.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=g@vkabc.me \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).