LXD Maintainership Being Limited to Canonical Employees | Hacker News Reader

LXD Maintainership Being Limited to Canonical Employees

phoronix.com

37 pointshpb429 comments

Serge Hallyn, Stéphane Graber, and Christian Brauner are/were some of the most prolific contributors to LXC and LXD. It is hard to tell from the Github insights, because they typically used their canonical email and no longer have that tied to their account.

Sad to see an open source project that they basically started from scratch be ripped away from them.

As an aside, congrats to Poettering for successfully keeping systemd separate from IBM and hanging onto maintainership when moved to Microsoft.

Nothing like a good recession to get these corporations showing their true colors.

A very astute observation. Everything is free, happy, and philanthropic as long as cheap Fed money is pouring down from the heavens.

Also, the open source projects not doing this are either have a fierce policy of no corporate interference (openbsd) or have very strict guidelines about keeping their codebases purely opensource (debian).

these kind shenanigans are looked down upon, especially from a operations perspective.

I want a boring operating system goddammit, without getting either grifted by a corporation (redhat/IBM) or having to deal with plain anti-user behaviour (microsoft).

There's a difference between maintainer and contributor. Canonical is now the maintainer of LXD, but I think they would still accept contributions from the community. I've contributed in the past to some projects from Canonical, I hope they continue accepting contributions.

The main point I see here is: LXD is not a community-driven project anymore. LXD now follows what Canonical wants/needs, not necessarily what the community wants/needs.

Impending fork in 3...2...1...

Is it? I felt much more at home with LXC/LXD when I looked into the container options but I feel like it basically lost to overwhelming hype.. Add a situation like this and maybe that's the end outside of some very small group of existing users?

What would be the point of a fork? Is there a controversial patchset that can't be accepted by current maintainers? Or, conversely, is anything important being done by the current maintainers what the community at large is unhappy about?

I can imagine an eventual fork, like gcc / grcs or xfree86 / x.org of old, if a real issue to split on crops up.

Fork

Reply on news.ycombinator.com