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

Document what "check" really means #57

Open
Nemo157 opened this issue Apr 29, 2019 · 2 comments
Open

Document what "check" really means #57

Nemo157 opened this issue Apr 29, 2019 · 2 comments
Assignees

Comments

@Nemo157
Copy link
Owner

Nemo157 commented Apr 29, 2019

It's not documented anywhere what a pass/fail for checking compatibility really means. I made a short comment here about it, but something like this should be moved into the readme and help text.

@Nemo157 Nemo157 mentioned this issue Apr 29, 2019
@Nemo157 Nemo157 self-assigned this Apr 29, 2019
@rhn
Copy link
Contributor

rhn commented May 6, 2019

Continuing the discussion from the referenced PR, to developers anything distributable, it's rather common to have to comply with additional terms, e. g. the attribution requirement in binary releases.

It would be useful to give the user a summary of what exactly those additional burdens are. That in turn could lay the groundwork for GPL compliance requirements.

@danieleades
Copy link

is there a way i can use this tool to check compliance with a non-standard commercial license? Say by providing a generic 'commercial' tag or by specifying a compatibility matrix in a config file.

In a perfect world this would need to include any commercial distribution restrictions as well (say by industry, by application, or by geography)

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

3 participants