From 82365dd68a57383d892243328a1bc5141e351c63 Mon Sep 17 00:00:00 2001 From: Alexander W Dehnert Date: Mon, 26 Jun 2017 20:46:40 -0400 Subject: [PATCH 1/1] add MIT vs. BSD reason --- projects/collaboration.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/projects/collaboration.mdwn b/projects/collaboration.mdwn index 3f9f61d..1f3ad8f 100644 --- a/projects/collaboration.mdwn +++ b/projects/collaboration.mdwn @@ -27,6 +27,8 @@ Since projects tend to vary as to GPLv2, GPLv2+ ("version 2 or, at your option, There are other licenses, most notably including the BSD license, which is similar to the MIT license, and the AGPLv3, 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. +For a permissive license, MIT and BSD are basically equivalent ([MIT TLO](http://tlo.mit.edu/community/software) recommends BSD online, but in person indicates that they don't differentiate). We recommend MIT over BSD just because much of Athena already uses it, [MIT appears substantially more popular](https://github.com/blog/1964-license-usage-on-github-com), and [Github recommends it](https://choosealicense.com/). + 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 Software Guidelines](http://www.debian.org/social_contract#guidelines) and an [FAQ for it](http://people.debian.org/~bap/dfsg-faq.html). -- 2.44.0