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

Clarify limits of licensing w.r.t generated output of tools #33

Closed
amykyta3 opened this issue Aug 24, 2023 · 0 comments
Closed

Clarify limits of licensing w.r.t generated output of tools #33

amykyta3 opened this issue Aug 24, 2023 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@amykyta3
Copy link
Member

in https://github.com/orgs/SystemRDL/discussions/184, @CodeStillBroken requested:

Can your team make a clear and unambiguous statement on the PeakRDL website ( e.g. in the licensing section ) clarifying what license, if any, applies to the output generated by running the PeakRDL tools covered by GPL v3? My understanding is that the output of the program is not governed by the terms of the program's license. If that is the case, it would be helpful to clearly state that the customer owns all rights to the outputs generated by the PeakRDL tools on your website :)

Add a similar statement to what is described in regblock docs to the general PeakRDL docs.
Will need to clarify that this exemption only covers core PeakRDL components, and 3rd-party plugins may be licensed differently.

Alternatively, consider switching away from GPL and move to the more FOSS hardware-friendly Apache license, as it is less likely to spook the lawyers.

@amykyta3 amykyta3 self-assigned this Aug 24, 2023
@amykyta3 amykyta3 added the documentation Improvements or additions to documentation label Aug 24, 2023
amykyta3 added a commit that referenced this issue Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant