Linux kernel developer's guide published
The Linux Foundation has released a guide for developers who wish to contribute Linux code.
A guide to the kernel development process aims to encourage participation by new programmers by explaining what's involved. Some developers and businesses attempting to submit changes to the Linux kernel find themselves tangled up with the processes used, according to the guide, which was written by Jonathan Corbet, executive editor of lwn.net and himself a Linux developer.
"A developer who does not understand the kernel community's ways (or, worse, who tries to flout or circumvent them) will have a frustrating experience in store," Corbet warned.
One major stumbling block is coders not taking into account the development lifecycle. According to the guide, patches deemed stable are "merged" into the mainline kernel at the beginning of the lifecycle, every two to three months.
The "merge window" lasts for two weeks, and is then closed. After that time, project lead Linus Torvalds issues a release candidate kernel, which is then stabilised. Developers who try to merge new features outside the merge window "tend to get an unfriendly reception", wrote Corbet, as usually only release-candidate fixes are accepted.
Dissatisfaction also arises from confusion over how patches are reviewed before being merged, according to the guide.
"Much developer frustration comes from a lack of understanding of this process or from attempts to circumvent it," wrote Corbet, who added that patches go through a series of reviews before and after they are accepted into the kernel.
At the moment, there are more than 1,000 developers at more than 100 companies making contributions to the kernel, according to the Linux Foundation. The not-for-profit organisation said the 30-page guide is central to its efforts to expand this community.
Mark Taylor, president of the Open Source Consortium, said that while it isn't that difficult to contribute to open-source projects, to avoid disappointment there are processes that must be adhered to.
"The bigger and more important the project, the more likely it is to have a number of levels," Taylor told ZDnet.co.uk on Friday. "Enterprise-class projects, including the Linux kernel, have more processes, but that shows how seriously they take the project. It's less difficult to get code into a project if you understand the rules."
Taylor added that it was "a misconception that open-source projects are total anarchy", and that enterprise-class projects, including Linux, often have a "beneficent dictator".
"It's not chaos – they have rules," said Taylor. "They have a beneficent dictator. Linus in the Linux kernel has lieutenants around him, [as does] Jeremy Allison at Samba."