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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020805281431y1aac903am442b333a2a13cd15@mail.gmail.com>
Date:	Thu, 29 May 2008 00:31:59 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"James Bottomley" <James.Bottomley@...senpartnership.com>
Cc:	"David Woodhouse" <dwmw2@...radead.org>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

Hi James,

On Thu, May 29, 2008 at 12:01 AM, James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
> Right, but that's why I think we have to change the process.  If we keep
> the Janitors project, then the bar has to be raised so that it becomes
> more participatory and thought oriented (i.e. eliminate from the outset
> anyone who is not going to graduate from mechanical changes to more
> useful ones).

I'm not sure what you expect to happen if we "shut down" the Janitors
project. The important janitorial work doesn't just magically
disappear. For example, we still need people for:

  - Fixing API misuse
  - Converting code from old APIs to new ones
  - Consolidating duplicate code
  - Fixing error handling code
  - Removing unused code
  - De-obfuscating code (e.g. removing bad macro magic, etc.)

And, quite frankly, I don't see what the big fuss is about. I know
we've had way too many "whitespace cleanup" patches in the past six
months or so, but can't we just NAK them politely and be done with it?

                        Pekka
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ