wish this was still in active development :/

[bthibault]

No description provided.

[veebs]

Sorry mate. Unfortunately, my work is taking up all my time. If you or someone else like to take over the project ... let me know.

Thanks

[simbo1905]

+1 for someone picking things up. the couple of open issues about memory leaks look serious but other than that keeping up to date with other libs would keep the ball rolling forwards. web frameworks are notoriously bloatware so the small and mighty socko is a breath of fresh air.

[bthibault]

If you look at the forks @mubarak from @layerhq have made quite a few updates... maybe they are interested in taking over.

[simbo1905]

I recently moved my TRex project into a new GitHub account setup as an organisation so I could add someone else as an administrator to closely collaborate with them.

I am willing to move my three socko demos over to a new org to help on testing merges of features by other devs. I can also setup travis, gitter, codacy, GitHub pages and other integrations and port articles and docs and start a wiki etc.

The community should choose to focus on the one repo with current docs and more people running the builds and contributing for the mutual benefit of all.

A small number odd number of admins/committers (3, 5, 7) should work as a vote won't be split: and @veebs would be the deciding vote as Beneficial Dictator For Life.

So I propose the three of us to be the initial admins of a socko GitHub account. If those other two folks want to be committers we could decide that by majority vote of the current committers. We can setup a public gitter chat room and conduct all matters in public there.

What do you think?

[simbo1905]

... the first matter beyond setting up the new account would be inviting those forks to merge back into the org codebase to pull the community back together.

[bthibault]

+1

[simbo1905]

@veebs you okay with me setting up a socko account on GitHub and adding you and bthibault as admins then forking the repo here into that as the new "official repo"? To get the community to follow you could put up a notice on the readme in this repo to say that the concept is to bring more people onboard and take things forward. hopefully there will be enough interest for socko to get it a life of its own where you can offer advice and input when you have the time.

[simbo1905]

... the second matter beyond the above would be to setup some milestones and assign some tickets to milestones like merging back forks and the various issues raised so far here. we could ask folks if their are feature they want or upgrades and get folks to vote on them.