-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HEALTH]: Teller #1544
Comments
Notes:
|
Why am I pinged? I don't engage with the project due to the contributor experience being negative. Other contributors may have similar reasons. I especially did not like how they handled the switch from Go to Rust, my feedback was clearly ignored there in asking for a final Go release 🤷♂ This isn't the first time that project received a DevStats notice like this btw. They responded with Teller 2.0 release in May 2024, and no development activity in public since then. That 2.0 release was sudden, there was nothing done in public until that point AFAIK, I wouldn't be surprised if that's continued to be the case since 🤷♂ |
thanks for your feedback @polarathene ! |
The org that owns the repo has no public members https://github.com/tellerops so its unclear whose running the project outside of https://github.com/jondot these days. I am not an official maintainer but have made several contributions to both the golang and rust code bases and would be sad to see it archived as its a very useful tool. It doesn't need a huge amount of work and even in a healthy state likely wouldn't see a huge volume of contributions other than potentially more providers but its in pretty dire need of some TLC to things like the docs and updating the core libraries and fixes to the build/publish process. |
Another inactivity indicator; they never completed onboarding: cncf/sandbox#177 |
Project name
Teller
Concern
There has been minimal activity over the past 90 days, and decreasing since then:
and no commits since June of last year:
Additional information can be seen on Teller's LFX insights dashboard
Prior engagement
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: