Quotes of the week
When a mechanism is introduced that makes it easy to disable a system feature in the LSM environment I start hearing voices saying "You can't use security and the cool thing together", and the developers of "the cool thing" wave hands and say "just disable it" and it never gets properly integrated. I have seen this so many times it makes me wonder how anything ever does get made to work in multiple configurations.— Casey Schaufler
I'm stepping down from all my maintainer roles. My first commit feed9bab7b14 ("spi: omap2_mcspi PIO RX fix") to the kernel was back in 2008 for v2.6.24 so I have been here for a long time. Thank you everyone who I have worked with, there are too many to list here.— Kalle Valo, wireless network driver maintainer, moves on
The DCO [developers certificate of origin] is a rather neat trick of legal hackery, and it works ok for Linux but the reason it works well in the Linux project is somewhat unique to Linux. The most important thing I want to draw the GDB community's attention to is that the DCO is specifically designed to shift the blame and burden for improperly licensed code ending up in the codebase *onto the individual developers personally*. This works great for companies, as it limits their liability. In practice, it's rare anyone gets sued, so Linux folks are ok with the legal hack. But I regularly urge developers to think carefully if they really want to take on such risk themselves.— Bradley Kuhn