-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Maintenance status #144
Comments
That's def something I'd appreciate. I'm juggling busy work a new baby and a bunch of oss projects |
Also heads up, I just realized I haven't been getting GitHub notif emails for a while. I'm trying to resolve that now. That's another source of delayed response for me. I'm not getting any email from GitHub atm! |
I'm happy to chip in with code reviews. Just tag me if you need an extra pair of eyes. |
EDITED: This is not applicable anymore. |
@softprops Let's invite @zamazan4ik to the owners of |
Ping, @softprops, we can't continue improving the crate if we can't make new releases... |
Hi folks there must have mean a mis-communication somewhere. I don't recall agreeing to moving the development for this crate to another repo? Forks are welcome but this is the canonical repository |
I do not appreciate this kind of thing. Declaring one's self a canonical replacement without consent if an author is closed to boarder line steeling. I've only consented to expanding the list of maintainers for those that would like to volunteer above |
Yeah, this was a kinda misunderstanding here, I agree. Sorry for that from my side. |
@softprops, I would like to volunteer for I see that you have low capacity so I want to ask you if you could share with me all or any of the permissions:
|
Looks like this project requires more maintainership to keep up.
@softprops, seems like your availability cadence is not enough, what do you think about expanding the maintainers list?
The text was updated successfully, but these errors were encountered: