A workshop for scientific computing in Python

Re:A workshop for scientific computing in Python by mattip on Sunday December 17, 2017 @01:12AM (#15944458)

The repo is missing a LICENSE file, and the links to the data should also specify their redistribution policy / license. Why is this not standard practice when creating a repo these days?

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by BucketSort on Sunday December 17, 2017 @12:55PM (#15946784)

I did not expect such a response to my post. Thank you for making the issue, and I updated it with a MIT licence.

In my defense, this is a repo I cobbled together on the side for my AI group. I did not expect it to get a lot of attention outside the group. Also, the code I've provided is more for educational purposes. I didn't really see people using the code in other open source projects. In respect to the data, I provided links to the public sources.

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by BrandoElFollito on Sunday December 17, 2017 @02:07AM (#15944611)

Because this is not a requirement : https://choosealicense.com/no-license/

Sure, it simplifies things for those who want to have a closer look.

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by cdancette on Sunday December 17, 2017 @05:13AM (#15945118)

No licence means that you can't even use the software. This seems very restrictive for a GitHub project

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by BrandoElFollito on Sunday December 17, 2017 @07:06AM (#15945424)

Have a look at the article I linked, the case of places such as GitHub is explained (TL;DR: the licence is derived from the TOS)

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by IanCal on Sunday December 17, 2017 @08:48AM (#15945748)

The article says you can view and fork the code, but it doesn't mean you can use it. It's very restrictive.

> Although a code host such as GitHub may allow you to view and fork the code, this does not imply that you are permitted to use, modify, or share the software for any purpose.

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by BrandoElFollito on Sunday December 17, 2017 @02:44PM (#15947274)

I stand corrected. Thanks for reading the TOS in detail.

Indeed, GitHub let's you fork but then you cannot do anything else. My understanding now is that forking makes no sense when there is no license.

[ Parent | on HN ]

Re:A workshop for scientific computing in Python by brianzelip on Sunday December 17, 2017 @09:17AM (#15945815)

it's been updated w/ MIT

[ Parent | on HN ]