Project maintainer lacks commitment to project

tonysimpson / nanomsg-python

nanomsg wrapper for python with multiple backends (CPython and ctypes) should support 2/3 and Pypy

MIT License

382 stars 85 forks source link

Project maintainer lacks commitment to project #43

Open tonysimpson opened 9 years ago

tonysimpson commented 9 years ago

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:

references this issue;
updates the documentation and setup.py to reflect the new location of the repo and maintainer;
has some details of why you are motivated to maintain the project, how you are qualified and what you would like to improve, just a few bullet points will do.

Thanks all and sorry that I haven't been able to prioritize nanomsg-python myself.

vac commented 8 years ago

Well done @tonysimpson! It's not bad! I'm using your implementation in few projects, in production. nanomsg-python BUS is working fine, on Linux and Windows. In github space it's difficult to drop the project. If someone's fork is developed enough then I think it will be the right time to swap maintainer. Now, a year after your issue I see that you are still doing more in nanomsg+python than anyone else :+1: So don't be sorry and be proud - you wont be forgotten. Live long and prosper!

tonysimpson commented 8 years ago

Thanks, feedback much appreciated - glad to hear its working for you in productions.

chiradip commented 8 years ago

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.

aphor commented 8 years ago

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?

thatch45 commented 8 years ago

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. If anyone is interested in building a nanomsg transport for Salt I would be happy to point them in the right direction.

omani commented 7 years ago

Please do not stop to maintain this. Really appreciated!!!