Skip to content
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

[Maintainer] Looking for maintainers! #218

Open
Shinyzenith opened this issue Aug 13, 2023 · 3 comments
Open

[Maintainer] Looking for maintainers! #218

Shinyzenith opened this issue Aug 13, 2023 · 3 comments

Comments

@Shinyzenith
Copy link
Member

Swhkd is now a mature enough projects where people use it in their daily workflow. Swhkd has it's fair share of flaws and issues which I have not been able to keep up with due to my various other commitments to the wayland ecosystem projects I maintain.

I think it's time to hand over swhkd to a new maintainer who is willing to improve the project.
I shall remain the BDFL of swhkd however I am willing to give maintainer rights to whoever is willing to accept the project under their guidance.

If you are interested feel free to mention in this thread. I want to ensure I transfer the rights to the right person and not just hand over the repo directly, It would be preferable if I could show them how every part of swhkd works to better transfer knowledge and rights!

@Shinyzenith Shinyzenith pinned this issue Aug 13, 2023
@foxjaw
Copy link

foxjaw commented Jan 8, 2024

Did you consult @baskerville ?
baskerville/sxhkd#109

@Shinyzenith
Copy link
Member Author

Hi, in reference to the linked sxhkd issue, I just want to make it clear that swhkd isn't a spiritual successor to sxhkd. I haven't asked baskerville to maintain this repo and I will not do so anytime soon. If anyone has any interest to maintain waycrate tools then I'd prefer if they voice their opinion on our issue tracker instead.

@foxjaw
Copy link

foxjaw commented Jan 8, 2024

I can understand. Btw I think your implementation is way different than sxhkd which is why it can't be a successor right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants