-
Notifications
You must be signed in to change notification settings - Fork 486
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
New maintainer for this project #75
Comments
+1 |
6 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
Today an alternative solution is to use https://github.com/primus/primus which is well maintained and provide an interesting abstraction layer, with Redis support (official plugin). |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Any chance of a response on this from the existing maintainers? @rauchg? If the project could do with some help I'd be happy to volunteer. |
@hgcummings I'm planning a release for the coming week. Apologize for the delay. |
Thanks for the update @rauchg. Note that I wasn't just commenting because I'm impatient for a release. The offer still stands if you could use any help in the future. |
Thanks @rauchg. But I agree with @hgcummings: this project is important for many people, you'd better promote some additional maintainers. |
@rauchg any update on the release? |
@jdesboeufs @hgcummings would any of you two be down for helping coordinate the next release? I believe this also requires that we push new client and server due to the changes of namespace handling. |
Hi @rauchg. Yes, I'd be happy to help out. Just let me know what you need. |
+1 |
@rauchg do you know when you'll be able to spend time on this? Let me know if there's anything I can do to help. |
This is obviously a very popular, useful and important part of Socket.IO which has not been maintained for a while. Has Socket.IO considered appointing a new maintainer? It's a big hassle finding a combination of fixes from all the forks right now.
The text was updated successfully, but these errors were encountered: