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...
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.
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.