As of yesterday, the #LXD project is no longer part of the Linux Containers project but can now instead be found directly under Canonical's control.

Please read our official statement on:
https://linuxcontainers.org/lxd

I personally consider Canonical's move to be a hostile act and as far as I'm concerned the decision was unilateral. It may be legally sound but it leaves a very bad taste behind.

I've been involved with this project independent of what company I moved to. To see this happening is sad.

Linux Containers - LXD - Has been moved to Canonical

Apparently I'm not a maintainer of #LXD anymore and neither is @stgraber. 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.

@brauner
That hits hard! I noticed the links into the documentation had stopped working but I was in a hurry and did not read the statement.

I thought you were all employed at Canonical anyway, but apparently this was a misconception.

LXD is one of my favourite tools - I am worried what will happen ๐Ÿ˜ข
@stgraber

@brauner
@stgraber
Oh FFS. Is it worth a fork or does it make more sense to see what direction it gets taken in?
@srtcd424 @brauner @stgraber with a move this hostile it seems pretty clear a fork is necesarry :/
@brauner @stgraber companies couping maintainers out is absolutely not okay for any project, the heck they were thinking.
@brauner @stgraber this is so sad ๐Ÿ˜ข LXD is an awesome project and deserves better than this!
@brauner @stgraber That means theyโ€™re gonna ๐Ÿคฌ it up and do something like RH has.
@brauner @stgraber sorry I say this, but Google generally does this better...

@brauner @stgraber

> So it seems from now on it's Canonical employees only.

Here it says this in the CONTRIBUTING.md file: https://github.com/canonical/lxd/blob/0c2f4271a6326a2a24bc57b50abe0456ae94e7f1/CONTRIBUTING.md#license-and-copyright

> The author of a change remains the copyright holder of their code (no copyright assignment).

You can probably fork the project and change its name (to avoid copyright issues)... I don't know if the benefits are more than its cost, though...

lxd/CONTRIBUTING.md at 0c2f4271a6326a2a24bc57b50abe0456ae94e7f1 ยท canonical/lxd

Powerful system container and virtual machine manager - canonical/lxd

GitHub
@brauner @stgraber this doesn't seem terribly unusual to me. When I left teams _within_ Canonical my maintainership of old projects was revoked. It seemed like reasonable opsec. When you're paid to work on something it seems that the assumption is when you're paid to work on something else you will no longer be contributing. Of course that's not always accurate, but it seems like a reasonable position to take.
@brauner @stgraber Right on the heels of Red Hat setting a torch to any remaining community good will they may have had and folks have been looking to Canonical/Ubuntu.
@brauner @stgraber Why am I not surprised of this?
@thelinuxEXP Can you include this in the next news episode?
@jeremystartm It was in a previous one, or at least in the podcast!
@thelinuxEXP Oh. Probably missed that. Thanks anyway!

@brauner @stgraber

Base on what interactions I have had with Canonical management, I am not surprised in the least that they'd pull such a hostile and alienating move. Luckily, given history, the Incus fork will thrive and Canonical's LXD will probably wither.