LXD now re-licensed and under a CLA

Thank heavens for Incus.

5

The issue here is that this will stall the development of LXD/Incus. Two separate projects running in different directions no future feature parity and potentially less features in Incus than in LXD.

4
- Currently LXC Incus is more active than Canonical LXD.
  
  2

I just see a problem here:

I perfectly understand, approve and back this move, however I’ve a question about the current state of things and specifically Debian 12 users. Debian includes LXD LTS 5.0.2 on their repositories and that version will be still be around after 2024/05 and trying to use the image server. Debian won’t likely change stable to include Incus until 2025, what’s the suggested path here?

https://discuss.linuxcontainers.org/t/important-notice-for-lxd-users-image-server/18479/9

5

Fucking Canonical at it again.

4

Do people actually use LXD in production? All hosting services I've seen use LXC and not LXD for containers, as do UIs like Proxmox and Unraid, and you don't have to use Snap for LXC.

4

Reminder that Incus (the community fork) is still a thing for people concerned about the relicensing and new direction https://github.com/lxc/incus

2

I though it was being relicensed under agpl?

1

I though it was being relicensed under agpl?

The answer is in the submitted blog post.

2
It's both

1

I actually stopped caring about what the fuck Canonical is doing. Matter of fact, the only REALLY good company for the Linux ecosystem as of right now is Valve; Canonical fucks us with snap, Red Hat kills X11, Google is closed and nVidia is closed and buggy.

The community should own everything. I know how important the company's contributions are, but sometime I'm just pissed off from how incompatible is what there are doing with the FOSS philosophy.

-2

Red Hat kills X11

I mean Red Hat does bad things, but is switching to Wayland a bad thing?

25
- Well let's see
  
  Doesn't work with nvidia, the leading vendor of graphics cards
  
  Drops support for a huge set of diverse window managers and applications
  
  Reimplements X11 functionality over shitbus, an incomprehensible nightmare
  
  sandboxing security designed to enable Windows/Android like apps where users run random proprietary malware
  
  Promoted for purely idiotic reasons like like "circular windows"
  
  I could go on...
  
  -13
Of all the reasons you could have chosen for Red Hat you chose "they killed a dead corpse"?

X11 was already dead, it isn't getting updated, and its maintenance is gonna end eventually. Sure Wayland still has issues but once it's ready for widespread use (which it is, save maybe for gaming on PCs with like 6GBs of RAM) the jump is unavoidable. In fact by doing this they got more people to work on fixing the issues in Wayland

12
- Wayland on its own may be ready but you can't build a whole desktop with just Wayland. The rest of the stack needs time to catch up.^(*) And no, not everybody is willing to use KDE and restrict themselves to whatever combination of elements happens to work right now.
  
  ^(*) Because the bright people who did this decided they needed to throw the baby out with the bathwater on X. They couldn't possibly find a way to ditch only the obsolete parts and fix the problems and maintain compatibility as much as possible. No, everything had to be rewritten from scratch.
  
  So here we are 15 years later, with another 5 or so to go until the whole Linux desktop ecosystem will be thoroughly redone.
  
  0
Red Hat kills X11

So does Valve. Valve and Red Hat are the driving forces behind the recent HDR advancements.

12
- Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.
  
  I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.
  
  But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)
  
  So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.
  
  1
- Yes, but I can still play steam, any Valve game and atm any Linux steam game on X11.
  
  I don't hate Wayland as a project, I just don't like Wayland as it current state. Give me better stability, better support with multiple monitors and a compositor with more customization, and I'll be happy.
  
  But, in my opinion, Wayland is by design opinionated. Some ideas are good, such as the security model, some are both good and bad, such as the Compositor VS Server+WM debate (both good systems in my opinion), some are just bad (no unified screen management option; obviously there are LOTS of protocol extension, but not all are supporting everywhere)
  
  So, imo, WayLand just needs a stable, (really) customizable Compositor with all useful extensions and designed to put other components together; I'm still on my X11+awesomewm+rofi+polybar, and I want a customizable, stable and module approach on Wayland.
  
  -1
It's important to note that the CLA does not take ownership of your commit. To quote the CLA:

(a) You retain ownership of the Copyright in Your Contribution and have the same rights to use or license the Contribution which You would have had without entering into the Agreement.

All the CLA does, is say "I agree that Canonical can use my code under another license if they want to". Your contribution is still yours.

I would also argue that by enforcing AGPL rather than Apache, the community gets more ownership. I'd rather have seen Canonical not require a CLA so they can sell the software you're contributing, but AGPL forces everyone but Canonical to open up their custom versions to their customers, which are free to rehost it elsewhere and help bring the changes upstream, of course.

As for ownership: LXD was started by Canonical. The name and trademark is theirs, and they control the upstream project. Like always, you can reject their terms and provide your changes under another license, but as the article states, Oracle is free to take your Apache2 changes and use them for practically any purpose as long as they put a copy of the license next to their code and give you credit. That includes selling the software. Not just Oracle either, of course; IBM/Red Hat and Oracle can do the very same.

The community should own everything.

In a perfect world I agree, but then the community should take over doing the actual work. Right now, almost all of the work on open source is done by companies and organisations such as KDE and Gnome with their own committees and politics.

Software for some products don't have company-supplied software (i.e. Asahi Linux, although they do have parts of the Darwin kernel for reference) but those devices also often take ages to become usable. There are also plenty of projects funded by charities and such, but most of those form some kind of organisation that owns the copyright by default.

the only REALLY good company for the Linux ecosystem as of right now is Valve

They brought Linux to the mainstream by locking down most of the customisability and by promoting running proprietary software. That's just the way things need to be, but I'm not sure if the Linux ecosystem should be that happy about these developments.

Canonical fucks us with snap

It takes two minutes to install Flatpak and remove Snap. Their apt-to-snap transition is stupid and annoying, but it's a very minor issue.

Red Hat kills X11

Red Hat stops maintaining X.org for free now that a better replacement is (almost) ready. The community is free to set up an effort to prolong X11's life span, of course.

Google is closed

More and more closed (mostly on Android, because as it turned out, the people taking the Android source code and distributing their own forks didn't contribute back much), but Android and Chrome are still almost completely open. Your alternatives are iOS (closed for all but the reference kernel), Sailfish (Android app support necessary for real world use but closed and paid), Ubuntu Touch (using the Android HAL, so about as open as Android), and the various Linux distros that can barely do power management and often lack features such as "placing a call"; Google still provides some of the best open source software for mobile devices.

Google's ChromeOS is perhaps the weird exception here, being basically a closed-ish source Linux distribution. All the components that power it (Linux, Chromium, Android) are open source, but the special sauce that makes those useful for end users is closed.

nVidia is closed and buggy

Buggy? Yes, 100%. One day I will be able to use Wayland without random stutters and crashes!

Closed? Not for recent GPUs. Starting at the GTX1650/1660, the drivers are completely open source, with only the firmware being closed like on every other GPU. The closed nature of earlier cards (which still requires something like the GPL condom) still sucks, but they're clearly improving.

7
I hate Red Hat as much as anyone, but X11 is dying even without them.

2
red hat is the one maintening x11 lol, it only working right now because of them

1