RFC: starting a kernel-testers group for newbies
Quoted 2 lines
We need to send them to a URL that lists all the known bugs and have them pick one, any one, and have them solve it. This would be the best way to learn part of the kernel.
what about adding some link to
on www.kernel.org or doing that via redirect from "http://bugs.kernel.org" ?
sorting results of bugzilla search could need some enhancement, btw. for example, it seems i cannot sort by ID top/down or sorting by date.....
its not obvious enough, what bugs exist - its all hidden in bugzilla and in lkml (and tons of other bugtrackers, forums, mailinglists....). furthermore, it`s also not obvious, that everyone is invited to work together with the kernel devs to solve the bugs.
List: linux-kernel Subject: Re: RFC: starting a kernel-testers group for newbies From: Steven Rostedt <rostedt () goodmis ! org> Date: 2008-05-01 16:38:23 Message-ID: Pine.LNX.4.58.0805011217200.11101 () gandalf ! stny ! rr ! com
[Download message RAW]
Quoted 5 lines · Andrew Morton
Arjan's fourth fallacy: "We don't make (effective) prioritization decisions." lol. This implies that someone somewhere once sat down and wondered which bug he should most effectively work on. Well, we don't do that. We ignore _all_ the bugs in favour of busily writing new ones.
And actually, core kernel developers are best for writing new bugs.
Really, the way I started out learning how the kernel ticks was to go and try to solve some bugs that I was seeing (this was years ago). I get people asking that they want to learn to be a kernel developer and they ask what new feature should they work on? Well, honestly, the last thing a newbie kernel developer should be doing is writing new bugs. We need to send them to a URL that lists all the known bugs and have them pick one, any one, and have them solve it. This would be the best way to learn part of the kernel.
I even find that I understand my own code better when I'm in the debugging phase.
People here mention differnt places to look at code, and besides the kerneloops.org I really don't even know where to look for bugs, because I haven't seen a URL to point me to.
The next time someone asks me how to get started in kernel programming, I would love to tell them to go and look here, and solve the bugs. I'm guessing that I should just point them to:
http://janitor.kernelnewbies.org/
and tell them to focus on real bugs (not just comments and such) to get fixed if they really want to learn the kernel.
-- Steve
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
[ Please don't strip the CC list. It may be a month before those on the CC
actually read your email ]
Just replying with the missing CC.
-- Steve
Quoted 15 lines · On Thu, 1 May 2008 [email protected] wrote:
Quoted 2 lines
We need to send them to a URL that lists all the known bugs and have them pick one, any one, and have them solve it. This would be the best way to learn part of the kernel.
what about adding some link to
on www.kernel.org or doing that via redirect from "http://bugs.kernel.org" ?
sorting results of bugzilla search could need some enhancement, btw. for example, it seems i cannot sort by ID top/down or sorting by date.....
it
s not obvious enough, what bugs exist - its all hidden in bugzilla and in lkml (and tons of other bugtrackers, forums, mailinglists....). furthermore, it`s also not obvious, that everyone is invited to work together with the kernel devs to solve the bugs.