Process Improvements in the Kernel Development

Kalki writes "In an e-mail to the Linux kernel mailing list, sent Saturday, Torvalds proposed that kernel developers begin certifying that the code that they contribute is entitled to be included in the Linux kernel as well as a technique for "signing off on patches" that would better track which developers had handled source code contributions. check this Infoworld story on it."

Comments

A good thing.

[Raven42rac]

The more organisation and delegation in Linux, the better. With the gains being made using Bitkeeper and this, I feel that Linux will make leaps and bounds in the next year. The things I hope for are better hardware detection and working device drivers for more devices (especially multifunction printers). I think Xandros is getting really close to the way things can be. But then again, I run a Debian CLI install on a Pentium II 350. I guess what I meant to say was, for Linux to gain mass market acceptance, it needs to do everything Windows/OS X does, but better, cheaper and faster.

tracking

[colinleroy]

"signing off on patches" that would better track which developers had handled source code contributions.

Linus Torvalds' problem is the fact that, as it is currently easy to find out who commited the patch, and often who provided it (which often appears in Bitkeeper's changelog), the whole submission process can be a blackbox - if I send a patch to alsa subsystem's maintainer, he'll probably apply it to alsa's CVS, maybe someone else will modify this patch, and when included in linux' main tree, only the merge information would appear.

Professional Approach coming to Linux ?

[kbsingh]

Sounds pretty good. I think Linux needs a basic system of this sort in place as-soon-as-practical. It will bring together a lot of accountability of / for code in the Kernel itself. Plus, it should counter any issue like the SCO created one, in the future.

Another interesting point here seems to be that with this management overhead and the admin work that issue such as this create, how much of time is Linus actually spending with them ? while he might be working with the technical side of things ?

Inspite of all the noise, there are just a handfull of people contributing major code into the Kernel ( would 300 be a fair guess ? ) How are all these admin overheads going to effect their performance ? Also is anyone / everyone expected to research the piles and piles of patenets / copyrights before they make such a declaration ?

Good Idea

[Whitecloud]

This sounds like a good way to ensure accountability on who made what changes, and when they did it. Linus says the SCO debacle "have provided a "big impetus" for the changes", this will make sure similar legal action can be shot down immediately.

Considering all the code thats been leaked lately, this is a welcome insurance policy to keep Linux on track as free alternative OS.

Re:Avoid even the appearance..

[BinLadenMyHero]

I wonder if this is in any way related to this.

From FSF:
We have just begun a project here at FSF to document and codify our process, so that it can be disseminated in the form of a policy manual and accompanying software, to all other Free Software projects who wish to solidify their legal assembly process. Distilling nearly two decades of organizational know-how into easy-to-understand software and documentation is no easy task, and we will rely greatly on your financial support to aid us in carrying out this momentous task.

When?

[miffo.swe]

Now that the Linux development is totally transparent when will we be able to audit Microsoft, SCO, and other propriarity code for stolen bits and pieces?

We should shout out of the top of our lungs that the propriarity way foster code stealing because no one can audit it.