•

Non-Canonical employees removed from LXD maintainership

Christian Brauner 🦊🐺 (@brauner@mastodon.social)

https://mastodon.social/@brauner/110781239093096206

Apparently I'm not a maintainer of #LXD anymore and neither is @stgraber@hachyderm.io. So it seems from now on it's Canonical employees only. I'd like to point out that before Canonical moved LXD into github.com/canonical/lxd maintainership was completely independent of the company. If you went to work somewhere else you still were a maintainer. As it should be with any well-functioning OSS project.

6 comments

nickb333

•

I noticed this a few days ago. https://stgraber.org/2023/07/10/time-to-move-on/

housepanther

•

I did not need another reason to avoid Ubuntu. There are already enough. 😁

comicallycluttered

•

I wonder when SUSE is going to have their turn at annoying a bunch of people.

Canonical's been doing it for years, Red Hat decided to run with it as well, and I'm pretty sure SUSE is the only major enterprise left that develops their own distro.

ono

•

LXD never quite fit my needs, but I use LXC daily, so this feels like a loss. I wonder what Canonical expects to gain by kicking out core contributors like this.

leetnewb

•

Headline sort of buries the lede of how important those two were to building lxd and supporting the container ecosystem on linux. Sad to see. I have been using lxd on my home network and vps instances for years. Disliked when the project moved to snap-only distribution, but at least other projects picked up native packaging. And it doesn't seem like lxd is going away, which is nice. But Canonical explicit seizure of control withers confidence I had in the long-term viability of the software for my own use.