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? #253

Closed
jacksonporter opened this issue Sep 25, 2022 · 6 comments
Closed

License? #253

jacksonporter opened this issue Sep 25, 2022 · 6 comments

Comments

@jacksonporter
Copy link

Hi! Thanks so much for your contribution!

I was wondering if you can add a LICENSE to this project? This allows for open-source use of your code (right now nothing is set, so the lines are gray).

Suggested LICENSE - based on MIT

Thanks!

@ladar
Copy link
Member

ladar commented Dec 8, 2022

I've thought about this in the past, and it's a rather complicated issue if you really understand things. That's because this repo is actually working with and utilizing so many hypervisor platforms, operating system distros, and other support tools on both the build robots, and inside the guest images, and all of those use different licenses, running the gamut from OSI approved, to commercial. And I felt it would be improper to publish a license file, like you suggest which might lead people to think everything this repo touches will also carries the MIT license.

I think wrote a short blurb to this effectr years ago, and stated that all the scripts and configs I've created, and stored int his repo are placed in the public domain.

@jacksonporter
Copy link
Author

Indeed it is complex and completely understand your point as well. Thanks for the additional context!

@jacksonporter jacksonporter closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2022
@ladar
Copy link
Member

ladar commented Dec 8, 2022

Oh I almost forgot. What license applies to the box images files themselves!

@ladar
Copy link
Member

ladar commented Dec 8, 2022

See #19.

@ladar
Copy link
Member

ladar commented Dec 8, 2022

If you feel obliged, it might worth adding a little disclaimer to effect of what I said above to the bottom of the README file.

@ladar
Copy link
Member

ladar commented Dec 8, 2022

I haven't done it, because it would need to have all the usual disclaimers and such.

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

No branches or pull requests

2 participants