No license information #5
Comments
Closed
|
We have started to add standardized license variables to the plugins. It's now added for those plugins where it was easy to do. |
Freso
added a commit
to Freso/picard-plugins
that referenced
this issue
Feb 10, 2017
Picard itself is licensed under the GPLv2 which means that any plugins written specifically for Picard might be argued to be under GPLv2 themselves due to GPLv2's viral nature, either due to being derived from Picard to some extent, or due to linking to Picard at runtime. To avoid any legal issues (and to make sure we have the rights to distribute and change plugins for the future) the added sentence declares that new plugins to the repository should be under a GPLv2-compatible license (ie., a license "more free" than GPLv2 is also acceptable). Also, be declaring it as "new plugins" the statement is "grandfathering" plugins already in the repository. Ideally these plugins should eventually get sorted out (see also metabrainz#5 ), but this should at least be something we can point new contributors to so we don't make the current license mess worse. :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many plugins in this repository have no information on what license they can be used and redistributed under. Preferably that information should be included in the generated
plugins.json.See also http://tickets.musicbrainz.org/browse/PICARD-326
The text was updated successfully, but these errors were encountered: