-
Notifications
You must be signed in to change notification settings - Fork 145
new maintainers / transferring to a group? #96
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
Comments
@stapelberg are you still interested on main this repository? |
Hey @mcuadros, yes, I would still be interested |
I would be weary of taking on any new maintainers that haven't already had a long history/role in contributing to the project. This smells like something we have all seen before in |
You can look at https://michael.stapelberg.ch/ and https://github.com/stapelberg/ to get a sense of how real I am :) I am contributing to Go in one way or another for 10+ years, since a while also professionally, see for example https://go.dev/blog/protobuf-opaque for proof. |
Hey @mcuadros, thank you for publishing this package! As you don’t seem to be active in the project anymore, I was wondering if you would accept a co-maintainer to help address open issues? Or perhaps would you be open to transfer the repository to a (to-be-created) GitHub org to make it independent of your name?
I would be happy to help (as time permits) and have some experience with this role (check my GitHub profile), for example with http://github.com/jacobsa/fuse/, which I am co-maintaining.
The text was updated successfully, but these errors were encountered: