License covering fex files

Question

License covering fex files

stoupa-cz opened this issue 11 years ago · 9 comments

Hi all,

I would like to ask you what is the license which covers fex files in this repo. I would like to use OLinuXino A10S fex file in a recipe for meta-allwinner OpenEmbedded layer.
Thanks,

Stoupa

Answer 1 · 2013-10-23T21:05:41.000Z

interesting question.... I don't know... I've always considered "public domain"... but maybe a CC fits better than something like MIT

Answer 2 · 2013-10-23T21:09:30.000Z

On 10/23/13 19:39, Tomas Novotny wrote:

Hi all,

I would like to ask you what is the license which covers fex files in this repo. I would like to use OLinuXino A10S fex file in a recipe for meta-allwinner OpenEmbedded layer.
I think the readme states GPL but if not, we should add that ;)
Thanks,

Stoupa

Reply to this email directly or view it on GitHub:
#16

Answer 3 · 2013-10-23T21:12:24.000Z

problem is these start as deserialized copies of files distributed by the vendor, which come from a "do whatever you like" template from Allwinner SDK

Answer 4 · 2013-10-23T21:17:37.000Z

On 10/23/13 23:12, Alejandro Mery wrote:

problem is these start as deserialized copies of files distributed by the vendor, which come from a "do whatever you like" template from Allwinner SDK
Oh, you gave this far more thought then I did, excellent point, so

public domain then probably.

Reply to this email directly or view it on GitHub:
#16 (comment)

Answer 5 · 2013-10-24T08:31:32.000Z

Thanks for the quick answer. So I will label it as public domain. (BTW it will be still linked with that git repository, files won't be directly copied.)

Answer 6 · 2013-10-24T14:23:55.000Z

Tomas Novotny notifications@github.com writes:

Thanks for the quick answer. So I will label it as public domain. (BTW
it will be still linked with that git repository, files won't be
directly copied.)

please never use "public domain"
there are countries where the legal status is at least unclear in that
case
use some explicit license statement

Answer 7 · 2013-10-24T14:25:33.000Z

that's why I mentioned CC or MIT

Answer 8 · 2013-10-24T14:44:15.000Z

I don't know other consequences, but CC0 would be ok?

Answer 9 · 2013-10-24T16:29:30.000Z

Tomas Novotny notifications@github.com writes:

I don't know other consequences, but CC0 would be ok?

http://www.gnu.org/licenses/license-list.html#OtherLicenses
"
CC0 is a public domain dedication from Creative Commons. A work released
under CC0 is dedicated to the public domain to the fullest extent
permitted by law. If that is not possible for any reason, CC0 also
provides a lax, permissive license as a fallback. Both public domain
works and the lax license provided by CC0 are compatible with the GNU
GPL.

If you want to release your work to the public domain, we recommend you
use CC0."