@@ -48,16 +48,22 @@ conveniences: addition of a README, a gitignore, and a license.
48
48
49
49
> A quick note on licenses:
50
50
>
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.
56
56
>
57
57
> I'm a big proponent of BSD. Jake Vanderplas, Director of Research at
58
58
> the University of Washington's eScience Institute, has a fantastic
59
59
> [ blog post] ( http://www.astrobetter.com/blog/2014/03/10/the-whys-and-hows-of-licensing-scientific-code/ )
60
60
> 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.
61
67
62
68
Follow [ GitHub's
63
69
instructions] ( https://help.github.com/articles/creating-a-new-repository )
0 commit comments