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 license #117

Closed
aizvorski opened this issue Sep 15, 2022 · 2 comments
Closed

Clarify license #117

aizvorski opened this issue Sep 15, 2022 · 2 comments

Comments

@aizvorski
Copy link

I'd like to confirm whether the whole repository is licensed under LGPL.

There are both "COPYING" and "COPYING.lesser" files, which would seem to suggest some parts are GPL and some LGPL.

A quick search through the F90 files shows all of them have a "MOPAC is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License" and "Copyright (C) 2021, Virginia Polytechnic Institute and State University" header; except for one file getpdb.F90 which has no header (probably omitted by accided).

If the whole repository is LGPL, could we delete the file "COPYING", and add a note in README.md which also says the license as a whole is LGPL?

@godotalgorithm
Copy link
Collaborator

Yes, MOPAC is wholly licensed under LGPL, and I can add a note to the main README to that effect. According to the instructions on the GNU website, both the COPYING (GPL) and COPYING.lesser (LGPL) files should be included in LGPL-licensed software because the LGPL license is an addendum to the GPL license rather than a self-contained legal document.

Thanks for catching the missing header, I'll fix that too.

@godotalgorithm
Copy link
Collaborator

Updates to the main README file should now resolve any license ambiguity.

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

2 participants