-
Notifications
You must be signed in to change notification settings - Fork 31
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
New maintainer needed! #138
Comments
@schaumtier @LordMZTE given your recent contribution, maybe you would be interested? |
Thanks, but I unfortunately moved away from Rust a while back, so I don't feel like I'd be entirely up to the task. I have worked with GTK (and Relm4 a while back), but I also don't really have the time. I'd definetely be open to contributing regularly, but maintaining is a little much :D |
I have almost no experience with rust. I personally don't use it. My PRs are mostly copy-paste from existing code in the project... but i have no idea about the whole thing. So i'm sorry, but that won't work. |
thank you, I appreciate your comments! |
May I ask in what way does it need to be maintained? Maybe giving a bit of details would attract more potential maintainers |
I wanted to thank you for this project. wish you success and happiness |
That is a very good point, thank you! I added details in the first post! |
Introduction
I do not have the time to maintain and/or develop Satty further. In fact, I recently had to migrate away from Linux :/.
At the same time, I am proud of the traction that Satty achieved so far and I still believe in its mission. Therefore I am reaching out to the community. I know that many of you are developers and I am sure there are people that are interested in pushing this forward. Required skills: Rust, GTK, a good vision and a warm hand with the community. If you are interested, please let me know!
Work as a Maintainer
There are two topics, that need to be worked on. My observation is, that both needs to be done at the same time!
Ways forward
I am prepared to give Satty away, if someone steps up. But I don't think that it is strictly necessary at this point. I am also open to some kind of co-maintainership, where someone would help with the technical side. This way, we could also ensure a smooth learning curve etc. After all, I am interested in keeping the tool and the community alive.
The text was updated successfully, but these errors were encountered: