this post was submitted on 18 Oct 2024
93 points (98.9% liked)

Linux

5324 readers
216 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
top 10 comments
sorted by: hot top controversial new old
[–] sabreW4K3@lazysoci.al 49 points 1 month ago (1 children)

They really just tried to get free labour.

[–] CosmicTurtle0@lemmy.dbzer0.com 52 points 1 month ago

They wanted free labor but own the changes.

They could have gotten free labor if they used a standard license like GPL or even MIT.

But nope. They were greedy.

[–] Hamartiogonic@sopuli.xyz 41 points 1 month ago* (last edited 1 month ago)

LOL. Those 3 weeks must have been really exciting at Llama Group. I can only imagine how the conversion went when the engineers tried to explain what FOSS means and the CEO understood none of it.

[–] 1984 21 points 1 month ago (2 children)

I don't even understand why anyone cares about winamp anymore. Or how the company figured people should be happy to work for free on it without it being open source.

[–] babybus@sh.itjust.works 4 points 1 month ago
[–] BeN9o@lemmy.world 1 points 4 weeks ago

I don't understand why anyone cares about winamp being updated, I still use winamp, have my music library locally and it does exactly what I need it to.. play music. What are winamp even trying to do at this point, take over streaming?

[–] fulg@lemmy.world 11 points 1 month ago (1 children)

I thought I read elsewhere there were some GPL 2 parts in there too, I guess not.

I tried to find a source for this more credible than “I remember reading it on Lemmy” but couldn’t, now that the repo is deleted nobody can confirm. Perhaps some forks still exist… 🤔

[–] sukhmel@programming.dev 11 points 1 month ago (1 children)

Perhaps some forks still exist…

No, that's impossible, because they didn't allow it 😭

[–] Scoopta@programming.dev 5 points 1 month ago

According to the article they did allow it. They got rid of that clause in a license update, just didn't allow you to modify your fork lol

[–] Kissaki@programming.dev 1 points 1 month ago* (last edited 1 month ago)

I wasn't aware the GitHub terms of service explicitly grant / require you to grant permission to fork [within GitHub].

GitHub ToS section License Grant to Other Users

By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).

If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). […] If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.