this post was submitted on 24 Sep 2024
176 points (94.9% liked)

Programming

17424 readers
24 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 !webdev@programming.dev



founded 1 year ago
MODERATORS
top 33 comments
sorted by: hot top controversial new old
[–] dohpaz42@lemmy.world 90 points 1 month ago* (last edited 1 month ago) (3 children)

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

[–] AlligatorBlizzard@sh.itjust.works 23 points 1 month ago (1 children)

So many forks, lol.

Winamp go fork yourself!

[–] theherk@lemmy.world 20 points 1 month ago

It really forks the llamas ass!

[–] TachyonTele@lemm.ee 14 points 1 month ago* (last edited 1 month ago) (3 children)

Does that actually matter?
I'm asking because license stuff is over my head, but I'd like to learn about it more.

[–] projectmoon@lemm.ee 48 points 1 month ago* (last edited 1 month ago) (1 children)

They basically want free labor.

[–] Kissaki@programming.dev 15 points 1 month ago (1 children)

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.

[–] amju_wolf@pawb.social 7 points 1 month ago

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.

[–] dohpaz42@lemmy.world 8 points 1 month ago

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.

[–] sukhmel@programming.dev 2 points 1 month ago

I guess, opening a PR without forking is possible, but hey that's sort of incredibly bullshit idea

[–] roadrunner_ex@lemmy.ca 44 points 1 month ago (1 children)

It...seems like there may be some issues with the repo...

[–] AlligatorBlizzard@sh.itjust.works 21 points 1 month ago (1 children)

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?

[–] naught@sh.itjust.works 16 points 1 month ago (2 children)

Context:
https://github.com/WinampDesktop/winamp/issues/17

Confidential Dolby code was pushed, though just some headers files.

[–] purplemonkeymad@programming.dev 10 points 1 month ago

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.

[–] Valmond@lemmy.world 4 points 1 month ago

Thats golden !

[–] Greg@lemmy.ca 20 points 1 month ago

This really whips the llama's ass

[–] refalo@programming.dev 19 points 1 month ago

It was already on github 10 months and 3 months ago.