GPL Violations

GPL Violations wins case against D-Link. D-Link had argued that the GPL was not legally binding.

On September 6, 2006 the district court issued its judgement, confirming the claims by gpl-violations.org, specifically its rights on the subject-matter source code, the violation of the GNU GPL by D-Link, the validity of the GPL under German law, and D-Links obligation to reimburse gpl-violations.org for legal expenses, test purchase and cost of re-engineering. Only the amount of the legal expenses was considered too high by some insignificant amount of 300 EUR. Therefore, this decision marks a clear-cut victory for gpl-violations.org. D-Link may file an appeal against the judgement.

(Via Cyberlaw)

Evolution of a Social Contract (the GPLv3 process)

OK so the GPL is a copyright license. But in part it has also evolved into something larger than life. It has become one of those rare things among legal documents – an icon.

Naturally it is not alone in this position. But what is interesting is that other icons tend to be “larger”. The US constitution is an icon, the declaration of rights is an icon. Very few contracts and licenses can be called iconic since few or none ever make it outside their small community. So what happens when the process of technological development forces the “evolution” of a license?

Unlike nature we cannot expect a natural selection. The development must be moved by an outside force. It can be done either dictatorially or democratically. In one way dictatorially is easier – you don’t have to ask all the people what they think. But using this process does not work with software licenses since the dissatisfaction of users will only lead to the demise of the license. Democracy also has its advantages. It allows for participation and the ability of smart people to bring forward comments and ideas that the dictator may not have recognised. The GPL has chosen a democratic process.
The formal system can best be seen in the overview of the process, which begins with the initial release and presentation of the draft of the GPLv3 with additional documentation such as the overview of the review system and the explanatory documents. In addition to the more formal structure the information needs to be communicated out to the users and to ensure an equality of information transfers was established. The latter was accomplished primarily through the use of the Internet as a distribution method of all texts and additional audio and video material.

The essence of the drafting process here described is to make it possible for the Free Software Foundation to decide the contents of the GPL through the fullest possible discussion with the most diverse possible community of drafters and users. Ideally, we would identify every issue affecting every user of the license and resolve these issues with a full consideration of their risks and benefits. In order to accomplish such a large task, the discussion process involves individual community members and Discussion Committees that represent different types of users and distributors.

The process was formally commenced with the release of the first Discussion Draft of version 3 of the GPL (including additional explanatory material) at the first International Public Conference in January 2006, at the Massachusetts Institute of Technology. The two day event at MIT was recorded and the audio video material was also made available online. The second draft has recently been released.

To ensure that comments on the GPL are collected and dealt with Discussion Committees have been formed. The members of the committees were chosen to represent diverse users groups such as â??â?¦large and small enterprises, both public and private; vendors, commercial and noncommercial redistributors; development projects that use the GPL as a license for their programs; development projects that use other free software licenses, but are invested in the contents of the GPL; and unaffiliated individual developers and people who use softwareâ??. The role of these committees is to organise and analyse the received comments and propose solutions.

The FSF invited the initial members of the Discussion Committees but granted the committees the power to invite further members and to autonomously organise their work process. The committees work to encourage commentary on the license from the sectors they represent. Once the comments have been collected, organised and analysed the committee is responsible for presenting its results of the deliberations to the FSF.

Aside from this organisational method of soliciting and analysing comments from a wider public the FSF have created an online method of allowing anyone to comment directly on the license draft. This is done by creating a software based commenting system, which works in this way. The draft text of the GPLv3 is online and users can mark a section of text, which they wish to comment, and then type â??câ??. Doing this opens a comment box, which allows the user to add a comment.

Once a user has commented on a section of text that section becomes highlighted. If no-one has commented on the text the background colour is white. After a comment the background is light yellow. The colour of the background becomes progressively darker for each comment added. This colour system allows users to see at a glance which sections of the draft are the most commented.

By holding the cursor over highlighted text the user is informed how many comments have been made on that section. By clicking on highlighted text the comments that have been made appear and can be read. The latter feature has the added benefit of reducing the amount of duplicated comments since the commentator can see the commentary of others.
So what are you waiting for? Participate in the democracy!

GPLv3 Second draft

Never turn your back on progress. I was offline for a couple of days and the second discussion draft was published along with explanatory texts and the first discussion drafts of the GNU Lesser General Public License. This was a couple of days ago – but still well worth reporting here.

The second discussion draft of the GNU General Public License version 3 was released on 2006 July 27, along with the first discussion draft of the GNU Lesser General Public License.

Read all about it!

GPLv3 issues: TiVO-isation

This is the first of a series of discussions on the version 3 of the GPL. This post will report on the oddly named process of TiVO-isation.

At times the GNU/Linux desktop operating system is seen as the flagship of Free Software but it is important to remember that while the flagship is important and symbolic it is not the foundation upon which the impact of Free Software should be measured.

The greatest technological foundation of Free Software is the use of stripped down Linux kernels in embedded applications. One such application is the TiVO recorder. The TiVO is an embedded device made up of several GNU packages. The device is capable of recording several TV channels at the same time.

The definition of Free Software is sometimes reproduced in a simple â??four freedomsâ?? format. If software fulfils these four conditions it is Free. If any of the four freedoms is limited in any way the software is proprietary. For the sake of completeness the four freedoms are listed here:

Freedom to run the program, for any purpose (freedom 0).
Freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
Freedom to redistribute copies so you can help your neighbor (freedom 2).
Freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

According to the freedoms it permissible to modify a GPL licensed program without re-distributing it, or running proprietary software on top of the GPL licensed software.

The TiVO has modified GNU/Linux in order to implement DRM within the operation of their video recorder. In compliance with the GPL, they released the source code for these modifications. Users are therefore able to modify the code and the operation of the video recorder. To this extent the TiVO is GPL compliant.

The problem is that TiVO contains a special mechanism that shuts down the machine if the user attempts to install modified software. Therefore the user is allowed to modify the code but is prevented from in reality from using these modifications in the embedded application of the TiVO. This makes freedom 1 into a sham.

The new version of the GPL (version 3) will prevent the compliance with the letter of the freedoms without the compliance to the purpose and spirit of the GPL.