-
Notifications
You must be signed in to change notification settings - Fork 49
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
Potentially add additional maintainers #30
Comments
Thanks for the note @LovecraftianHorror! And apologies to all for my lack of activity here. I'd be happy to add additional maintainers. I had at one point attempted to merge the blocking and non-blocking work together, but didn't have enough time to finish / reduce some of the duplication. I've added you to the repo! |
No worries! Life has a way of keeping people busy at times I'll take some time this weekend to get things more up to date |
Great, thank you so much! |
Great, thank you so much! At least to start, I'd like to review any changes. |
Alright so just to give some insight on the direction I'm going currently. My current goal is to
After that I can work on some additional cleanup and work towards potentially exposing an async API alongside the current blocking one |
Perfect, that sounds like a great plan! |
Apologies for the ping @compressed. I'm assuming you're busy again. If you don't have time for on-boarding additional maintainers then you could give me or rust bus crates.io privileges to keep things moving |
It looks like this crate has fallen out of maintenance for the past couple of years leading to
slack-hook2
andslack-hook3
which both mention in their README's that they are happy to merge the changes back to here in the future.If maintaining this crate is too time/effort consuming then you could add me (and/or others) as maintainers to spread the load across multiple people, and keep this crate more up to date
The text was updated successfully, but these errors were encountered: