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 covering fex files #16

Closed
stoupa-cz opened this issue Oct 23, 2013 · 9 comments
Closed

License covering fex files #16

stoupa-cz opened this issue Oct 23, 2013 · 9 comments

Comments

@stoupa-cz
Copy link

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

@amery
Copy link
Member

amery commented Oct 23, 2013

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

@oliv3r
Copy link
Member

oliv3r commented Oct 23, 2013

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

@amery
Copy link
Member

amery commented Oct 23, 2013

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

@oliv3r
Copy link
Member

oliv3r commented Oct 23, 2013

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)

@stoupa-cz
Copy link
Author

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

@karme
Copy link

karme commented Oct 24, 2013

Tomas Novotny [email protected] 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

@amery
Copy link
Member

amery commented Oct 24, 2013

that's why I mentioned CC or MIT

@stoupa-cz stoupa-cz reopened this Oct 24, 2013
@stoupa-cz
Copy link
Author

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

@karme
Copy link

karme commented Oct 24, 2013

Tomas Novotny [email protected] 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."

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

4 participants