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

License? #264

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions