You're conflating git with git forges. Most popular forges use a centralized model. Git was built as distributed from the start and it's original mode of collaboration was through a federated protocol.
Apache doesn't enforce copyleft, so the Pear authors can license whatever changes they made to Continue with any license they want.
What isn't ok is to change the license of the existing code. They seemed to have corrected this since[0]. I think it's very hard to argue they didn't comply with the Apache license in this case, especially since the license is technically included in the forked git history.
On the surface this just seems like it was a naive and sincere mistake. I doubt that the Pear people were trying something nasty.
It also seems one of the founders has a fairly popular YouTube channel, so he's probably aware that this sort of nothingburger drama is great for business if handled competently.
A lot of effort is spent on packaging the stuff we need for our own infrastructure so we can run it in prod. Gitlab is one of these exceptions but generally it's been working well for us.
I'm sad to see Stephane leaving, but it's lost in me how his departure towards doing whatever else he wants to do suddenly transforms into LXD not being open?
I use it a lot for personal homelab infrastructure. I find it feels a lot more natural than single process containers for the workloads I use (torrent clients, game servers, plex...). I've unfortunately never used it for production workloads, and likely never will after recent news.
I also find lxc system containers better than OCI style immutable containers for dev environments for my personal projects, and LXD is the best way to manage them AFAIK.
- if you have a good hardware , you can easily build digital ocean / aws lightsail like environment with a single install in 5 mins of configuration - A VPS Like experience for both Containers and QEMU
- Quick and easy multi-tenancy
- Very easy to build development enviorment isloated from the system.
- Isolation host for docker containers.
- Automatic networking support with DHCP , OVN or MacVLAN if you have multiple physical IPs.
- Home Made Cluster of containers.
It is literally best way to host multiple docker containers. Isolated from each other.
You wont need K8s in many case , infact if you don't have 10k+ users , do not need to worry about 99.999 uptime and redundancy - LXD is all you need.
Or if you have only one Physical Machine and want to test K8s cluters , you can use LXD Containers for that instead of resource intensive VMs.
CentOS 7 is supported and will be EOL at the same time as RHEL 7.
Stream does have major versions so you can continue to use CentOS Stream 8 and get backports. You only lose anything if you're tied to some minor version of EL for some reason.
