The Creative Commons Attribution 4.0 International and Attribution-ShareAlike 4.0 International licenses are now on our list of free licenses for works of practical use besides software and documentation.

We have updated our list of Various Licenses and Comments about Them to include the Creative Commons Attribution 4.0 International license (CC BY 4.0) and the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). Both of these licenses are free licenses for works of practical use besides software and documentation.

CC BY 4.0 is a noncopyleft license that is compatible with the GNU General Public License version 3.0 (GPLv3), meaning you can combine a CC BY 4.0 licensed work with a GPLv3 licensed work a larger work that is then released under the terms of GPLv3.

Most discussions of free software licenses bore listeners. In fact, licenses are usually of such little interest that 85%of the projects on Github fail to have one.

However, one aspect of licensing never fails to stir partisan responses: the debate over the relative advantages of copyleft licenses such as the GNU General Public License (GPL), and permissive licenses such as the MIT or the Apache 2 licenses.

You only have to follow the links to Occupy GPL! that are making the rounds to see the emotions that this unending debate can still stir. Calling for an end to "GPL purism," and dismissing the GPL as "not a free license," the site calls on readers to use permissive licenses instead, describing them as "truly OSS [Open Source Software] licenses and urging readers to "Join the Fight!"

Occupy GPL! itself is unlikely to have a future. Anonymous calls to actions rarely succeed; people prefer to know who is giving the call to arms before they muster at the barricades. Nor is the site's outdated name and inconsistent diction, nor the high number of exclamation and question marks likely to inspire many readers. Still, the fact that the site exists at all, and the counter-responses in comments on Google+ show that the old debate is still very much alive.

Having used OpenOffice for several years on the Panasonic Toughbooks I use in the field, I've avoided buying into traditional or subscription-based services. While enterprises may have a different view on licensing, cost most always figures into the decision-making process. So if they go the subscription route, they'll have to then ask what strategies they can use to lower those costs. Will they be able to haggle on price?

If the subscription model does become the norm, will OpenOffice and other open-source software thrive, dive, or stay the same in market share? I'd like to hear your thoughts.

Google has had enough of its long-running legal battle with Oracle over whether application programming interfaces (API)s can be copyrighted. The search giant has asked the Supreme Court of the United States (SCOTUS) to bypass further battles in lower courts and address the API copyright issue once and for all. SCOTUS, in return, is soliciting the Obama administration for its view of the case before moving forward.

Also: Top 10 FOSS legal developments of 2014

The litigation surrounding Android continued this year, with significant developments in the patent litigation between Apple Computer, Inc. (Apple) and Samsung Electronics, Inc. (Samsung) and the copyright litigation over the Java APIs between Oracle Corporation (Oracle) and Google, Inc. (Google). Apple and Samsung have agreed to end patent disputes in nine countries, but they will continue the litigation in the US. As I stated last year, the Rockstar Consortium was a wild card in this dispute. However, the Rockstar Consortium settled its litigation with Google this year and sold off its patents, so it will no longer be a risk to the Android ecosystem.

The copyright litigation regarding the copyrightability of the Java APIs was brought back to life by the Court of Appeals for the Federal Circuit (CAFC) decision which overturned the District Court decision. The District Court had found that Google was not liable for copyright infringement for its admitted copying of the Java APIs: the court found that the Java APIs were either not copyrightable or their use by Google was protected by various defenses to copyright. The CAFC overturned both the decision and the analysis and remanded the case to the District Court for a review of the fair use defense raised by Google. Subsequently, Google filed an appeal to the Supreme Court. The impact of a finding that Google was liable for copyright infringement in this case would have a dramatic effect on Android and, depending on the reasoning, would have a ripple effect across the interpretation of the scope of the “copyleft” terms of the GPL family of licenses which use APIs.