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

Closed
Enmk opened this issue Feb 14, 2023 · 3 comments
Closed

License? #264

Enmk opened this issue Feb 14, 2023 · 3 comments

Comments

@Enmk
Copy link

Enmk commented Feb 14, 2023

Can't find license information anywhere on this repo, could you please make it explicit?
Is it MIT? Is it GPL? Or is it Apache 2.0 ?

@ladar
Copy link
Member

ladar commented Feb 14, 2023

See #253 ... as far as I'm concerned the scripts used by this repo can be considered part of the public domain. However the software/tools and other resources they rely upon are all governed by their own license.

@ladar ladar closed this as completed Feb 14, 2023
@Enmk
Copy link
Author

Enmk commented Feb 16, 2023

I get that there are many tools involved in building boxes, but what is the license of the code in this repo itself? All the .json and script-files

If you consider that to be a public domain, why not just mark it as such in a License file or why not just use MIT license as the simplest and shortest one (easiest to understand) ?

@ladar
Copy link
Member

ladar commented Feb 16, 2023

@Enmk because including a LICENSE file in the repo might mislead some people to think the license also applies to the to box files we generate, and/or tools we use. That's to say nothing of the software inside the box files.

It's worth noting that I actually have no idea what license, if any, should apply to the box files themselves.

As I've said, I consider the scripts/configs I've created for the Robox project to be in the public domain. So if you want to fork and reuse this code you are welcome to do so.

In a perfect world, I'd add a section to the README stating precisely this, along with a notice/explanation to make clear what is covered, and what is not. And that specifically, the tools/boxes/distros all have their own licenses. That's to say nothing of the software installed on the guest itself. But it's a low priority, and I haven't had the time. And in lieu of a proper message, it's better to do nothing.

@Enmk if you're a good writer, I would welcome help with this. We really need help expanding our documentation, by expanding the README and/or adding more to info to the roboxes.org website and/or GitHub wiki pages. Specifically we need documentation that explains how to use the various scripts and configs to setup a build environment and then build boxes. How someone could go about adding a new distro or platform to our release pipeline. And how to actually consume the box themselves.

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