-
-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change LICENSE from GPL v3 to AGPL v3 #150
Conversation
I approve Will this change affect also the original Sunshine repo/source? |
I approve |
No; however if everyone on this list agrees, it already encompasses all the original contributors so the change could be made to Loki's repo as well. Also, this will only affect future releases, anything already released would remain under GPL v3. |
I approve ! |
Btw which proprietary versions are we talking about? |
I approve! |
This is the one that sparked this request: https://www.oneplay.in/ Someone has speculated to me that this one is also using Sunshine: https://shrine.app/ Then of course, there is Maximum settings: https://maximumsettings.com/ |
I approve. |
I approve! |
I approve |
I approve! |
I approve |
1 similar comment
I approve |
I approve. |
How dare they profit off our work and give nothing back? Parasites they be. I approve! |
I approve! You have the OK from me! |
I approve! |
2 similar comments
I approve! |
I approve! |
While I approve, we must also look into how this affects linking against GPL libraries and other compatibility issues we may encounter down the road; Looks like linking a GPL thing against AGPL library doesn't work, though otherwise it should be fine - So full steam ahead |
I approve |
3 similar comments
I approve |
I approve |
I approve |
I approve 👍 |
I approve! |
I approve |
I approve. |
@KiralyCraft where did you find that linking GPL in an AGPL project isn't allowed? I've found it to be the opposite. I am not a license/legal expert though. |
May have gotten them reversed, although I did remember there was something to keep in mind regarding GPL; Oh well, looks like it's all good then, sorry |
a13ea6d
to
18cb5a0
Compare
18cb5a0
to
8b42c36
Compare
@loki-47-6F-64 has last been seen at https://github.com/Sude-/lgogdownloader/pull/224 |
@PapyKahan Bonjour! I hope this message gets to you! |
I have emailed @notentered once again, now using their personal email. |
@Doomsdayrs thanks for your efforts in trying to reach the remaining contributors... much appreciated! |
Trying my best, Freedom is a verb and I must act! I have emailed @jorys-paulin with their personal email now. |
If papy does not respond from ping, I will dig up their email too. |
This PR is stale because it has been open for 90 days with no activity. Comment or remove the stale label, otherwise this will be closed in 10 days. |
Hi everyone, I approve too. Sorry for being so far away since a long time. |
OMG. I've been not following for quite a while. Hope this is still ongoing and please excuse me for the quite laaaaate response. |
Is the last traceable person They have a twitter here, if anyone still has twitter they can try contacting them. Their website is down since I last checked it I sent them a message on crowdin I'll later start digging their email out of git commits. |
@Doomsdayrs That user jorys-paulin is one of the import helpers/moderators on the moonlight discord server. I'll forward this issue to the channel. |
Oh that makes it much easier! |
Finally, I'll contact the FSF on the situation with @loki-47-6F-64 |
@jorys-paulin does not approve, and I'm waiting on a reply from the fsf |
@Doomsdayrs any word from FSF? |
What's your email, I'll forward you their response. Excerpt:
|
@Doomsdayrs are you on our LizardByte discord server? |
I used this as a tip:
As a result I found not only jorys-paulin but also loki-47-6F-64 on that Discord server. I won't public links to their profiles here, but will DM them to @ReenigneArcher on Discord and @Doomsdayrs on Mastodon instead. |
I apologize, but this is already known. Lokis discord account is dead, and jorys is hostile to the license change |
Whops. Didn't mean to clutter your DMs, guys. Sorry.
That's sad to know. Wish you best of luck anyway. |
While I agree with changing the license, I'd say that the way @Doomsdayrs contacts the contributors is questionable, rather than stating others are hostile to license change. |
I admit I was quite aggressive in finding the contributors, and I can see how it was unwanted by some. While some contributors were appreciative, as seen in this comment, I understand how others may not appreciate this approach. It wasn't my intention to come off as pushy or invasive, and it was my own frustration that made me judge Jorys position as hostile, which was incorrect. Ultimately, my intent was solely to facilitate a smooth license transition for Sunshine and to unify all contributors in this decision. I genuinely meant no harm and I apologize for any unease I may have caused. |
Thanks everyone for your efforts to get this license changed. Since this has been open for 1.5 years now and we were unable to get complete agreement, I will now be closing this. We came very close to a complete consensus, only missing 2 out of 80 total contributors. If either of the remaining two developers have a change of heart, please let me know and I will resume this activity. P.S. There could potentially be a path forward with dual licensing, but that is not desirable path at this time. Maybe in the future we will reconsider. Thank you everyone! |
Description
Some commercial companies are utilizing modified versions of Sunshine without publishing the source code. Using GPL v3 could be argued that it's still distribution even though it's a network asset, as the end user has a high level of control over the virtual machine. Changing to the AGPL v3 license will remove any doubt.
The AGPL V3 license is a strong copyleft license that enforces open source on all components derived from any previous work. It closes the server-side loophole, where the source code isn’t made available if the software isn’t released. AGPL defines a user as anyone who accesses the server-side application if it is public-facing. For applications that reside inside the organization’s network, AGPL does not trigger the release of the source code.
https://snyk.io/learn/agpl-license/
This PR requires approval from previous contributors before being merged. Contributors tagged in this PR, please comment with "I approve" or "I reject"
Approval Tracking List
CPP contributors:
Non CPP contributors:
Contributors with un-merged changes (not in
master
branch yet):In process PRs (not yet merged into any branch):