link to licenses

[wiki.git] / projects / collaboration.mdwn

diff --git a/projects/collaboration.mdwn b/projects/collaboration.mdwn
index 5ed0c9b552a52fce6b6cb2ee123c90eb3a1c07bd..3f9f61d48e8af94330b5a584d9c4723f4be57a80 100644 (file)
--- a/projects/collaboration.mdwn
+++ b/projects/collaboration.mdwn
@@ -4,10 +4,10 @@ SIPB projects should generally be free software with open collaboration, that is
 
 For software and source code, the [[SIPB project licensing recommendation|doc/code-licensing]] advises you to choose one of the following two licenses:
 
 
 For software and source code, the [[SIPB project licensing recommendation|doc/code-licensing]] advises you to choose one of the following two licenses:
 

-* the <a>MIT license</a>, also known as the "Expat" or "X11" license. This is a short, permissive license that allows code to be distributed and reused in most forms, without placing redistribution requirements on the user or distributor.
+* the [MIT license](https://opensource.org/licenses/MIT), also known as the "Expat" or "X11" license. This is a short, permissive license that allows code to be distributed and reused in most forms, without placing redistribution requirements on the user or distributor.

 
   The MIT license is often seen in smaller works, although most of the X Window System and other Project Athena works (including Debathena) use this license.
 
   The MIT license is often seen in smaller works, although most of the X Window System and other Project Athena works (including Debathena) use this license.

-* the <a>GNU GPLv2+</a>. This is a longer "copyleft" license that ensures that anyone who redistributes your work must provide access to source code, and anyone who reuses your work must license the resulting work under the GPL (or a compatible license).
+* the [GNU GPLv2+](https://opensource.org/licenses/gpl-license). This is a longer "copyleft" license that ensures that anyone who redistributes your work must provide access to source code, and anyone who reuses your work must license the resulting work under the GPL (or a compatible license).

 
   Most large free software projects, including the Linux kernel, the GNU userland, and Firefox, as well as scripts.mit.edu and Invirt (XVM), use the GPL.
 
 
   Most large free software projects, including the Linux kernel, the GNU userland, and Firefox, as well as scripts.mit.edu and Invirt (XVM), use the GPL.
 


@@ -25,7 +25,7 @@ If you're also distributing a Debian package of your software, see
 
 Since projects tend to vary as to GPLv2, GPLv2+ ("version 2 or, at your option, any later version"), or GPLv3/3+, we currently recommend GPLv2+ for compatibility.
 
 
 Since projects tend to vary as to GPLv2, GPLv2+ ("version 2 or, at your option, any later version"), or GPLv3/3+, we currently recommend GPLv2+ for compatibility.
 

-There are other licenses, most notably including the <a>BSD license</a>, which is similar to the MIT license, and the <a>AGPLv3</a>, which provides slightly more restrictions on reusers so that hosting a web application effectively counts as distribution. Code available under the GPLv3 can be used in an AGPLv3 application, but code only available under the AGPL cannot be used in a GPL application. Again, we recommend the GPL for compatiibility.
+There are other licenses, most notably including the <a>BSD license</a>, which is similar to the MIT license, and the <a>AGPLv3</a>, which provides slightly more restrictions on reusers so that hosting a web application effectively counts as distribution. Code available under the GPLv3 can be used in an AGPLv3 application, but code only available under the AGPL cannot be used in a GPL application. Again, we recommend the GPL for compatibility.

 
 We anticipate that most SIPB projects' needs are best served by selecting either the MIT license or the GPL and moving on. However, if you are interested in this subject, you can learn more at [GNU's licensing website](http://www.gnu.org/licenses/) and [the Open Source Initiative's](http://www.opensource.org/licenses/). You can also read more about free and open source
 software on GNU and OSI's websites; see also the [Debian Free
 
 We anticipate that most SIPB projects' needs are best served by selecting either the MIT license or the GPL and moving on. However, if you are interested in this subject, you can learn more at [GNU's licensing website](http://www.gnu.org/licenses/) and [the Open Source Initiative's](http://www.opensource.org/licenses/). You can also read more about free and open source
 software on GNU and OSI's websites; see also the [Debian Free