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

License? #2

Closed
nebrius opened this issue Mar 1, 2016 · 3 comments
Closed

License? #2

nebrius opened this issue Mar 1, 2016 · 3 comments
Assignees

Comments

@nebrius
Copy link

nebrius commented Mar 1, 2016

Before we can integrate this into raspi-io, we'll need to get an open source license in place. It's totally up to you which license you go with, as long as it's MIT compatible (or MIT itself).

If you do decide to go with the MIT license, feel free to borrow the licensing structure from raspi-gpio, which is structurally very similar to this module. Specifically, there is a LICENSE file, the contents of the license are added to the end of the README, and the contents of license are also added as a comment to the top of every source code file, like this.

@sesh-kebab
Copy link
Owner

Sure MIT license works for me. About copying the contents of the license to prepend to each source file; is this definitely necessary?

If it is necessary, can there be a compromise made in terms of having a link to the LICENSE file on a single line text?

@sesh-kebab sesh-kebab self-assigned this Mar 1, 2016
@nebrius
Copy link
Author

nebrius commented Mar 1, 2016

ideally yeah, it would go in every file (and I add it to everyone of my files), but you can leave it out and just drop it in LICENSE and README.md if you prefer.

@sesh-kebab
Copy link
Owner

Committed new LICENSE file and updated existing README.md

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

No branches or pull requests

2 participants