Slashdot Mirror
Click-Thru Licensing on Open Source Software?
Russ Nelson writes "At the July OSI board meeting last week, we approved the Academic Free License (think MIT/BSD/X11/Apache with a patent grant) and we sent four licenses back for reconsideration. Here's the hitch: we were asked to approve a license which includes a requirement for click-wrap. Read more to see why we're asking you about it.
The submittor had already been asked if that requirement was a necessity. She said yes, because of various legal precedents. We consulted a few people and yes, it looks like a license without click-wrap is weaker at protecting your rights. So, folks, the lawyers are coming. The time is coming when you won't be able to distribute software unless you have presented the license to the user and their assent is necessary to access the software. Even free software. Our industry is maturing and we need to be more legally careful and rigorous.
The question here is whether we should amend the Open Source Definition so that it is clear whether click-wrap licenses are allowable or not. We could go either way, but we want to hear from you first. Your opinions solicited, and engaged!" While I can understand some legal necessities are necessary in the software world, click-thru licenses have never, and will never, make sense to me. Maybe commercial software has soured me on the concept, but I dislike agreeing to something before I even get a chance to use it.
Have your lawyers read Eben Moglen on enforcing the GPL.
-- Some things are to be believed, though not susceptible to rational proof.
Read the article by Eben Moglen, the lawyer who, for the Free Software Foundation, actually enforces the GPL.
This claim is based on a misunderstanding. The license does not require anyone to accept it in order to acquire, install, use, inspect, or even experimentally modify GPL'd software. All of those activities are either forbidden or controlled by proprietary software firms, so they require you to accept a license, including contractual provisions outside the reach of copyright, before you can use their works. The free software movement thinks all those activities are rights, which all users ought to have; we don't even want to cover those activities by license. Almost everyone who uses GPL'd software from day to day needs no license, and accepts none. The GPL only obliges you if you distribute software made from GPL'd code, and only needs to be accepted when redistribution occurs. And because no one can ever redistribute without a license, we can safely presume that anyone redistributing GPL'd software intended to accept the GPL. After all, the GPL requires each copy of covered software to include the license text, so everyone is fully informed.
A requirement imposed on whom, to do what?
What precedents? Whom did you consult? Whose rights? What's the argument?
What kind of FUD is this? Are you telling us it's a forgone conclusion that you will accept this license? Are you telling us that the FSF (which defines "free software") will accept this license? Are they and other free software distributers going to change their licenses to require click-through?
Come on, Russ. Give us the facts, straight, so we have some basis for discussion.
The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
Nobody is saying click-through licenses would be required. The question is should they be allowable under the official Open Source definition.
The OSI board doesn't force anyone to use a particular approved license on any given program. What they want to know is should they approved any license that requires assent before installing the associated program.
In my mind this doesn't violate any of the other requirements of the Open Source Definition so I think it really matters more what is in the license than how it is presented. The questioner seems to be acknowledged the fact that the receiving party has to agree to the license for it to be valid, so I don't really understand the problem. The GPL (and any other open source license) can be violated just like commercial licenses. Instead of assuming the user agrees to the license make them say so if you want the extra legal protection. You might need it if you wind up in court.
Si vis pacem, para bellum
The only thing more annoying than a Libertarian is an (un|mis)informed Libertarian
The OSD was developed by the Debian group under the aegis of Software in the Public Interest. Nobody who is presently involved with OSI had any part of that.
OSI is probably the biggest mistake I've ever made, and yes it's my mistake. It's time to clean it up. The OSD should be returned to SPI, who can be trusted to administer it sanely.
Bruce
Bruce Perens.
Having read some of what Eben Moglen wrote, I'm inclined to agree. Software is covered under copyright, and copyright grants your work protection by default. We don't need a shrinkwrap on a book to note that copying it is illegal; the same should remain true of software.
Obviously, Free Software producers must be able to deny warranties, since they are not getting the consideration (money) necessary to provide them. People who want warranties should be able to buy them, either from the software producer, another software shop, or an insurance company.
It's different with cars, because cars have a high potential to do physical injury to people and are thus expected to be built to a higher standard.
Bruce
Bruce Perens.
There are many reasons why click-through licenses are bad:
- They obviously place the software distributor in a place of power over the end user, something that free software is supposed to combat.
- There is no clear way to define who agreed to what. What if the purchaser isn't the same as the user? What if a user installs software on a computer and then resells that computer, with it's software, to another user.
- Software licensing is too complicated. That complication is a barrier to entry for small, independent software authors. Promotion of a software "fair use" doctrine that says that click-through licenses are unnecessary seems to be in the public interest.
- Click-through licenses provide a convenient method for a downhill slide towards prohibition of other fair uses, such as reverse engineering or published benchmarks or criticism. They may also provide a mechanism for other onerous goals: censorship ("you agree not to use this software to produce communist manifestos"), patent abuse ("you agree that our patents are valid"), barring trade or competition ("you agree not to sell this program to Pakistan or the FBI")... The list is endless. Not that this is what's planned, but once the door is opened, who knows where it leads?
- Every additional click-through license in use marginalizes the existing non-click-through licenses, making them seem more like some lunatic fringe rather than plain use of copyright law. No matter how OSI feels about the FSF and the GPL, I as a user understand and appreciate the GPL's stand on this issue: "You are not required to accept this License, since you have not signed it.
- Click-wrap licenses, if they spread to other media, will quickly lead us into a "pay-per-use" world. Click-wrap issues have barely been touched by the courts, and a small push in the right direction now may help keep us away from that path.
Please fight to keep click-wrap licenses away from Free and Open-Source Software. I understand that overly cautious lawyers (is there another kind?) will wring their hands over the idea of bucking the trend, but this is a battle worth fighting."Use" contracts make no sense (and have been shot down by courts when applied to other copyrighted content). Though you have not provided any details as to why the party in question wants them, I fail to see a compelling legal reason why they should be allowed.
Please reply to eds at reric.net if I can be of any assistance.
314-15-9265