I just found out an interesting fact: from the 20 patches that are supposed to be included into the next stable 2.6.17.y (where y=10) kernel, 6 5 were done by OpenVZ developers.
What it could mean, besides the fact that OpenVZ team is a valueable contributor to the mainstream kernel? It also means we do care much for stability and security of OpenVZ, we do a lot of testing and QA, which is good for OpenVZ kernel, but for the mainstream kernel as well.
In a broader sense, this is a nice example of how collaborative open source development works. A nice example of “everybody wins” strategy. Indeed, in open source everybody wins.
http://lkml.org/lkml/2006/8/21/205
http://lkml.org/lkml/2006/8/21/206
http://lkml.org/lkml/2006/8/21/209
http://lkml.org/lkml/2006/8/21/213
http://lkml.org/lkml/2006/8/21/219
http://lkml.org/lkml/2006/8/21/223
Update: our kernel team found a bug in this blog post. Looks like the bug belongs to the infamous "off-by-one" category. :) There are actually 5 patches from OpenVZ developers, not 6 — it's just Greg sent one patch twice and thus I counted it twice. Fixed.
What it could mean, besides the fact that OpenVZ team is a valueable contributor to the mainstream kernel? It also means we do care much for stability and security of OpenVZ, we do a lot of testing and QA, which is good for OpenVZ kernel, but for the mainstream kernel as well.
In a broader sense, this is a nice example of how collaborative open source development works. A nice example of “everybody wins” strategy. Indeed, in open source everybody wins.
http://lkml.org/lkml/2006/8/21/205
http://lkml.org/lkml/2006/8/21/206
http://lkml.org/lkml/2006/8/21/209
http://lkml.org/lkml/2006/8/21/219
http://lkml.org/lkml/2006/8/21/223
Update: our kernel team found a bug in this blog post. Looks like the bug belongs to the infamous "off-by-one" category. :) There are actually 5 patches from OpenVZ developers, not 6 — it's just Greg sent one patch twice and thus I counted it twice. Fixed.


Comments
Do you still stand by your opinions above now in 2016?…