They are nuts. Their license means that you give up all of your authorship rights to the code you contribute, and on top of that you’re not allowed to distribute modified source, nor can you fork the source for any purpose.
Edit: lol
this post was submitted on 24 Sep 2024
175 points (95.3% liked)
Programming
17313 readers
313 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
So many forks, lol.
Winamp go fork yourself!
It really forks the llamas ass!
Does that actually matter?
I'm asking because license stuff is over my head, but I'd like to learn about it more.
They basically want free labor.
If you only care about contributing improvements, no, it doesn't matter.
If you want to at least be recognized as an author, and be able to say "I made this", the license opposes that.
Waiver of Rights: You waive any rights to claim authorship of the contributions […]
I don't know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.
Also, this isn't even compatible with copyright law in some countries. I.e here you can't give up authorship at all; you can only grant an irrevocable, perpetual license (that might even prohibit you from distribution yourself and such) but you'll always be able to say "I made this" no matter what their license says.
The way I look at it is this: I want credit for the work I do, I should also be able to fork a repo that I work on, and I sure as hell don’t like giving up my rights if I can help it.
But others may feel different.
I guess, opening a PR without forking is possible, but hey that's sort of incredibly bullshit idea
It...seems like there may be some issues with the repo...
I lost it when coming across this commit: https://github.com/WinampDesktop/winamp/commit/67c68e6dc24f36b266427034d016fb86ef4d486c
I love GitHub drama.
Anyone know if the Dolby code leak is going to lead to anything interesting, or had this code been leaked before? And how fucked are the Winamp folks?
Context:
https://github.com/WinampDesktop/winamp/issues/17
Confidential Dolby code was pushed, though just some headers files.
And then they just push a new commit without the files, completely unaware that git keeps all versions of the code? I feel like this repo is going to disappear.
Thats golden !
This really whips the llama's ass