-
Notifications
You must be signed in to change notification settings - Fork 85
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
Project maintainer lacks commitment to project #43
Comments
Well done @tonysimpson! |
Thanks, feedback much appreciated - glad to hear its working for you in productions. |
I am tempted to take the responsibility but need to sort out my responsibilities. I almost replaced ZeroMQ by nanomsg in one of my big products. You did a great job - please do not abandon it before somebody volunteers to be the new maintainer. |
SaltStack is experiencing some growing pains WRT 0MQ. I don't really know enough about the 0mq failure modes in their massive-scaled clients, but since they've decided to try and abstract transports, I found nanomsg interesting. Maybe there is a future? |
While I really like the nanomsg project, the approach that we have taken for SaltStack is to implement the queuing networking system ourselves in python and using tornado coroutines. This approach is much harder than just using 0MQ but it has allowed us to optimize the communication for our specific needs and makes it easier to view the whole stack. |
Please do not stop to maintain this. Really appreciated!!! |
Filling this issue against myself :)
A new maintainer is required for the nanomsg-python project as the current maintainer has no motivation to do so.
I still feel that nanomsg is a promising design but at this time I don't have any projects I will be using it on.
If you would like to take over as maintainer please raise a pull request which:
Thanks all and sorry that I haven't been able to prioritize nanomsg-python myself.
The text was updated successfully, but these errors were encountered: