License?
nebrius opened this issue · 3 comments
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.
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?
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.
Committed new LICENSE file and updated existing README.md