Skip to content

Adding "LICENSE" file#34

Merged
retostauffer merged 2 commits into
mainfrom
license
May 16, 2026
Merged

Adding "LICENSE" file#34
retostauffer merged 2 commits into
mainfrom
license

Conversation

@retostauffer

Copy link
Copy Markdown
Contributor

Good evening @freezenik and @zeileis

referring to issue #33 : shall might add a LICENSE file to our git repository for those not checking the DESCRIPTION file. The best suggestion I found is to add both licenses with a short header that this software is double-licensed (see merge request), though I have little experience wit this so far. @zeileis what would be your approach?

In addition to the DESCRIPTION file and (potentially) the LICENSE file one can add licenses to a github project (not sure if we nee/want this either).

@zeileis

zeileis commented May 15, 2026

Copy link
Copy Markdown
Member

For now I would just put a GPL-3 file into the Git repository. This is what most users will know/expect. And those who want to use the GPL-2 license can still do so - based on the DESCRIPTION file.

And when the package has been released on CRAN, both licenses will be nicely listed/linked as well. (At that point we could also remove the Git license file again.)

@retostauffer

Copy link
Copy Markdown
Contributor Author

@zeileis thanks, I have removed GPL-2 and the header from the LICENSE file.

@retostauffer retostauffer merged commit deb5b38 into main May 16, 2026
1 check passed
@retostauffer retostauffer deleted the license branch May 16, 2026 05:17
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.

2 participants