Tasmota: what is the license on this code?

Created on 11 Mar 2017  路  8Comments  路  Source: arendst/Tasmota

I may be just overlooking it, but I'm not seeing any license listed for this codebase.

question

Most helpful comment

In many parts of the world "no license" means that technically we aren't allowed
to use it at all. If you mean "no license" to be "do anything you want with this
code", (and looking at the files that do have license text in them, and how the
project is used, this seems like what you mean), please declare the rest of the
code to be under the same license (it looks like your intent is BSD)

Only the one you see at the top of some the files. Other than that there is no license.

All 8 comments

Only the one you see at the top of some the files. Other than that there is no license.

In many parts of the world "no license" means that technically we aren't allowed
to use it at all. If you mean "no license" to be "do anything you want with this
code", (and looking at the files that do have license text in them, and how the
project is used, this seems like what you mean), please declare the rest of the
code to be under the same license (it looks like your intent is BSD)

Only the one you see at the top of some the files. Other than that there is no license.

@davidelang & @arendst I haven't done a full review on all of the libraries referenced by this project, but I believe that since at least some of these libraries are LGPL licensed (e.g. core_esp8266_timer.c), it wouldn't matter if this project were BSD licensed, as the "static linking" rule from the LGPL would apply. I suppose you could distribute unlinked binaries to get around this, but that wouldn't be particularly useful to anyone.

well, arendst only distributes source, so it really doesn't matter (except
possibly for the licenses that are forked, but since they are distributed as
source as well, that complies with any licenses involved)

Yeah, I don't mean to say he's not in compliance, just that since the project statically links to LGPL code, the distribution restrictions of the LGPL would apply to others looking to distribute this software or derivative works even if the overarching project were BSD license.

But my comments distract from your previous point, which I strongly agree with. @arendst if you haven't done so already, I strongly recommend reading https://choosealicense.com/no-license/ (Don't worry, it's a short read). The most pertinent detail from this is that per international copyright law, by explicitly declaring that there is no license, you're declaring that nobody may use your software. Worse yet, if others contribute to this work under similar terms, technically _nobody_ may use this software, as no permission for use of the complete work has been granted to anyone.

I'm working on a different PR today, but if you're willing to declare a license or that you wish to make this code public domain, I'd be happy to submit a PR w/ the various license documents, headers, etc, as well.

Thnx for the license info. Looked at the link supplied by @benjamincburns and now have to decide between the MIT or (L)GPL license. The latter one needs "an" email and mail address. Looking at the arduino esp8266 project files this seems to be the default yoyodine info. Is that enough?

I read it over and decided to go for GPL.

Please add the license info to the readme.md

Was this page helpful?
0 / 5 - 0 ratings

Related issues

abzman picture abzman  路  3Comments

j4k3 picture j4k3  路  3Comments

ximonline picture ximonline  路  3Comments

TylerDurden23 picture TylerDurden23  路  3Comments

luisfpinto picture luisfpinto  路  3Comments