request for clarity of AuthPass's licensing about authpass

[hpoul]

@hwpplayer1 to be honest I didn't think too much about that part. But reading GPLv3.0-only or GPLv3.0-or-later makes me think GPLv3 makes more sense. I have updated the README and (/metadata/linux/app.authpass.AuthPass.metainfo.xml)[https://github.com/authpass/authpass/blob/main/metadata/linux/app.authpass.AuthPass.metainfo.xml].

(I've set up a CLA which all contributors must sign, exactly so I'm able to change the license if GPLv4 is released (or any other).. which seems to be the main point of that "or later" clause..)

Let me know if this clarifies the license issue. thanks for pointing that out.

[tallship]

@hpoul ,

Thank you for your choice in this matter. I believe that since you cannot know what a GPLv4/5/6 might look like, your decision to hold it at GPLv3-only is prudent, and considering the terms in your CLA, you'll be able to freely make a determination later as to whether you feel comfortable bumping the license up a version at a time or not.

Linus himself has been adamant about GPLv2 only, and has stated that he would not license the Linux kernel under GPLv3. His reasons are beyond the scope of this discussion however, and is a matter of public record.

Also, there's basically two constructs as to how contributions are made to copyleft licensed software (permissive cuck licenses too like BSD and MIT) - The contributor assigns copyright to the project, or the contributor assigns a license under their copyright to the project.

Here's the gist of it all for everyone, in a nutshell:

2. License grant

2.1 Copyright license to Us

Subject to the terms and conditions of this Agreement, You hereby grant to Us a worldwide, royalty-free, NON-exclusive, perpetual and irrevocable (except as stated in Section 8.2) license, with the right to transfer an unlimited number of non-exclusive licenses or to grant sublicenses to third parties, under the Copyright covering the Contribution to use the Contribution by all means, including, but not limited to:

• publish the Contribution,
• modify the Contribution,
• prepare derivative works based upon or containing the Contribution and/or to combine the Contribution with other Materials,
• reproduce the Contribution in original or modified form,
• distribute, to make the Contribution available to the public, display and publicly perform the Contribution in original or modified form.

Ramifications:

• Unlike many CLAs designed to monetize a corporation, whereby the contributor must Assign Copyright to the project, this one requires the contributor to assign a license to the project of their Copyright.
• If you assign your copyright - you no longer own the intellectual property
• If you assign a license to the project, you still own the extent of the intellectual property that you contributed, are free to contribute that code or prose elsewhere, etc.
• In this case, the contributor assigns a non-exclusive license, meaning that the contributor can license others to use the code they authored and contributed.
• Also note that since you've licensed the use of your (the contributor's) intellectual property, without any expiry (you've assigned the license in perpetuity), you, as the contributor may NOT ever assign your copyright to someone else (Not that you would want to, but some projects require this, and you cannot take away the license you've granted to AuthPass) without incumbering whomever you assign your copyright to, by requiring them to honor this previous license to AuthPass.

IMNSO, this is the most ethical form of CLA - beware of other projects who want you to assign your copyright (ownership of intellectual property that you've created).

Again, thank you for taking the track of copyright licensing rather than that of copyright assignment. It sounds like a subtle distinction, but it is indeed not so subtle.

All the best!

⛵

.