Visitar URL original
Separate the patent clause from the license into its own file by namurphy · Pull Request #1686 · PlasmaPy/PlasmaPy · GitHub
Skip to content

Separate the patent clause from the license into its own file - #1686

Merged
namurphy merged 9 commits into
PlasmaPy:mainfrom
namurphy:split-license-and-patent-clause
Aug 23, 2022
Merged

namurphy merged 9 commits into
PlasmaPy:mainfrom
namurphy:split-license-and-patent-clause

Conversation

@namurphy

Copy link
Copy Markdown
Member

Way back in the antiquity of PlasmaPy (#114), we added a patent grant to our current license that came from the OSI-approved BSD+Patent license. The BSD+Patent license is the BSD 2-clause license plus language that protects against software patents (which we adopted because there are many commercial applications to plasma science). One complication was that we already had the BSD 3-clause license, so we ended up going with the BSD 3-clause license + patent instead of the canonical BSD 2-clause license + patent, and the BSD-3-clause-patent license doesn't show up on lists.

This pull request splits off the patent grant into its own file. PlasmaPy will effectively be under the BSD 3-clause license again, but the patent grant will still be in effect.

One additional thing to note is that the BSD+Patent, BSD 2-clause, and BSD 3-clause licenses all say that the package can be redistributed and/or modified so long as redistributions retain "the above copyright notice, this list of conditions, and the following disclaimer" where the list refers to the enumerated list and the disclaimer is the final paragraph of each of the licenses that talks about no implied warranties. In the BSD+Patent license, the patent grant is not explicitly listed as one of the things that is required to be included in redistributed versions of the code.

@namurphy namurphy added status: needs discussion Issues & PRs that need to be discussed at a community meeting or by the Coordinating Committee proposal Proposals that need to be decided upon before implementation labels Aug 22, 2022
@codecov

codecov Bot commented Aug 22, 2022 •

Copy link
Copy Markdown

Codecov Report

Merging #1686 (87b37b0) into main (0754976) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1686   +/-   ##
=======================================
  Coverage   97.23%   97.23%           
=======================================
  Files          85       85           
  Lines        8020     8020           
=======================================
  Hits         7798     7798           
  Misses        222      222           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@StanczakDominik StanczakDominik left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks okay to me, though of course my only law experience comes from playing Ace Attorney (so if you need someone to shout OBJECTION! really loudly...) and this is not even a murder case!

My only worry here is that now the license "key" or "enum value" in setup.cfg and citation, sorry, CITATION!cff, describes our license as BSD-3-clause, but that's not the extent of the license because of the separated out patent clause. So the license files are not interchangeable or uniquely identified by the "key".

Does that matter? No idea, just pointing out a possible issue.

@StanczakDominik
StanczakDominik removed their request for review August 23, 2022 19:03
@namurphy
namurphy merged commit 110c862 into PlasmaPy:main Aug 23, 2022
@namurphy
namurphy deleted the split-license-and-patent-clause branch August 23, 2022 20:26
namurphy added a commit to namurphy/PlasmaPy that referenced this pull request Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proposal Proposals that need to be decided upon before implementation status: needs discussion Issues & PRs that need to be discussed at a community meeting or by the Coordinating Committee

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants