Language Selection

English French German Italian Portuguese Spanish

Open to Misinterpretation

Filed under
OSS

Before "open source", before free software, there was software in the public domain. You could say that software in the public domain was truly free. The code was "open source" and the user had the right to take it, break it, appropriate it, re-use it, package it, sell it, re-brand and license it, or do what you will with it.

The problem with software in the public domain, was that, more often than not, any changes to the software didn't come back to the developer in any usable form, and modifications didn't revert to the original maintainer of the code. In some cases the software was appropriated and relicensed by the user. In other words there was no guarantee that the software would remain free, or would grow.

The solution to this problem was the GPL. Not only did the GPL protect free software and keep it free, but it opened the door for a community to form around the software in the knowledge that contributions were fed back into the original body of code. The often criticised "viral" nature of copyleft and the GPL was the instrument that fostered participation and feedback from the community, and provided the framework for the later success of free and "open source" software.

More Here.




More in Tux Machines

WebKitGTK+ 2.5.2 Drops GTK+2 Dependency

WebKitGTK+, a version of the WebKit open source web engine that uses GTK+ as its user-facing frontend, has reached version 2.5.2. Read more

today's leftovers

Proposed: A Tainted Performance State For The Linux Kernel

Similar to the kernel states of having a tainted kernel for using binary blob kernel modules or unsigned modules, a new tainting method has been proposed for warning the user about potentially adverse kernel performance. Dave Hansen of Intel has proposed a new "TAINT_PERFORMANCE" for the kernel that would proactively print a warning message about not using the kernel for any performance measurements. Dave explained in his RFC announcement, "I have more than once myself been the victim of an accidentally-enabled kernel configuration option being mistaken for a true performance problem. I'm sure I've also taken profiles or performance measurements and assumed they were real-world when really I was measuring the performance with an option that nobody turns on in production. A warning like this late in boot will help remind folks when these kinds of things are enabled." Read more

Scientific Linux 7.0 x86_64 BETA 3

Fermilab's intention is to continue the development and support of Scientific Linux and refine its focus as an operating system for scientific computing. Today we are announcing a beta release of Scientific Linux 7. We continue to develop a stable process for generating and distributing Scientific Linux, with the intent that Scientific Linux remains the same high quality operating system the community has come to expect. Please do not install Pre-Release software in your production environment. Read more