Language Selection

English French German Italian Portuguese Spanish

Torvalds 'pretty pleased' about new GPL 3 draft

Filed under
OSS

Linus Torvalds, leader of the Linux kernel project and a major figure in the open-source programming movement, said Wednesday he's "pretty pleased" with changes in a third draft of the General Public License (GPL) released Wednesday.

The Linux kernel and many higher-level software packages are governed by the current GPL 2, and Torvalds has expressed strong displeasure with earlier version 3 drafts. After a preliminary analysis of GPL 3, however, some of those concerns are gone or moderated, he said.

"I'm actually pretty pleased. Not because I think it's perfect, but simply because I think it's certainly a lot better than I really expected from the previous drafts," he said. "Whether it's actually a better license than the GPLv2, I'm still a bit skeptical, but at least it's now 'I'm skeptical' rather than 'Hell no!'"

In particular, one provision against digital rights management has been narrowed, and another that Torvalds feared could lead to multiple incompatible versions of the GPL has been removed or defanged.

"I'm much happier with many parts of it. I think much of it reads better, and some of the worst horrors have been removed entirely," Torvalds said.

Full Post.

GPLv3 third draft: Linus likes it, ACT hates it

Stressing that it's his initial take on the new draft, Torvalds wrote in an e-mail response to a request for comment Wednesday that the third draft is "a huge improvement on the previous ones." He's particularly impressed by the work the FSF has done on revising the language referring to patents.

Not surprisingly, the Association for Competitive Technology (ACT), a technology lobbying organization, which has been highly critical of GPLv3 especially in relation to DRM in the past, was negative about the latest draft of the license.

Full Story.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's leftovers

Software: VirtualBox, TeX Live Cockpit, Mailspring, Qt, Projects, and Maintainers

  • VirtualBox 5.2.2 Brings Linux 4.14 Fixes, HiDPI UI Improvements
    The Oracle developers behind VM VirtualBox have released a new maintenance build in the VirtualBox 5.2 series that is a bit more exciting than their usual point releases.
  • TeX Live Cockpit
    I have been working quite some time on a new front end for the TeX Live Manager tlmgr. Early versions have leaked into TeX Live, but the last month or two has seen many changes in tlmgr itself, in particular support for JSON output. These changes were mostly driven by the need (or ease) of the new frontend: TLCockpit.
  • Mailspring – A New Open Source Cross-Platform Email Client
    Mailspring is a fork of the now discontinued Nylas Mail client. It does, however, offer a much better performance, and is built with a native C++ sync engine instead of JavaScript. According to the development team, the company is sunsetting further development of Mailspring. Mailspring offers virtually all the best features housed in Nylas Mail, and thanks to its native C++ sync engine it uses fewer dependencies which results in less lag and a reduction in RAM usage by 50% compared to Nylas Mail.
  • Removing Qt 4 from Debian testing (aka Buster): some statistics
    We started filing bugs around September 9. That means roughly 11 weeks, which gives us around 8 packages fixed a week, aka 1.14 packages per day. Not bad at all!
  • Products Over Projects
    However, projects are not the only way of funding and organizing software development. For instance, many companies that sell software as a product or a service do not fund or organize their core product/platform development in the form of projects. Instead, they run product development and support using near-permanent teams for as long as the product is sold in the market. The budget may vary year on year but it is generally sufficient to fund a durable, core development organization continuously for the life of the product. Teams are funded to work on a particular business problem or offering over a period of time; with the nature work being defined by a business problem to address rather than a set of functions to deliver. We call this way of working as “product-mode” and assert that it is not necessary to be building a software product in order to fund and organize software development like this.
  • Why we never thank open source maintainers

    It is true that some of you guys can build a tool in a hackathon, but maintaining a project is a lot more difficult than building a project. Most of the time they are not writing code, but [...]

today's howtos

Tizen News