From: Steven Rostedt <rostedt@goodmis.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
ksummit@lists.linux.dev, outreachy@lists.linux.dev,
kernel-janitors@vger.kernel.org
Subject: Re: KTODO automated TODO lists
Date: Mon, 11 Dec 2023 13:47:00 -0500 [thread overview]
Message-ID: <20231211134700.2c90f106@gandalf.local.home> (raw)
In-Reply-To: <9e0dc452-c4fe-4511-83fe-a1e356bd5438@embeddedor.com>
On Mon, 23 Oct 2023 17:38:15 -0600
"Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
> On 10/18/23 22:11, Dan Carpenter wrote:
> > Yesterday someone on my lists just sent an email looking for kernel
> > tasks. This was a university student in a kernel programming class.
> > We also have kernel-janitors and outreachy and those people are always
> > asking for small tasks.
>
> We have tons of issues waiting to be audited and fixed here:
>
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You will never run out of fun. :) People just need to sign up.
>
> That's really a great way to learn and gain experience across the whole
> kernel tree.
>
The difference between this and the KTODO is that the above is bugs that a
bot has discovered, right?
Although I agree that fixing bugs is a great way to learn the kernel, in
some cases people want to create a feature. At least that's a bit more
rewarding.
Currently, while working on adding a feature to the tracing ring buffer,
I've come across several bugs (that I fixed), but also a list of "nice to
haves".
That is, small feature enhancements that make the system better, that I
simply do not have the time to implement. This is where I think KTODO is
useful. If someone wants to add these enhancements, I'd be happy to help
them out (sparingly).
-- Steve
prev parent reply other threads:[~2023-12-11 18:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 4:11 KTODO automated TODO lists Dan Carpenter
2023-10-19 12:50 ` Linus Walleij
2023-10-19 13:21 ` Geert Uytterhoeven
2023-10-19 15:43 ` Liam R. Howlett
2023-10-19 16:30 ` Bird, Tim
2023-10-19 17:34 ` Dan Carpenter
2023-10-19 17:37 ` Bird, Tim
2023-10-19 17:47 ` Konstantin Ryabitsev
2023-10-23 18:49 ` Andrew Morton
2023-10-23 18:55 ` Linus Torvalds
2023-10-23 19:00 ` Geert Uytterhoeven
2023-10-23 19:17 ` Linus Torvalds
2023-10-23 19:29 ` Steven Rostedt
2023-10-23 21:31 ` Paul E. McKenney
2023-10-23 21:44 ` Tony Luck
2023-10-23 22:25 ` Paul E. McKenney
2023-10-23 19:41 ` Konstantin Ryabitsev
2023-10-24 4:58 ` Andrew Morton
2023-10-24 15:28 ` Konstantin Ryabitsev
2023-10-26 21:58 ` Miguel Ojeda
2023-10-23 21:45 ` NeilBrown
2023-10-24 7:19 ` Geert Uytterhoeven
2023-10-24 7:25 ` Laurent Pinchart
2023-10-24 8:42 ` Jani Nikula
2023-10-24 8:52 ` Laurent Pinchart
2023-10-24 12:36 ` Steven Rostedt
2023-10-24 13:12 ` Laurent Pinchart
2023-10-24 15:53 ` Krzysztof Kozlowski
2023-10-24 21:29 ` NeilBrown
2023-10-24 22:05 ` Steven Rostedt
2023-10-25 3:47 ` Paul E. McKenney
2023-10-25 23:45 ` Steven Rostedt
2023-10-25 6:55 ` Geert Uytterhoeven
2023-10-25 21:14 ` NeilBrown
2023-10-25 22:00 ` Randy Dunlap
2023-10-26 4:29 ` Dan Carpenter
2023-10-26 6:56 ` Geert Uytterhoeven
2023-10-25 7:01 ` Krzysztof Kozlowski
2023-10-25 11:45 ` James Bottomley
2023-10-25 16:40 ` Jani Nikula
2023-10-25 18:07 ` James Bottomley
2023-10-25 18:10 ` Steven Rostedt
2023-10-25 19:43 ` Linus Torvalds
2023-10-25 21:19 ` NeilBrown
2023-10-25 21:17 ` NeilBrown
2023-10-25 18:55 ` Alexey Dobriyan
2023-10-25 19:27 ` Steven Rostedt
2023-10-25 20:03 ` Alexandre Belloni
2023-10-25 21:38 ` NeilBrown
2023-10-23 23:38 ` Gustavo A. R. Silva
2023-10-24 0:07 ` Gustavo A. R. Silva
2023-10-24 2:16 ` Joe Perches
2023-12-11 18:47 ` Steven Rostedt [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=20231211134700.2c90f106@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dan.carpenter@linaro.org \
--cc=gustavo@embeddedor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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).