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

append changelog to fulfill the license obligation #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

naonaono
Copy link

@naonaono naonaono commented Mar 9, 2023

Reminding about missing "notices" for modifications on original work (violation of GPL-3.0)

Hello,

[Modification terms and conditions in license] The original work should be honored while the modifications on it should be attached with prominent notices as the license GPL-3.0 dictates. Your project is a forking project from Kr328/ClashForAndroid which adopts GPL-3.0 as its project license.
The modification terms and conditions of GPL-3.0 dictate that:

GPL-3.0:

... The work must carry prominent notices stating that you modified it, and giving a relevant date. ...

Therefore, we think the project is obligated to abide by the modification terms and conditions in GPL-3.0.

[Violation of modification terms and conditions] We run through your history, and it turns out that you have conducted modifications to the source files of original work while didn't provide prominent notices.
You have 7 commits which conduct modifications to the files of original work, all of which are not declared in README.md.
According to the license terms and conditions above, it is regarded as license violation.
Thus, to avoid potential legal risks, I would suggest you carry out prominent notices for the 7 commits.

[Recommended Fix] There are 2 recommended solutions to fulfill the modification related obligation of GPL-3.0:

  1. Git Mechanism.

    • Just put a note in the top directory, something like MODIFICATION.md, or any file but the license text and NOTICES, in order to give people who follow you the most latitude to comply with the license without making a mess,
    • Write "In compliance with the GPL-3.0 license: I declare that this version of the program contains my modifications, which can be seen through the usual "git" mechanism."
  2. Changelog Text.
    Or add changelog for modification to comply with the license.

For your convenience, I created a PR with by picking up modification-related commit messages. It adds a few lines in changelog without touching the codebase. Please be comfortable to check it out.

Full details of the report you could refer to the html file attached.
Hope it helps!

If there is anything wrong in this reminding, I'm sorry for my bothering, and please feel free to close this PR.

Cheers!

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

Successfully merging this pull request may close these issues.

1 participant