Language Selection

English French German Italian Portuguese Spanish

Why Torvalds is sitting out the GPLv3 process

Filed under

Why isn't Linus Torvalds involved with the drafting of the third version of the GNU General Public License (GPL)? Torvalds has frequently criticized the process and the drafts of the GPLv3, and recently voted against the license in an informal poll of kernel developers, so it seems obvious to question why he chose to sit out the process. Torvalds gives his reasons as a dislike of committees, an inability to contribute in his preferred way, and philosophical differences with the Free Software Foundation (FSF), which he suggests is trying to absorb other licenses under the GPL.

At the same time, he suggests that his opposition may have been distorted or exaggerated. "GPLv3 is not 'evil,'" he says. "It just doesn't stand up to the great licenses out there, like the GPLv2."
According to Jim Garrison, public relations coordinator of the Software Freedom Law Center (SFLC), whose members are involved in drafting the GPLv3, "Linus was personally assured from the outset of the process that his participation was actively sought."

Torvalds replies that he was invited only in the sense that "everybody was invited to participate. In that sense, yes, I certainly could have, too." However, apparently unaware that the GPLv3 committees do most of their work by email or IRC, he goes on to say that, "It's absolutely true that I could have been part of some committee. I could probably even have gotten somebody to pay for flights to Chicago or some other nasty place to go to meetings at. I didn't feel it was worth it."

Instead, Torvalds put forward an offer to read and comment on the first draft before it was published in January. "That was denied," Torvalds says.

Full Story.

More in Tux Machines

NVDA 2019.3beta1 now available for testing

Beta1 of NVDA 2019.3 is now available for download and testing. For anyone who is interested in trying out what NVDA 2019.3 has to offer before it is officially released, we welcome you to download the beta and provide feedback. NVDA 2019.3 is a very significant release as there are a great deal of under-the-hood changes which improve security and allow for some pretty cool innovations in the future. The most significant changes are the upgrade of Python 2 to Python 3, and a major re-write of NVDA’s speech subsystem. As these changes require add-ons and custom synthesizer drivers to be re-written, we plan to make the 2019.3 beta cycle much longer than normal, so that we can ensure that add-on developers have plenty of time to upgrade and test their add-ons with NVDA 2019.3 betas before 2019.3 stable is officially released. the current plan is to release several more betas over this month, and hopefully make the official release very early in the new year. Read more Also: NVDA 2019.3 Beta 1 is available

Graphics: Mesa, Vulkan and PipeWire

  • ADriConf GUI Control Panel Support For Mesa Vulkan Drivers Is Brought Up

    One of the most frequent complaints we hear from Linux gamers running open-source GPU drivers is over the lack of the hardware vendors supporting any feature-rich control panels like they do on Windows. There are many Linux driver tunables exposed by these open-source graphics drivers, but often they can only be manipulated via command-line options, environment variables, boot parameters, and other less than straight-forward means especially for recent converts from Windows and other novice Linux users. ADriConf has been doing a fairly decent job as a third-party means of helping to improve the situation and now there is talk of it supporting Vulkan driver settings.

  • Vulkan 1.1.130 Released With New Tooling Extension

    The new extension with Vulkan 1.1.130 is VK_EXT_tooling_info. The VK_EXT_tooling_info extension is for letting the Vulkan application/game/engine query what development tools are running right now. In particular, this is for tools like RenderDoc and other Vulkan profilers/debuggers. This extension will offer some uniformity and assistance to developers in debugging potential compatibility issues between Vulkan tools and other problems.

  • New graphing tool for PipeWire debugging

    PipeWire, the new and emerging open source framework that aims to greatly improve the exchange and management of audio and video streams inside a Linux system, has seen a number of improvements and bug fixes over the past year. With many developers now actively contributing to it, PipeWire is maturing quickly and is well on its way to becoming the new standard. At Collabora, we have been busy helping clients work with PipeWire, notably Automotive Grade Linux who have chosen to adopt PipeWire for its implementation of the low-level platform audio service, replacing previous solutions like 4A, PulseAudio and AudioManager. Assisting early adopters such as AGL has brought us to design and implement new elements within PipeWire, such as the session & policy management component WirePlumber, which George Kiagiadakis presented in October at the GStreamer Conference in Lyon.

Odio is a Classy Looking Radio Player for Linux Desktops

If so, check out Odio (styled ‘odio’). This is a free Electron-based radio streaming app for Windows, macOS and Linux desktops. Odio has super clean UI that is, to my eyes at least, somewhat inspired by Spotify’s desktop client (no bad thing). Plus, the app touts broad internal radio station support (over 20,000, apparently) and offers a couple of handy customisation options. Read more

LibreCorps mentors humanitarian startups on how to run the open source way

Free and open source software are no longer workplace taboos, at least not in the same way they were fifteen years ago. Today, distributed collaboration platforms and tools empower people around the world to contribute code, documentation, design, leadership, and other skills to open source projects. But do newcomers actually have a deep understanding of free and open source software? If you hang around in open source communities for long enough, you realize there is more to open source than slapping a free software license on a project and throwing it over an imaginary fence to wait for contributors who never come. To address this problem in the humanitarian sector, the LibreCorps program, led by Rochester Institute of Technology's FOSS initiative at the Center for Media, Arts, Interaction & Creativity (MAGIC,) partnered with UNICEF to develop a set of resources to help new open source maintainers chart an "open source roadmap" to build a community. Read more