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, 26 Jul 2006 20:19:15 -0500
From:	David Masover <ninja@...phack.com>
To:	Russell Cattelan <cattelan@...barn.com>
CC:	Hans Reiser <reiser@...esys.com>, Jeff Garzik <jeff@...zik.org>,
	Theodore Tso <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>,
	ReiserFS List <reiserfs-list@...esys.com>
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org
 regarding reiser4 inclusion

Russell Cattelan wrote:

> Guess it's sort of like adopting a 8 year old child vs a new born, hard
> to tell what happened in first 8 years.

And, by that token, the newborn is sometimes preferable.  It hasn't had 
time to develop severe emotional problems, it's physically harmless, and 
you get to help it form its ideas and beliefs.

On the other hand, the 8 year old is potty trained, you won't have to 
change a single diaper, it's intelligent and makes you question things, 
it understands what you want it to do...

So, it depends what kind of developer you are, what kind of gatekeeper, 
and what kind of project it is.  I still believe in releasing early and 
often, but I can see many reasons not to.  Some are financial -- Namesys 
is trying to operate a business, so any features they open up too early 
could be that much harder to sell as a commercial product.  The 
repacker, for instance.

I'm not arguing for closed source, I'm just saying that once you open, 
there's no going back.  Many times it's a good thing, but sometimes you 
want to wait and see.
-
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