JetLib News

An anonymous reader writes “A petition has recently been started to get the developer of the popular Android ‘MIUI’ ROM, Chinese based Xiaomi, to comply with the GPL. While Android itself is licensed under the Apache 2.0 License, and therefore does not actually require derivative works to be FOSS, the Linux kernel itself is GPL-licensed and needs to remain open. Unless Xiaomi intends to develop a replacement for the Linux kernel, they need to make their modifications public.”

sfcrazy writes “A very serious argument erupted on the Linux kernel mailing list when Andy Grover, a Red Hat SCSI target engineer, requested that Nicholas A. Bellinger, the Linux SCSI target maintainer, provide proof of non-infringement of the GPL. Nick is developer at Rising Tide Systems, a Red Hat competitor, and a maker of advanced SCSI storage systems. Nick’s company recently produced a groundbreaking technology involving advanced SCSI commands which will give Rising Tide Systems a lead in producing SCSI storage systems. Now, RTS is blocking Red Hat from getting access to that code as it’s proprietary. What’s uncertain is whether RTS’ code is covered by GPL or not — if it is then Red Hat has all the rights to get access to it and it’s a serious GPL violation.”

DMA-BUF is a recent kernel feature that allows multiple GPUs to quickly copy data into each others’ framebuffers. A use case would be the NVIDIA Optimus that pairs a fast GPU with an Intel integrated GPU, where the NVIDIA GPU writes into the Intel framebuffer when it is active. But, NVIDIA won’t be able to use this infrastructure because it’s GPL. Alan Cox replied on LKML to a request from one of their engineers to mark the API non-GPL: “NAK. This needs at the very least the approval of all rights holders for the files concerned and all code exposed by this change. Also I’d note if you are trying to do this for the purpose of combining it with proprietary code then you are still in my view as a (and the view of many other) rights holder to the kernel likely to be in breach of the GPL requirements for a derivative work. You may consider that formal notification of my viewpoint. Your corporate legal team can explain to you why the fact you are now aware of my view is important to them.” The rest of the thread is worth a read (a guy from RedHat agrees that this code is GPL and cannot become non-GPL without relicensing from a major subset of graphics system contributors). This has a ripple effect: it means that all of the ARM SoC GPU drivers can’t use it either, and it may prevent any proprietary drivers for the proposed DRI version 3.

New submitter juenger1701 writes “Xbian‘s developer Koenkk has posted a reply to the code stealing accusations mentioned here Friday.” In response, Sam Nazarko of Raspbmc has replaced his earlier complaint, “on the agreement that XBian participate with compliance of the GPL.” Koenkk makes the case that his project has always complied with the GPL.

tetrahedrassface writes “Rasbmc developer Sam Nazarko is reporting that Xbian had violated the GPL and stolen his installer code without providing attribution and not releasing their source. His breakdown of events is interesting, and currently the Xbian project has been taken offline with several tweets saying Xbian development is terminated.”

David Gerard writes “It seems the authors of Stuxnet/Duqu/Flame used the LZO library, which is straight-up GPL. And so, someone has asked the U.S. government to release the code under the GPL. (Other code uses various permissive licenses. As works of the U.S. federal government, the rest is of course public domain.) Perhaps the author could enlist the SFLC to send a copyright notice to the U.S. government…”

Reader rtfa-troll writes: “‘GPL enforcement by Software Freedom Conservancy puts electronics makers on notice, leaves business users untouched,’ says Infoworld, going on to explain ‘You are several orders of magnitude more likely to be raided by your proprietary suppliers, in the form of the Business Software Alliance, than to ever hear from SFC, let alone face any action. License compliance is a major and costly issue for proprietary software, but the case concerns an end-user license agreement (EULA), not a source license.’ The article gives a good summary of why having GPL licenses enforced helps everybody, except for ‘hardware manufacturers — typically those creating low-cost consumer and business electronics’ who need to verify that they pass on the same rights to others as they received with the original code.”

An anonymous reader tipped us to news that the Software Freedom Conservancy is expanding its GPL compliance efforts. Quoting Bradley Kuhn: “This new program is an outgrowth of the debate that happened over the last few months regarding Conservancy’s GPL compliance efforts. Specifically, I noticed that, buried in the FUD over the last four months regarding GPL compliance, there was one key criticism that was valid and couldn’t be ignored: Linux copyright holders should be involved in compliance actions on embedded systems. Linux is a central component of such work, and the BusyBox developers agreed wholeheartedly that having some Linux developers involved with compliance would be very helpful. Conservancy has addressed this issue by building a broad coalition of copyright holders in many different projects who seek to work on compliance with Conservancy, including not just Linux and BusyBox, but other projects as well.” The anonymous reader adds: “This news was also discussed in the latest episode of the Free as in Freedom Oggcast.”

An anonymous reader tipped us to news that the Software Freedom Conservancy is expanding its GPL compliance efforts. Quoting Bradley Kuhn: “This new program is an outgrowth of the debate that happened over the last few months regarding Conservancy’s GPL compliance efforts. Specifically, I noticed that, buried in the FUD over the last four months regarding GPL compliance, there was one key criticism that was valid and couldn’t be ignored: Linux copyright holders should be involved in compliance actions on embedded systems. Linux is a central component of such work, and the BusyBox developers agreed wholeheartedly that having some Linux developers involved with compliance would be very helpful. Conservancy has addressed this issue by building a broad coalition of copyright holders in many different projects who seek to work on compliance with Conservancy, including not just Linux and BusyBox, but other projects as well.” The anonymous reader adds: “This news was also discussed in the latest episode of the Free as in Freedom Oggcast.” Update: 05/30 14:20 GMT by U L :It may not be entirely clear, but several Linux developers have assigned copyright so that the Conservancy can pursue violations for them.

GMGruman writes “Simon Phipps writes, “As Apache licenses proliferate, two warring camps have formed over whether the GPL is or isn’t falling out of favor in favor of the Apache License.” But as he explores the issues on both sides, he shows how the binary thinking on the issue is misplaced, and that the truth is more nuanced, with Apache License gaining in commercially focused efforts but GPL appearing to increase in software-freedom-oriented efforts. In other words, it depends on the style of open source.”