-
Notifications
You must be signed in to change notification settings - Fork 9
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
Please include a license file in the sources #26
Comments
Sure, I will have a look / BTW the way I will do some clean-up |
While GPL is not one of the licenses that requires the license text to be included, a license file would still be helpful. Beyond this, the GPL is normally applied via a license notice, which GNU recommends putting in the header of each source file. Even if the notice were only in the README, it would be good to include it, and the notice would help clarify whether the intended license is You might also consider upgrading the deprecated SPDX identifier Thanks for having a look at this! |
In 95b4dea I switched lic to AGPLv3+, added LIC file, fixed the SPDX tags (to AGPL-3.0-or-later) and released tag 20230321 on pypi --> https://pypi.org/project/linuxdoc/20230321/ @sanjayankur31 I hope I have thought of everything, if I have forgotten something, please let me know. Otherwise close the ticket / Thank you! 👍 |
That looks great! Thanks for the quick update @return42 . I'm also generating man pages for the different Here's the command in the current spec: https://pagure.io/python-linuxdoc/blob/main/f/python-linuxdoc.spec#_52 |
OK, thanks for your feedback / I'm going to close this issue. About man pages: IMO we should add man pages for the entry points (commands) here in the project. linuxdoc/linuxdoc/__pkginfo__.py Lines 115 to 123 in fd2f8ef
Would you like to open a new issue (or PR if you have) / thanks! |
Hello!
Similar to return42/fspath#1, could we please have a license file added here too?
Thanks very much,
The text was updated successfully, but these errors were encountered: