-
Notifications
You must be signed in to change notification settings - Fork 18
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
Concerns regarding license of various homalg packages #467
Comments
Background information from my side: PackageJanitor adds |
I think there is no way to avoid that someone looks over the manuals of each of these packages (or at least runs a simple grep for terms like "license" on them) to verify they make no contradictory license claims. Assuming this passes, adding a |
Most of these packages are neither in active development nor use, so they are not handled by |
Not sure if this is the best place to file this, but I didn't want to open identical issues on a ton of repositories... I think most (all) of the packages I am talking about are not shipped with GAP, so this is very non-urgent for me. And perhaps irrelevant because you never intend to ship any of those. But if you ever want to submit them for distribution with GAP, ideally the issues should be addressed before.
Also, I am guessing your PackageJanitor is already checking for
License
fields and files, so perhaps all of this is already covered -- if so, just close the issue!License
field in thePackageInfo.g
file. It would be great if those could be added. The following packages are affected:In fact many of those also have no
LICENSE
/COPYING
/whatsoever file, so perhaps that could be added as well.I also noticed that at least some of them list only GPL2 as license, not "GPL2 or later". E.g. in
AbelianSystems
the only reference I could find to a license is in the title page of the manual, which says:The text was updated successfully, but these errors were encountered: