this post was submitted on 26 May 2024
657 points (98.5% liked)

Technology

59219 readers
3980 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jonasw@discuss.tchncs.de 198 points 5 months ago (11 children)

WinAmp making their source code 'source available' instead of open source, and then dropping this phrase:

The release of the Winamp player's source code will enable developers from all over the world to actively participate in its evolution and improvement.

Yeah I don't think so

[–] xavier666@lemm.ee 5 points 5 months ago (2 children)

What are some projects which have "source available"? Can someone get the source and upload or will it violate some NDA? And what kind of licence is associated with this?

[–] jonasw@discuss.tchncs.de 3 points 5 months ago

For example terraform changed their license to a non open-source license, and everyone hated it. Then a fork was created, which used the code before the license change which was still licensed under an open source license. The fork "OpenTOFU" is now 'owned' by the Linux Foundation

https://opentofu.org/blog/opentofu-announces-fork-of-terraform/

Same for redis, there is also a fork called Valkey now, which is also 'owned' by the Linux Foundation:

https://redis.io/blog/redis-adopts-dual-source-available-licensing/

https://devops.com/valkey-is-rapidly-overtaking-redis/

load more comments (1 replies)
load more comments (9 replies)