-
Notifications
You must be signed in to change notification settings - Fork 43
Archive project? #184
Comments
No responses. Coming up to a year since I posted this in a few months. |
My assumption at this point is that lxdock now has zero users left, it's likely not functional anymore in it's current state and with the version of LXD today. |
It's now been over a year since I created this ticket and nobody seems to care about moving the project to archive status. |
Does anyone care if I archive this project? I don't think anyone uses it and nobody wants to contribute. |
I haven't looked into LXD for a while, but ran into this today: https://old.reddit.com/r/linux/comments/1c2bzmh/lxdincus/ I really think we should archive lxdock, to me it seems irrisponsible to keep this repo in an unmaintained state for years like this. Many releases of LXD have happened in the mean time and we totally haven't kept up. And now it seems something else is going on again with this LXD to Incus migration. I'm going to have a read up, but I still want to archive the project by the end of the year if nobody steps up. |
Nobody cares, I'm talking to a brick wall. I'm archiving this now. |
Several years have passed since the original authors of lxdock moved on. I took over for a while, but I stopped using lxdock years ago for docker compose and it's just been sitting here gathering dust.
There haven't really been enough maintainers step up to keep this project going. Basically the project is dead at this stage in many peoples eyes. There has never been a pypi release since the original authors moved on either.
I don't have the time and energy to maintain it myself, let alone build and publish snaps for it regularly.
Unless someone else steps up, I see it is more responsible to archive the project.
The text was updated successfully, but these errors were encountered: