Relicensing Sparkle to something more permissive? #12

Closed
opened 2026-04-04 08:10:38 -05:00 by PPPDUD · 7 comments
PPPDUD commented 2026-04-04 08:10:38 -05:00 (Migrated from github.com)

For people who want to fork Sparkle for personal or business use, a strong copyleft license like the GPLv3 could prove quite cumbersome. @e016 @codingisfun2831t @Bubgamer07 What do you think about relicensing to one of the Apache, MIT, or BSD licenses?

For people who want to fork Sparkle for personal or business use, a strong copyleft license like the GPLv3 could prove quite cumbersome. @e016 @codingisfun2831t @Bubgamer07 What do you think about relicensing to one of the Apache, MIT, or BSD licenses?
codingisfun2831t commented 2026-04-04 10:26:27 -05:00 (Migrated from github.com)

Yeah, MIT sounds good. I originally chose GPLv3 as it was the same license as Snap!

Yeah, MIT sounds good. I originally chose GPLv3 as it was the same license as Snap!
PPPDUD commented 2026-04-04 11:14:12 -05:00 (Migrated from github.com)

Yeah, MIT sounds good. I originally chose GPLv3 as it was the same license as Snap!

Hold on, isn't Snap! AGPLv3?

> Yeah, MIT sounds good. I originally chose GPLv3 as it was the same license as Snap! Hold on, isn't Snap! _AGPLv3_?
codingisfun2831t commented 2026-04-04 11:36:36 -05:00 (Migrated from github.com)

Oh right. Still, similar!

Oh right. Still, similar!
PPPDUD commented 2026-04-09 10:11:08 -05:00 (Migrated from github.com)

@e016 @Bubgamer07 Still waiting on your input here...

@e016 @Bubgamer07 Still waiting on your input here...
e016 commented 2026-04-09 10:19:32 -05:00 (Migrated from github.com)

I don't care too much about the license as long as it lets people fork your work without hassle. I usually use a GPL license; although it's up to you!

I don't care too much about the license as long as it lets people fork your work without hassle. I usually use a GPL license; although it's up to you!
PPPDUD commented 2026-04-09 10:22:43 -05:00 (Migrated from github.com)

I don't care too much about the license as long as it lets people fork your work without hassle. I usually use a GPL license; although it's up to you!

That's convenient, actually, because the MIT license is way friendlier to forking than the GPL ever was!

@Bubgamer07 Just waiting on you and we can go through with this.

> I don't care too much about the license as long as it lets people fork your work without hassle. I usually use a GPL license; although it's up to you! That's convenient, actually, because the MIT license is way friendlier to forking than the GPL ever was! @Bubgamer07 Just waiting on you and we can go through with this.
PPPDUD commented 2026-04-09 10:24:02 -05:00 (Migrated from github.com)

Hold on... @Bubgamer07's only contribution is to the API.md page. Let me see if I can rewrite the affected sections to effectively remove their copyright control over that document.

Hold on... @Bubgamer07's only contribution is to the API.md page. Let me see if I can rewrite the affected sections to effectively remove their copyright control over that document.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sparkle-devs/sparkle-old-migration#12
No description provided.