Changeset 1737

Show
Ignore:
Timestamp:
05/12/05 11:44:09 (4 years ago)
Author:
karman
Message:

cleaned up anchors; added "non-legal" but encouraged"

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/swish_website/src/license.html

    r1730 r1737  
    4242As a special exception, the copyright holders of Swish-e give you 
    4343permission to link Swish-e with independent modules that communicate with 
    44 Swish-e solely through the libswish-e API interface, regardless of the license 
    45 terms of these independent modules, and to copy and distribute the 
     44Swish-e solely through the libswish-e API interface, regardless of the  
     45license terms of these independent modules, and to copy and distribute the 
    4646resulting combined work under terms of your choice, provided that 
    47 every copy of the combined work is accompanied by a complete copy of 
    48 the source code of Swish-e (the version of Swish-e used to produce the 
    49 combined work), being distributed under the terms of the GNU General 
     47every copy of the combined work is accompanied by, or provides a URL link to, 
     48a complete copy of the source code of Swish-e  
     49(the version of Swish-e used to produce the combined work),  
     50being distributed under the terms of the GNU General 
    5051Public License plus this exception.  An independent module is a module 
    5152which is not derived from or based on Swish-e. 
    …… 
    290291 
    291292<dl> 
    292 <a name="special"></a> 
    293 <dt> 
    294 So what's the deal with the special exception to the standard GPL?</dt> 
     293 
     294<dt> 
     295<a name="special"> 
     296So what's the deal with the special exception to the standard GPL? 
     297</a> 
     298</dt> 
     299 
    295300<dd> 
    296301<p>The GNU GPL allows for a special exception to the "tainting" behaviour of the GPL. 
    …… 
    318323</dd> 
    319324 
    320 <dt>I want to develop a new API interface to Swish-e in [<i>insert your favorite programming 
    321 language here</i>]. Can I do that under the Swish-e License?</dt> 
     325 
     326<dt> 
     327<a name="api"> 
     328I want to develop a new API interface to Swish-e in [<i>insert your favorite programming 
     329language here</i>]. Can I do that under the Swish-e License? 
     330</a> 
     331</dt> 
    322332 
    323333<dd>Why yes, you can! <a href='#special'>See FAQ #1</a>.</dd> 
    324334 
    325 <dt>Why did you switch from the LGPL? You've ruined [<i>insert name of your favorite project 
    326 here</i>]!!</dt> 
     335 
     336<dt> 
     337<a name="rationale"> 
     338Why did you switch from the LGPL? You've ruined [<i>insert name of your favorite project 
     339here</i>]!! 
     340</a> 
     341</dt> 
    327342 
    328343<dd> 
    …… 
    345360</dd> 
    346361 
    347 <dt>If I write a new API module in [<i>insert your favorite programming 
     362 
     363 
     364<dt> 
     365<a name="srccode"> 
     366If I write a new API module in [<i>insert your favorite programming 
    348367language here</i>] and take advantage of the Swish-e License's "special exception" to the GPL, 
    349368do I really have to include the Swish-e source code with my module? 
    350 </dt> 
     369</a> 
     370</dt> 
     371 
    351372<dd> 
    352373<p> 
    …… 
    371392</dd> 
    372393 
    373 <dt> 
     394 
     395<dt> 
     396<a name="whatversion"> 
    374397What version(s) of Swish-e does this license apply to? 
     398</a> 
    375399</dt> 
    376400 
    …… 
    379403</dd> 
    380404 
    381 <dt>I'm confused. Are you saying that "we are GPL, but unlike normal GPL, we don't force 
     405 
     406<dt> 
     407<a name="confused"> 
     408I'm confused. Are you saying that "we are GPL, but unlike normal GPL, we don't force 
    382409you into GPL for using the code"? 
     410</a> 
    383411</dt> 
    384412 
    …… 
    390418</dd> 
    391419 
     420 
     421<dt> 
     422<a name="free"> 
     423You mean I can use Swish-e in my project without obligation? 
     424</a> 
     425</dt> 
     426<dd> 
     427<p> 
     428Well, not exactly.  You have to provide source code for the actual 
     429    version you use (you may point to swish-e.org if you use an 
     430    unmodified version of the software and state the version). 
     431</p> 
     432<p>In addition to that legal requirement, there are some <b>strong 
     433recommendations</b> that aren't legally required. 
     434You 
     435    should make it clear to your users that you are using Swish-e in 
     436    your product by listing Swish-e in your documentation and, if you 
     437    have a web site, with an easy to find link on your web site. 
     438    (Consider using the <a href="/graphics/">Swish-e logo</a>). 
     439    You must feel guilt if you 
     440    add features or bug fixes to the software and do not inform other 
     441    users of swish-e via the Swish-e discussion list, and you should 
     442    think about buying the developers a beer.  Or two.  Or until they 
     443    say 'stop'. 
     444</p> 
     445 
     446</dd> 
     447 
     448 
    392449</dl> 
    393450