-
Notifications
You must be signed in to change notification settings - Fork 13
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
Choose a license #4
Comments
There are few other related decisions to make here...
|
We discussed this at the dev meeting last Monday. The general consensus was to allow different examples to have different licenses. Therefore, we will encourage each example to advertise a copyright and license like so: copyright = "Copyright (c) 2016 Applied Brain Research Inc."
license = "See https://github.com/nengo/nengo/blob/master/LICENSE.rst" This has precedent in Python; if you open an interpreter and type in Doing it like this is nice because it is obvious if you open up the file in the GUI, and is still accessible if you don't look at the file and only import it (e.g., There was some discussion about the license format. We decided that we a URL is sufficiently short (copying the whole license text in the file would be a lot of clutter) yet explicit (saying "see LICENSE.rst" or "Licensed with Nengo licence" could be misinterpreted). |
Interestingly, Python allows to use |
So does that mean that whoever is submitting the example can decide on whatever license they want? |
Yes, that's right. |
What license should the htbab tutorials be given then? |
Copyright should be authors, and license maybe standard nengo? Not sure about the latter.
…On May 10, 2017 12:29:52 AM EDT, Sean Aubin ***@***.***> wrote:
What license should the htbab tutorials be given then?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on
GitHub<#4 (comment)>,
or mute the
thread<https://github.com/notifications/unsubscribe-auth/AB5JU45s9bL5SjYRj-2l3kycixX1_v_0ks5r4T1AgaJpZM4KiuN5>.
|
No description provided.
The text was updated successfully, but these errors were encountered: