[Code scan] Include the GPLv3 companion text for LGPLv3 licensing

Open Beginner friendly
#567 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Start by reviewing the tracked LICENSE file and its references to the GNU GPL. Add the GPLv3 text as COPYING and keep the LGPLv3 text as COPYING.LESSER, or use another conventional layout that preserves both texts in source and release artifacts. Done means downstream users can find both complete license texts.

Written by the indexing model from the issue text.

Description

This issue was found during a Codex global code scan of the repository.

Baseline commit: e3c5b38a99eb7ab778b5d8c68a5ed4ddf6cf91b3

Problem

The repository contains the LGPLv3 text in LICENSE, but the LGPLv3 text incorporates and refers to the GNU GPL. A separate GPLv3 companion text was not present in the tracked files.

Code references:
https://github.com/deepmodeling/dpgui/blob/e3c5b38a99eb7ab778b5d8c68a5ed4ddf6cf91b3/LICENSE#L9-L11
https://github.com/deepmodeling/dpgui/blob/e3c5b38a99eb7ab778b5d8c68a5ed4ddf6cf91b3/LICENSE#L76-L77
https://github.com/deepmodeling/dpgui/blob/e3c5b38a99eb7ab778b5d8c68a5ed4ddf6cf91b3/LICENSE#L91-L92

Impact

This is license hygiene rather than a runtime failure. Downstream redistributors and source package consumers may expect both GPLv3 and LGPLv3 texts to be present when the project is licensed under LGPLv3.

Suggested fix

Add the GPLv3 text as COPYING and keep the LGPLv3 text as COPYING.LESSER, or use another conventional file layout that includes both license texts in source and release artifacts.

Dominant language
Vue
Stars
9
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deepmodeling/dpgui

All issues in deepmodeling/dpgui

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.