Home opinion-and-analysis Open Sauce Kernel report: it's all good

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Linux developers and management people have little in common. Yet the latter would find plenty of which to approve in the latest kernel report - it is a dream come true as far as work practices go.

The project, for one, appears to be highly flexible. When there was a breach of the servers back in August last year, the work did not suffer to the extent that things became paralysed. The time for release jumped to 95 days but that was just 15 days more than the average of 80. And the next release, 3.2, made it out of the hatches in 72 days.

The rate of development is staggering. For a huge, complex project of this nature to keep releasing so often, mostly high-quality releases, and display such a high work-rate consistently is simply amazing.

What is even more amazing is that despite all the flame-fests on mailing lists and the loneliness factor - you cannot do kernel development while socialising - the number of kernel developers continues to increase. And not merely from companies - where people are recruited to work on the kernel because of the company's interest - but from outside.

This, remember, is happening at a time when many other free and open source software projects are struggling to find people who can be added to the developer ranks.

To date, from the 2.6.11 release, a total of 855 companies have made contributions. For the latest release, 226 were involved. This means that they hire hackers to work on aspects of the kernel which suit their own interests.

But whether people are from companies, fall into the unknown category - where no company affiliation can be determined - or are working on their own, they are all managed well by one person who has created a hierarchy based on meritocracy that results in amazing output. That, in itself, is another very remarkable result. The word dysfunctional is never heard when discussing the kernel project.

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect