This is a follow-up to Jon’s original post on Carefully (but purposefully) oxidising Ubuntu and Julian’s migration spec for 25.10. We promised transparency throughout this process, and this post is written in that spirit. What happened after the announcement Following the decision to adopt rust-coreutils, we got to work. Any package shipped by default in Ubuntu must be promoted to Ubuntu Main, which requires passing a thorough security review. We quickly assembled an internal team spanning Ubun...
The mit license allows someone (some company) to modify the open source codebase and sell the result without making their modifications public.
That is not equivalent to closure of the commons, that’s some company spinning a proprietary version of something. If they try to sell it, most people won’t buy - most people will continue to use the FOSS version. The people they sell it to may enjoy the proprietary enhancements, but that doesn’t prevent the FOSS community from developing those enhancements in the open if they so choose.
It’s a thing that happened a long time ago during the Industrial Revolution in England where land that people used to grow subsistence or cash crops for their own use as opposed to their lords use (land called the commons) was fenced in and given to newly elevated lords as estates.
The effect was that people who could live in villages before were forced to move to the cities and live in slums or poorhouses and became laborers in mills.
Oh, so you believe MP3 pirates have actually stolen something off of the retail music shelves as well, then? Digital piracy is the ultimate evil and all that? Supporting strong jail terms for pirates, are you?
The difference between the commons of the industrial revolution and the commons of the digital landscape is that the commons of old was a finite resource. The digital commons is effectively infinite.
It’s a mat with conclusions on it and you can jump on them, it’s a jump to conclusions mat!
The digital commons is protected by making sure changes to it and work that builds upon it remain in the commons, not by letting everyone go hog wild because copying only costs the amortized price of access, storage and electricity.
Gpl does that by requiring that things that use it also become gpl.
I’m really surprised to be explaining this. Some guy wrote a book that has a good overview of all this stuff but in the context of sampling almost 30 years ago, I’ll chase it down when I get near that shelf.
That is not equivalent to closure of the commons, that’s some company spinning a proprietary version of something. If they try to sell it, most people won’t buy - most people will continue to use the FOSS version. The people they sell it to may enjoy the proprietary enhancements, but that doesn’t prevent the FOSS community from developing those enhancements in the open if they so choose.
MIT license is not a software patent.
The enclosure of the commons.
It’s a thing that happened a long time ago during the Industrial Revolution in England where land that people used to grow subsistence or cash crops for their own use as opposed to their lords use (land called the commons) was fenced in and given to newly elevated lords as estates.
The effect was that people who could live in villages before were forced to move to the cities and live in slums or poorhouses and became laborers in mills.
E: clarity
Oh, so you believe MP3 pirates have actually stolen something off of the retail music shelves as well, then? Digital piracy is the ultimate evil and all that? Supporting strong jail terms for pirates, are you?
The difference between the commons of the industrial revolution and the commons of the digital landscape is that the commons of old was a finite resource. The digital commons is effectively infinite.
It’s a mat with conclusions on it and you can jump on them, it’s a jump to conclusions mat!
The digital commons is protected by making sure changes to it and work that builds upon it remain in the commons, not by letting everyone go hog wild because copying only costs the amortized price of access, storage and electricity.
Gpl does that by requiring that things that use it also become gpl.
I’m really surprised to be explaining this. Some guy wrote a book that has a good overview of all this stuff but in the context of sampling almost 30 years ago, I’ll chase it down when I get near that shelf.