Repository navigation
Conversation
|
To me, the "legal content" of the license is not changed, so that should be fine. Others have to check that the citation style/authors etc is correct, but from my side this is good. |
s-poll
left a comment
There was a problem hiding this comment.
I believe that, from a legal point of view, the PR is a change to the licence. It is these legal subtleties that could prove problematic. IMO, it might important here not to change the licence of CLM (CTSM). It might be possible to introduce a separate licence by using two licences, as it is also used at different repos. As having only a superficial understanding of licences can be dangerous, I would suggest that we ask the legal department to clarify this. There is certainly somebody at JSC/FZJ.
There was a problem hiding this comment.
It is these legal subtleties that could prove problematic. IMO, it might important here not to change the licence of CLM (CTSM).
There should be no legal problems since we're not customizing our LICENSE and simply adhere to a standard BSD-3 LICENSE file (links in my 1st post). The original CTSM LICENSE is based from GitHub's BSD-3 license template; what I did is to replace the text with more authoritative source and clearly specify that it's a BSD-3-Clause LICENSE.
Current
LICENSEfile is based from GitHub's BSD-3 license template. It would be better to use aLICENSEtext from a more authoritative source: https://opensource.org/license/BSD-3-Clause. Other references:This PR also fixes #134.