Open Nemo157 opened 5 years ago
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.
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)
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.