Process Improvements in the Kernel Development 124
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."
Groklaw article (Score:5, Informative)
It covers more or less the same territory in a bit more depth.
This quote says it all (Score:5, Informative)
[RFD] Explicitly documenting patch submission (Score:4, Informative)
Posted anonymously to avoid karma whoring.
Link to Linus' Mailing List Post (Score:3, Informative)
Re:Linus retiring? (Score:5, Informative)
He'll pass version 2.6 to someone and then start work on 2.7, just as he passed 2.4 to Marcelo Tosatti and then began working on 2.5.
Thread on kerneltrap (Score:5, Informative)
Just thought it could be interesting...
Re:Linus retiring? (Score:4, Informative)
Re:Details? (Score:3, Informative)
Re:Linus retiring? (Score:4, Informative)
Google link to full text (Score:1, Informative)
The original thread (Score:4, Informative)
Re:tracking (Score:2, Informative)
Re:Accounting (Score:5, Informative)
Over years, Linux development team has become an enterprise. Finally they realised that they need accounting.
Just a clarification: What Linus is doing is making the accountability easier and somewhat more complete, not adding it. As he pointed out in his LKML post, Linux developers have been able to find the origin of every bit of code they've needed to, but the process has been painful and has required a little guesswork, particularly for the oldest stuff.
What he's proposing here is just a slight formalization and elaboration of the process that has been used for years. Currently, if I submit a patch to LKML to fix, say, a VFS bug, it will get poked, prodded and adjusted on the mailing list until people think it's clean and solid. Then the subsystem maintainer (Al Viro, in this case) will pick it up, probably tweak it some more, attach a "From" comment, stating that I am the author and forward it to Linus. Linus will review it, accept it, and his scripts will add my name into the changelog and the CREDITS file.
Since all of this happens on the public, archived, mailing list, there's plenty of accountability, but figuring out the sequence of events requires digging through the archives, and there may not be any obviously ideal search criteria.
Now, Linus wants me to attach my name myself, and to do it in a standardized format so that it's more searchable. Further, he wants everyone else who modifies the patch in any way to add their stamp as well, providing a change history in the patch itself. It's a weak change history, since it doesn't describe what changed, but it provides the starting point for searching the archives.
So, what Linus is asking for isn't so much to create a better accountability trail as it is to make the existing trail easier to follow. It's an ease-of-use optimization.
Well, there is one way in which this is perhaps a significant enhancement, and that is that Linus wants to formally define the legal commitment a contributor makes. In a reasonable world, this should be unnecessary, since if I contribute some code that I don't own, I should be the one held liable for the copyright infringement, not the others who used it in good faith. In the litigious world we live in, however, it's a good idea to formally spell it out, and make clear to everyone that by attaching their name to a patch, they're providing a certain warranty of their right to contribute it.
Re:[RFD] Explicitly documenting patch submission (Score:2, Informative)
[RFD] Explicitly documenting patch submission (Score:2, Informative)
Heh... (Score:2, Informative)
Go figure?