🔴 Project Status

[NickLarsenNZ]

Sorry if this isn't the right place to ask.

Sloth looks like a really useful tool, and I think I'd like to use this for our applications.

I was wondering what the future of this project is? There hasn't been a merge since the end of lsat year and there are some open PRs that are getting quite old. I also see newish PRs, but if they aren't getting merged, it might discourage future contributions.

Is there a place to discuss (eg: matrix.org) or would you consider enabling Github Discussions on this repo?

[freeseacher]

looks like project is done and it is in final shape.

[sstarcher]

@freeseacher by final shape do you mean abandoned and PRs are no longer accepted?

[slok]

The idea of enabling discussions can be good so the community around the project continues. I will think about it, many thanks @NickLarsenNZ

@freeseacher is right. Thanks :)

@sstarcher It's not abandoned, it's stable and working, 99% of the work that was expected is done and works for most of the people (if this is not your case, I'm sorry), being used every day in different companies and installations. If you think that this is not the case and the project can't be used as today or doesn't meet the minimum requirements, please, be my guess and maintain an up to date fork that meets those. If people start using that, I will happily archive this one in favor of yours.

Regarding the PRs, ad-hoc features (specific single use case) and custom installations (e.g: Helm properties) are not a priority in the project or in my life currently.

[sstarcher]

It would be helpful to document in the README.md what is supported and being maintained. The issue I ran into is that your tolerations in your helm chart are invalid due to the location. This is certainly a bug and a PR exists for it #503.

I'm not insisting that you maintain anything just wanting to know the status and expectations on the project.

An additional question is if the project will be keeping dependencies up to date or should users of the project expect to need to do that from a security standpoint?

[freeseacher]

being used every day in different companies and installations

with some local patches. ;)

[NickLarsenNZ]

looks like project is done and it is in final shape.
@freeseacher is right. Thanks :)

To me that sounds like it is indeed abandoned. There are currently 61 open issues, and 14 open PRs (excluding automatic) - contributions from people who are fixing or adding features that they feel are needed.

If you think that this is not the case and the project can't be used as today or doesn't meet the minimum requirements, please, be my guess and maintain an up to date fork that meets those. If people start using that, I will happily archive this one in favor of yours.

That is certainly a last-resort, but I had hoped that perhaps there could be more maintainers if you are not in a position to take that on.

---

Could I suggest (as @sstarcher suggested) you add a notice to the readme to allay expectations and perhaps consider inviting maintainers (also as a notice on the readme)?

[gaby]

The main problem is that all the dependencies are super outdated!

https://github.com/slok/sloth/blob/main/go.mod

[christidis]

I guess project is called Sloth for a reason!

[alex067]

Is there any interest in forking the project to continue development?

[cxdy]

Cross-posting here, but we're maintaining an active fork of sloth at linode-obs/sloth if anyone is interested in submitting PRs over there. We requested to become maintainers of the upstream repo in #541 as well.