this post was submitted on 25 Jun 2023
145 points (100.0% liked)

Technology

37708 readers
403 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] RandoCalrandian@kbin.social 3 points 1 year ago (1 children)

is AGPLv3

Hey, you’re right!

To get around that they’d have to do something drastic, like getting the owner of the code to change the license in next release, and keep him in an NDA while doing so in order to position themselves when the change happens.

Good thing we’re not seeing that

[–] dan@upvote.au 3 points 1 year ago

getting the owner of the code to change the license in next release

AFAIK, all contributors need to agree in order to change the license of a codebase. If a contributor disagrees, their part of the code has to be rewritten in order to comply.