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.

2 of 520 comments (clear)

  1. Copyright law protects you even without click-wrap by st.+augustine · · Score: 5, Informative
    Copyright law says no one can make copies, period (with a few "fair use" exceptions, which are more limited than many /. readers seem to think). Without a license, you can't make copies; it doesn't matter whether you've "agreed" to the license or not. The only way you can make copies is under the terms of the license. If you make copies in violation of the license, you're in violation of copyright law. The reason commercial software has click-wrap licenses is that they want to restrict rights evem further than the law already does.

    Have your lawyers read Eben Moglen on enforcing the GPL.

    --

    -- Some things are to be believed, though not susceptible to rational proof.
  2. The GPL doesn'[t need a click-through agreement by Animats · · Score: 5, Informative
    The GPL doesn't need a click-through agreement, because it's about copying, not use.

    Read the article by Eben Moglen, the lawyer who, for the Free Software Foundation, actually enforces the GPL.

    • Because there's nothing complex or controversial about the license's substantive provisions, I have never even seen a serious argument that the GPL exceeds a licensor's powers. But it is sometimes said that the GPL can't be enforced because users haven't ``accepted'' it.

      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.