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]

Message-ID: <20080529163247.GW22636@parisc-linux.org>
Date:	Thu, 29 May 2008 10:32:47 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	James Bottomley <James.Bottomley@...senpartnership.com>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	penberg@...helsinki.fi, dwmw2@...radead.org,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

On Thu, May 29, 2008 at 05:06:15PM +0200, Jiri Kosina wrote:
> I fully agree, but my impression is that this really is not going to be 
> easy. Fixing bugs definitely is a good way to start kernel coding -- it 
> forces you to understand the internals of the source, get used to the 
> coding style by reading the code, etc. Unfortunately, it's simply not very 
> attractive for newcomers.

"Programming is hard, let's go shopping"?

> For example -- I am leading a seminar at university, oriented at linux 
> kernel internals. I provide the possibility to students either to
> 
> - write some stand-alone interesting kernel project
> - fix a few non-trivial bugs in kernel bugzilla
> - chose any part of a kernel, learn how it works, and present this to 
>   other seminar attendees
> 
> The feedback I often get from students (and these guys are studying 
> computer science) is
> 
> - writing some wholy new interesting kernel project is usually too 
>   complicated (both coming with an interesting idea for a project, and 
>   doing the coding itself)
> - fixing random bugs from kernel bugzilla is boring (spending 10 hours 
>   looking for missing '=' doesn't really attract them)
> 
> So in overwhelming majority of cases, they just chose the presentation.

In general, students are going to choose the easiest option ;-)

Perhaps you could try making the process of finding a kernel bug seem
more exciting?  I doubt that most kernel bugs are a simple as a missing =.
But even if they were, it's about the /process/ you take to get to that
boring patch.

> All I want to say is that I could very well imagine that a lot of 
> newcomers will find "hey, feel free to crawl through bugzilla and fix 
> whatever you are able to fix" very non-attractive.

Of course.  We have to make it sexier than that.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/