linux-kernel - Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 May 2008 16:15:55 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	ksummit-2008-discuss@...ts.linux-foundation.org
Cc:	Rik van Riel <riel@...hat.com>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

On Wednesday 28 May 2008, Rik van Riel wrote:
> On Wed, 28 May 2008 12:20:12 -0500
>
> James Bottomley <James.Bottomley@...senPartnership.com> wrote:
> > The most obvious solution might be to shut the Janitors project down, or
> > at least more tightly manage its TODO list
>
> I've had some limited success with:
>
> http://kernelnewbies.org/KernelProjects
>
> One problem is that people end up beginning with a project but
> for some reason stop working on it later - with no indication
> as to whether the project ended up being too difficult, or they
> ran out of time, or something else happened...

I think our mistake is the assumption that everyone who wants to contribute to 
the kernel wants to code, or that everyone wants to end up at the top of the 
major feature contributors list.  For lots of people, we're going to be that 
experiment from college they never quite want to admit to later on in life.

Looking at the KernelProjects link, bugzilla is at the buttom and janitors is 
at the top.  I've always thought the janitors project was important, but 
maybe we want to change the emphasis around a bit.

The regressions page on kernelnewbies is out of date, and there are many more 
howtos on coding than on bug hunting.  It doesn't mention linux-next 
anywhere.

I'm not picking on kernelnewbies, it is one of our best resources.  But, going 
back to James' ideas, introducing people to bug hunting is a better way to 
involve them in the community.

Maintainers are easier to interact with when you send good bug reports along 
with a clear way to reproduce it and perhaps a bisection

Getting all of the above is often 95% of the work of fixing it, people are 
most likely to jump into the coding when they've found a bad patch and start 
to wonder if they can fix it themselves.

Along those lines, how about a kernel bug hunting challenge.  The top 
contributor(s) to creating bugzillas that get solved get a new pc, laptop, 
high end graphics card, ssd device...whatever.  We could send the best 
testers hardware that breaks most often...everyone wins.

Other prizes could include tickets to a linux conf of choice (not airline 
tickets, just free entry).

One motivation here is to bring bug reporters from active distro communities 
into testing mainline kernels as well.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/