linux-kernel - Re: Spamming linux-kernel and linux-scsi by out-of-tree patches (LIO)

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] [day] [month] [year] [list]

Date:	Mon, 26 Jan 2009 09:15:24 -0800
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Vladislav Bolkhovitin <vst@...b.net>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: Spamming linux-kernel and linux-scsi by out-of-tree patches
	(LIO)

On Mon, 2009-01-26 at 08:19 -0800, Arjan van de Ven wrote:
> On Mon, 26 Jan 2009 19:08:24 +0300
> Vladislav Bolkhovitin <vst@...b.net> wrote:
> 
> > I wouldn't object if Nicholas des the same and send in linux-scsi
> > and linux-kernel a complete patchset, which we will review and
> > discuss. But he sends *intermediate* patches and this looks for me
> > like a violation of fundamental rules/intention of Linux kernel
> > mailing lists, hence I complain.
> > 
> > So, should I understand your words that you agree if I also start 
> > sending intermediate patches for SCST to linux-scsi/linux-kernel?
> > 
> 
> 
> <looking in as an outsider>
> 
> I am thoroughly surprised by this email exchange.
> From where I sit, there is almost no such thing as posting patches too
> early. Really. Transparency and early review/feedaback is by far
> more important than ignoring a few more patches in an area you
> don't careabout.
> 

For those wanting to know more about "Release Early, Release Often":

http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html

<SNIP>

Linus's open development policy was the very opposite of
cathedral-building. Linux's Internet archives were burgeoning, multiple
distributions were being floated. And all of this was driven by an
unheard-of frequency of core system releases.

Linus was treating his users as co-developers in the most effective
possible way:

        7. Release early. Release often. And listen to your customers.

Linus's innovation wasn't so much in doing quick-turnaround releases
incorporating lots of user feedback (something like this had been
Unix-world tradition for a long time), but in scaling it up to a level
of intensity that matched the complexity of what he was developing. In
those early times (around 1991) it wasn't unknown for him to release a
new kernel more than once a day! Because he cultivated his base of
co-developers and leveraged the Internet for collaboration harder than
anyone else, this worked.

<SNIP>

--nab

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