Skip to content

Commit 1d9ae69

Browse files
committed
Update note on licenses
1 parent 9d22fcd commit 1d9ae69

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

Diff for: 2-working.md

+11-5
Original file line numberDiff line numberDiff line change
@@ -48,16 +48,22 @@ conveniences: addition of a README, a gitignore, and a license.
4848

4949
> A quick note on licenses:
5050
>
51-
> The two most popular free and open source (FOSS) licenses are the
52-
> GNU Public License (GPL) and the BSD 3-clause license. The main
53-
> difference between them is that GPL forces users of your code to
54-
> publish their own code under the GPL itself, while the BSD makes
55-
> no such prescriptions.
51+
> The three most popular free and open source (FOSS) licenses are the
52+
> GNU Public License (GPL), the MIT license, and the BSD 3-clause license.
53+
> The main difference between them is that the GPL requires published
54+
> derivative works to themselves be licensed under
55+
> GPL-compatible licenses, while MIT and BSD make no such prescriptions.
5656
>
5757
> I'm a big proponent of BSD. Jake Vanderplas, Director of Research at
5858
> the University of Washington's eScience Institute, has a fantastic
5959
> [blog post](http://www.astrobetter.com/blog/2014/03/10/the-whys-and-hows-of-licensing-scientific-code/)
6060
> explaining why.
61+
>
62+
> Having said that, as Jake says, what's important is that you license
63+
> your software and use one of the above licenses. Which license you use is
64+
> a personal choice, not a technical one. A good rule of thumb is, when in
65+
> Rome, do as the Romans do: if writing scientific Python, use BSD. If
66+
> writing R packages, use GPL.
6167
6268
Follow [GitHub's
6369
instructions](https://help.github.com/articles/creating-a-new-repository)

0 commit comments

Comments
 (0)