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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
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.
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
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.