-
Notifications
You must be signed in to change notification settings - Fork 41
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
Call to action #93
Comments
I am using this library pointing to the master branch to be able to use Tokyo v1 (Example) |
Hi, thank you for your care for the project. I am using the current master as well, and it would really be nice to get a release of that. I already thought about forking the project before, and maybe that's the easiest way to go forward, since @thedodd's time seems to be too limited. I myself unfortunately cannot promise any lasting time commitment either. However if there a few people who can accept pull requests such that any changes can be integrated faster, I would expect that interested parties will have a much better time improving things if they are lacking (including me, but still no promise). Maybe it makes sense if the three of us get the rights to merge pull requests, as well as review them? If we do it such that each pull request requires one review to be merged, that could work quite well. |
I think we have to fork it under an organization since we didn't receive an answer yet... |
Hey folks! I'm happy to invite some others as maintainers. Even if you can not make a long-term commitment, that's totally fine. @ISibboI & @ndelvalle would you like for me to send you invites? |
Thank you for the invitation! Let us aim to push out a release soon. |
Any update on potential release? |
Sadly, it has been sometime since the last release, I would like to keep this awesome project alive and to release a new minor patch (since we have the upgrade of mongo client and tokio which are fundamental to support the newer web services); I believe that this project should be put under an organizations with the main contributors to distribute better the workload.
Thank you @thedodd for the awesome work until now!
Thank you @ndelvalle and @ISibboI for the previous collaborations.
I would like to further discuss the future of the project with you.
The text was updated successfully, but these errors were encountered: