Skip to content
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

Open
Seanny123 opened this issue Oct 27, 2016 · 7 comments
Open

Choose a license #4

Seanny123 opened this issue Oct 27, 2016 · 7 comments

Comments

@Seanny123
Copy link
Collaborator

No description provided.

@tbekolay
Copy link
Member

There are few other related decisions to make here...

  1. Do all the examples have to be covered by the same license? Doing so makes things simpler for users, but might constrain the examples we can put in here. Another option would be to have a default license, but still allow some to deviate.
  2. If same license, do we want copyright assignments or license agreements from contributors? In Nengo we do copyright assignments, but that might not be appropriate here.

@tbekolay
Copy link
Member

tbekolay commented Nov 3, 2016

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 copyright or license you'll get something like the above.

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., from nengo_examples import some_example; print(some_example.license)).

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).

@jgosmann
Copy link

jgosmann commented Nov 3, 2016

Interestingly, Python allows to use print(copyright) as string as well as function copyright(). Not sure if we want to reproduce this behavior, but thought I mention it.

@Seanny123
Copy link
Collaborator Author

So does that mean that whoever is submitting the example can decide on whatever license they want?

@tbekolay
Copy link
Member

tbekolay commented Nov 9, 2016

So does that mean that whoever is submitting the example can decide on whatever license they want?

Yes, that's right.

@Seanny123
Copy link
Collaborator Author

What license should the htbab tutorials be given then?

@celiasmith
Copy link

celiasmith commented May 10, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants