About promiscuity, against security

Few weeks ago I read that someone had found an exploit to became root on local Linux systems because of a Kernel issue.
The bug was fixed quickly but maybe not enough to prevent someone, evil or not (me included), to exploit it in an exposed machine.

We can find that kind of matters on every systems, even they are free or not, but the question is: ¿is a good thing to release so quick or to be so open in every step of development that everyone could know what is going bad (or well) in every moment?

From The Cathedral and the Bazaar you can read that "Linus Torvalds's style of development is to release early and often, delegate everything you can, be open to the point of promiscuity". But maybe that "promiscuity" may be a lack of security. Like in sex, more people can mean more fun, but not more security.

When you are developing software in an office, for a company, you use private chanels to comunicate with your mates. But when you are developing for all people who want to use your software, and you are not doing this alone, you have to use global and public channels.

That's, for me, one of the weak points of global development of free software. Maybe if developers coordination change and new versions are released only when they are really stable, this weak point would be "fixed" from the developing process.

Safe sex, safe share your code.

First free post

Hi all!

This is my very first post on my own new blog. Things about libre software and misc stuff will be posted and discussed, so, feel free to discuss whatever post. Blog is about free software and free thinking.

Here some links to topics that will be common on the blog (spanish versions on the right):

- GNU on the Wikipedia es
- Free Software definition es
- Free Software Movement on the Wikipedia es

Wellcome all and enjoy!! (me included)

...unless you are on the moon