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...
Is rust-coreutils being developed by Canonical? Then it sounds like shooting themselves in the foot. Why give competitors a chance to take over a vital package that is at the core of their OS?
I’m no licensing expert and I was responding to the previous comment that said someone can fork it and then make it proprietary. So If they already have dominant market position, they could force people to use a proprietary version.
Is rust-coreutils being developed by Canonical? Then it sounds like shooting themselves in the foot. Why give competitors a chance to take over a vital package that is at the core of their OS?
How is MIT a “chance to take over”? It’s a chance to go proprietary with future enhancements, but that’s far from a takeover.
I’m no licensing expert and I was responding to the previous comment that said someone can fork it and then make it proprietary. So If they already have dominant market position, they could force people to use a proprietary version.
Some Canonical employees are working on it but it’s not originally a Canonical project.