Microsoft: Novell is toast and the patent Juggernaut rolls on

The end of 2010 has been interesting. Mass defections from Oracle's OpenOffice team and the software is ported as LibreOffice. Then Mark Shuttleworth announces that Wayland is in, Xorg is out and Unity will be the next Ubuntu desktop. I was just getting my head around all that when the newswires started humming again with the news that Novell had been sold. I experienced a strong sense of deja vu and began to wonder if this was going to be a reprise of Sun's sale to Oracle and the forking of OpenOffice, one of the crown jewels of GNU/Linux.

Confusion and Complexity: High time to prune the Creative Commons licenses?

In a recent blog, Nina Paley, the animator behind the free-licensed animated film, "Sita Sings the Blues", complained of the enormous confusion caused by poor differentiation of the Creative Commons licenses. In particular, there's a great deal of confusion over the difference between "NonCommercial" and "ShareAlike" licenses. Maybe the Creative Commons licensing system is still too complex? I'd suggest that only three licenses are really needed: "Attribution" (CC By), "ShareAlike" (CC By-SA), and "NonCommercial" (CC By-NC), and that the others are essentially deadweight that's holding the movement back.

Doing the Impossible

There is no "magic" to commons-based peer production. Most of the techniques that have brought free culture products ranging from software to art to electronic hardware have been in play for hundreds or thousands of years. But they do run counter to the patterns of commercial proprietary industry. Due to the massive improvements in communications and authoring technology, we have reached a point where we can be more productive in our "leisure" than we are in our "work". And any labor of love is almost always going to be superior to labor alone.

Why "open source" is not "free software"

Choosing to release a piece of software under the terms of a free software license is an important step through which many programmers and writers first approach the free software community. However, the myriad of licenses available can sometimes confuse and disorient the user, sometimes making this first step much harder than it should be. Let's try and make things clearer.

What if copyright didn't apply to binary executables?

By rights, copyright really shouldn't apply to binary executables, because they are purely "functional" (not "expressive") works. The decision to extend copyright to binaries was an economically-motivated anomaly, and that choice has some counter-intuitive and detrimental side-effects. What would things in the free software world look like if the courts had decided otherwise? For one thing, the implementation of copyleft would have to be completely different.

Hypothetical? Academic? Not if you're a hardware developer! Because this is exactly what the law does look like for designs for physical hardware (where the product is not protected by copyright).

GPLv3: Do we really need it?

I assume that people who read will most likely be aware of the fact that the Free Software Foundation is working on an update to the GPL version 3. If you're not, a number of articles and blog posts have been written on the subject. But with the Linux kernel developers stating that they oppose many of the changes, and with some people licensing software explicitly as "GPLv2" rather than "GPLv2, or any later version", one could wonder whether the whole update effort makes any sense.


Views on the GPLv3 hoo-har

There has been a lot of hoo-hah recently regarding the pros and cons of certain aspects of the drafts of Version 3 of the GNU General Public License from the Free Software Foundation. The originator of the Linux kernel, Linus Torvalds himself, is playing a role here. Unfortunately, each side has taken to the ploy of misrepresenting the other’s points. Arguments are getting heated to such an extent that you need to wear an asbestos suit just to look at the issues. However, on examination, not only do I find that both sides have valid issues but I also believe an obvious solution exists that will make most, if not all, satisfied and the world a less flame-ridden obstacle course.

The GNU GPL - a software license for yesterday, today and tomorrow

With the draft of the GNU General Public License Version 3 (GPLv3) have come many interesting comments, although not all of which I have found positive. While I understand proprietary vendors have offered complaints against a license they do not even use, I was surprised that Linus Torvalds had taken some issues which I thought were in any case misguided criticisms.

Subscribe to RSS - licenses