-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add a license #13
Comments
Consider it public domain, at least what concerns me. @d1manson what do you think? |
That's fine with me, yeah. Probably should add a statement of that then (in the readme at least). |
Fixed in afa5f3a |
Thanks, but "public domain" is not a great software license. I really
|
Yeah, lawyers, a very strange breed. I'm not really excited about worrying about licensing too much. For simplicity I suppose the best would be to go with the same license that numpy uses then. |
What do you think about this suggestion? It's the same 3-clause BSD-license as for numpy, the only modification is that I scratched numpy-groupies as an organization in clause 3. I don't really see us two lone developers as some kind of organization, so mentioning it there sounded somewhat strange. If that's already messed around too much with the license, I'd be fine throwing it in again.
|
I would either include the third clause exactly or ditch it entirely -- the later is known as 2 clause BSD |
Given the text there https://en.wikipedia.org/wiki/BSD_licenses#2-clause , I'd like to scratch the last paragraph about the views contained in documentation and whatever, which again mentions any form of organization, and seems superfluous for us anyways. Not sure why this paragraph got added explicitly for the 2-clause license, but I guess just skipping it would still make this count as regular BSD 2-clause license:
@d1manson , your thoughts? Edit: Oops, just saw your link, yeah, that makes it clear that we don't need this last paragraph, thanks. |
I'm fine with whatever you decide |
Ok, then let's pick the BSD 2-clause license as suggested by Stephan. |
thanks! |
The lack of an open source license stops me from using, contributing to or even seriously considering this package.
I would suggest 3-clause BSD, which is standard in the scientific Python ecosystem (including NumPy, SciPy, pandas, etc.).
The text was updated successfully, but these errors were encountered: