{"id":764,"date":"2011-03-21T00:55:22","date_gmt":"2011-03-20T23:55:22","guid":{"rendered":"http:\/\/www.gennard.net\/blog\/?p=764"},"modified":"2011-03-21T00:55:22","modified_gmt":"2011-03-20T23:55:22","slug":"google-gpl-2-linux-headers","status":"publish","type":"post","link":"http:\/\/www.gennard.net\/blog\/2011\/03\/google-gpl-2-linux-headers\/","title":{"rendered":"You can make money without doing evil&#8230;"},"content":{"rendered":"<p>Well this is what google says in their corporate philosophy but I seriously doubting this.<\/p>\n<p>If you are not aware of the most recent cuffle about google, let explain and perhaps rant a little.<\/p>\n<p>Google; in an attempt to prevent the spread of the gpl-2 license from the linux kernel on the android platform to user&#8217;s application decided to clean the kernel headers of it so it can be used in the bionic libc.<\/p>\n<p>My understanding of the gpl-2 license is that once you have applied the license to your code, you are free to change it, include it and attribute your changes but the gpl-2 remains, so I can not see how they can clean the code of the license when the license itself prohibits it.<\/p>\n<p>Cleaning up the linux headers files does not seem such a big deal at first especially given the linux chaps have the own sanitised version themselves but it really does open it a huge whole in the open source arena.  If you can remove the gpl-2 from the linux headers which contain macro&#8217;s aka inline code then why can&#8217;t you do the same for other gpl-2 software and release it or use it anyway you wish.   After all if google can do it without doing any evil&#8230; why can&#8217;t anyone else do the same?<\/p>\n<p>Is this the end of gpl-2 or just the start of new legal battle with the do no evil company being covered the brown stuff.<\/p>\n<p>So what should google to next&#8230;<br \/>\n &#8211; standup and say &#8220;sorry&#8221; and &#8220;we will fix it&#8221;<br \/>\n &#8211; move bionic libc to the proper sanitized headers<br \/>\n &#8211; reissue a firmware that mitigates issue<br \/>\n &#8211; put some more love in the open source arena and stop taking evil shortcuts<\/p>\n<p>Anyway rant over&#8230; lets see what happens next&#8230;<\/p>\n<p>http:\/\/www.brownrudnick.com\/nr\/pdf\/alerts\/Brown%20Rudnick%20Advisory%20The%20Bionic%20Library-Did%20Google%20Work%20Around%20The%20GPL.pdf<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Well this is what google says in their corporate philosophy but I seriously doubting this. If you are not aware of the most recent cuffle about google, let explain and perhaps rant a little. Google; in an attempt to prevent &hellip; <a href=\"http:\/\/www.gennard.net\/blog\/2011\/03\/google-gpl-2-linux-headers\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,11],"tags":[95,212,213,125],"_links":{"self":[{"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/posts\/764"}],"collection":[{"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/comments?post=764"}],"version-history":[{"count":0,"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/posts\/764\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/media?parent=764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/categories?post=764"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.gennard.net\/blog\/wp-json\/wp\/v2\/tags?post=764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}