From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Raxel Gutierrez <raxelgutierrez09@gmail.com>,
mricon@kernel.org, patchwork@lists.ozlabs.org,
Taylor Blau <me@ttaylorr.com>,
Emily Shaffer <emilyshaffer@google.com>,
Git Users <git@vger.kernel.org>
Subject: Re: Pain points in Git's patch flow
Date: Wed, 14 Apr 2021 01:02:58 -0700 [thread overview]
Message-ID: <xmqq7dl5z425.fsf@gitster.g> (raw)
In-Reply-To: <b562e614-add7-575f-3013-1dbc667bc5bf@gmail.com> (Bagas Sanjaya's message of "Wed, 14 Apr 2021 14:22:51 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> There is no lists of "beginner-friendly" issues that can be worked on by
> new contributors. They had to search this ML archive for bug report
> issues and determine themselves which are beginner-friendly.
Yeah, looking for "#leftoverbits" or "low-hanging" on the list
archive is often cited as a way, and it does seem easy enough to
do. You go to https://lore.kernel.org/git/, type "leftoverbits"
or "low-hanging" in the text input and press SEARCH.
But that is only half of the story.
Anybody can throw random ideas and label them "#leftoverbits" or
"low-hanging fruit", but some of these ideas might turn out to be
ill-conceived or outright nonsense. Limiting search to the
utterances by those with known good taste does help, but as a
newbie, you do not know who these people with good taste are.
It might help to have a curated list of starter tasks, but I suspect
that they tend to get depleted rather quickly---by definition the
ones on the list are easy to do and there is nothing to stop an
eager newbie from eating all of them in one sitting X-(.
So, I dunno. We seem to suffer from the same lack of good starter
tasks before each GSoC begins.
next prev parent reply other threads:[~2021-04-14 8:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 6:13 Pain points in Git's patch flow Jonathan Nieder
2021-04-14 7:22 ` Bagas Sanjaya
2021-04-14 8:02 ` Junio C Hamano [this message]
2021-04-14 21:42 ` Junio C Hamano
2021-04-15 8:49 ` Denton Liu
2021-04-15 6:06 ` Junio C Hamano
2021-04-15 15:45 ` Son Luong Ngoc
2021-04-19 2:57 ` Eric Wong
2021-04-19 13:35 ` Theodore Ts'o
2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:21 ` Eric Wong
2021-04-28 7:05 ` Eric Wong
2021-04-15 18:25 ` Atharva Raykar
2021-04-16 19:50 ` Junio C Hamano
2021-04-16 20:25 ` Junio C Hamano
2021-05-02 5:35 ` ZheNing Hu
2021-04-18 8:29 ` Sebastian Schuberth
2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason
2021-04-19 2:58 ` Eric Wong
2021-04-19 5:54 ` Sebastian Schuberth
2021-04-19 6:04 ` Sebastian Schuberth
2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:23 ` Sebastian Schuberth
2021-04-19 22:34 ` Theodore Ts'o
2021-04-20 6:30 ` Sebastian Schuberth
2021-04-20 16:37 ` Theodore Ts'o
2021-04-30 20:45 ` Felipe Contreras
2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:36 ` Eric Wong
2021-04-19 19:49 ` Sebastian Schuberth
2021-04-19 22:00 ` Konstantin Ryabitsev
2021-05-08 2:10 ` dwh
2021-04-19 21:49 ` Konstantin Ryabitsev
2021-04-19 23:03 ` Stephen Smith
2021-05-08 2:08 ` dwh
2021-05-08 4:41 ` Bagas Sanjaya
2021-04-30 20:58 ` Felipe Contreras
2021-04-21 4:46 ` Daniel Axtens
2021-04-26 2:04 ` brian m. carlson
2021-04-26 14:24 ` Theodore Ts'o
2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:59 ` Eric Wong
2021-04-28 22:44 ` brian m. carlson
2021-04-30 20:16 ` Felipe Contreras
2021-04-30 20:35 ` Felipe Contreras
2021-04-30 21:09 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7dl5z425.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=me@ttaylorr.com \
--cc=mricon@kernel.org \
--cc=patchwork@lists.ozlabs.org \
--cc=raxelgutierrez09@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).