Is project is dead? about socketstream HOT 8 CLOSED

I might be able to help to some extent, we're still using SocketStream in http://infinitewhiteboard.com/ (hobby/side project), and HTTP2 would definitely be a great addition in general.

from socketstream.

Hi,

I handed over the role of running the project to @thepian last September, as my year was going to be very hectic. In the past year I've just about finished writing a book for Manning publications about Cross Platform Desktop Applications, moved back to London from Amsterdam, helped support my girlfriend as she went through medical treatment this year, and done all of that alongside a full time job in a startup.

Thankfully the treatment is over and she is well, but it has been a really hard year, and I just wasn't prepared to try and squeeze SS in amidst all of that. I am slowly winding my way back into doing some OSS.

WRT is the project dead? I think it's a fair question to ask based on commit activity - the framework still works (amazingly SocketStream works out of the box on Heroku as they now support WebSockets), but lack of recent activity shows that there is a challenge here - how to keep the project going if no activity happens.

Simple answer is to generate some activity - make commits, fix bugs, write code, refactor code, write tutorials, answer Qs on Stack Overflow, you get the idea. Problem is how do you that alongside life in general? No one individual can do all of that alone, it's too much. You have to spread the workload, and you have to make it happen regularly. I think that Pieter Hintjen's book on social architecture is a really good read on this.

If someone wants to invite me back into the GitHub organisation (I rationalised them a few months ago to the ones I could work on actively at the time), then I will be happy to try and pickup a few items and get the ball rolling.

from socketstream.

It is certainly not dead, but I will have to spend a couple of weeks full time to complete what I set out to do with 0.5
We do have a version 0.4 which should be working. I guess there might be one or two things outstanding there, but I think it is as good as 0.3

Additionally I see HTTP2 as the future of real-time long term. It will work over proxies which websockets will not. That would require a lot of effort to figure out, but to stay relevant I think Socketstream needs to move the needle forward.

I hope the project can be a community effort though as I have no plans to treat this as a job.

from socketstream.

I have not seen a lot of movement on it lately, and I used to be much more active as a participant. @paulbjensen? @thepian?

I believe @thepian is the current project lead.

from socketstream.

I actually used 0.3.x branch in production and was satisfied with results, Now I'm starting another node rpc project from the ground and confused about SS as main framework - last commit almost 6 months ago.

from socketstream.

Currently, @thepian is the only one who can invite you back in (I'm only a member, not an owner).

from socketstream.

No. I'm back to help.

from socketstream.

I'll close the issue.

from socketstream.