![]() ![]() Gabber had worked for Ubuntu for more than 18 years, and for the last eight years had been directly involved with the LXD project - first as the project’s technical lead, and since September 2018 as the projects engineering manager. When we reported the story on July 5, the reasons for Canonical’s removing the project from community control were unknown, but at least one reason came to light on July 10, when Stéphane Graber announced on his personal blog that he had resigned from Ubuntu. You might remember that back in early July, Linux Containers announced in a statement that going forward it would no longer be hosting LXD because, “the creator and main contributor of the LXD project has decided that after over eight years as part of the Linux Containers community, the project would now be better served directly under Canonical’s own set of projects.” Almost all of the same community people who were in charge of the project when it was Ubuntu’s LXD are in charge at the project as Incus. ![]() This was a neat cut and paste for the folks at Linux Containers. While this was happening, the head honcho at Canonical/Ubuntu, Mark Shuttleworth, was commenting to a Hacker News post, in what seems to be something of a doomed attempt at damage control. ![]() On Friday the LXD project that Ubuntu had removed from community development a month ago was forked as Incus, and then almost immediately the fork was accepted as a project by Linux Containers, LXD’s former home. The LXD story has turned into a bit of a soap opera, but one with a happy ending for those who support openness. Stéphane Graber at the 2016 Linux Security Summit. ![]() About a month after Canonical pulled LXD from Linux Containers, with the ‘LXD community experiment’ evidently being labeled internally as a ‘failure’ by Ubuntu, the code is forked and almost immediately accepted as a project at Linux Containers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |