5 ms·

How much equity did they kick back to the devs from the open source era?

• bsnnkv 1y ago
  As much as I appreciate a good snarky comment, this is a good reminder for contributors to be thoughtful about the licenses under which they contribute code to projects > Nowhere in any common open license does anyone promise to keep working on their project, much less on particular terms. Any contributor to a permissively-licensed project can license their next contribution however they want. Any steward of a copyleft project with rights to all contributions can, too. Much as you could pick an Apache-licensed project, fork it, and sell your enhanced version under proprietary terms, a project steward can share new work under new terms, as well. > > None of this changes the license terms for old releases. Prior versions with MIT or Apache 2 or MPLv2 or what have you in the LICENSE file remain available to use, share, and change under those terms. That includes forking. We see that every time a going-forward relicensing spawns a new one. The reason the new license terms matter for new releases is that those new license terms apply to the diff between the old release and the new one.[1] [1]: https://writing.kemitchell.com/2023/09/23/Two-Kinds-Relicensing https://writing.kemitchell.com/2023/09/23/Two-Kinds-Relicens...