Looking for maintainer(s)

[Taluu]

Hello all,

As we are not using Elephant.io anymore (or almost...) at Wisembly, we are not developping it anymore except on our free time when we have any, which has become kind of difficult these past few months.

To help the library to grow (features wise, bugfixes, releases, support, ...), we are looking for someone who could maintain this library and give lots and lots of love.

If you are interested, please shoot a message in this issue ! :}

[daslicht]

may I ask what you are using now ?

[guillaumepotier]

Hi @daslicht, we use now RabbitMQ to tell our push server what to broadcast. This is easier, faster and less cpu consuming. Here is the article I wrote about that

Best

[daslicht]

Thank you very much for the reply !
So with RapidMQ you can also have continuous running process' serverside ?
I apologize for the off topic, but I am to excited :)

[guillaumepotier]

So with RapidMQ you can also have continuous running process' serverside ?

Not really :) RabbitMQ is a running process where you store messages that could be consumed by other running processes (called consumers) but yes, result is quite similar. Its based on AMQP please have a look. Best

[ncrypthic]

Hi @Taluu, may I know what technical requirements you expect for a maintainer? I'm interest to maintain this library because I use socket.io alot.

Cheers!

[Taluu]

Hey @ncrypthic, basically you need a good understanding of the websockets RFC (https://tools.ietf.org/html/rfc6455 if my memory serves me right), a good understanding of OO in php I guess (but nothing too deep though), and also how to use sockets, streams, etc in PHP.

I think you'll make a better idea for yourself looking at the current code. :}

[jens1o]

Is this still up to date?

[Taluu]

The offer is still on the table, yes. :}

[jens1o]

Hmm... I'll think about it, since I love this library and it's working good. I think I have enough knowledge, but it's a huge job maintaining libs. (I saw this issue in the morning while I was updating the dependencies.)

[Taluu]

If you need anything, start by making some contributions, it should help you assessing what needs to be done when maintaining a package :}

[jens1o]

Okay, thanks. But at the moment, I'm fine with the possibilities I have. 😄

[DeveloperMarius]

Hey,

I am not sure and do not speek for the person, but the https://github.com/tohenk/elephant.io fork seems pretty up to date. Maby he is interested?
@tohenk

[Taluu]

If he wants to give it a go, I'm open to give him a try. :}

[Taluu]

(Even though TBH it would be best to make his own fork (or an elephant.io organization ?), so we can mark the package a abandonned in favor of the new one)

[tohenk]

Okay, count me in.

[Taluu]

Okay, added as a maintainer for now, until the repo / orga is made if you're up to do that. :)

[tohenk]

I need a confirmation, should we create new organization or stay at wisembly? If we need create the organization, what we should call it, Elephant.io maybe?
The next plan, the 3.x version will be archived and I will push my changes as version 4.x.

[Taluu]

AFAIC, I think it would be best to have a custom organization (such as the one you are proposing). But then, I guess it's up to @guillaumepotier, who is the owner of the Wisembly organization to decide at that point, if he wants or not to keep it here.

Feel free to archive the 3.X version. :)

[tohenk]

Hi everyone, new organization for Elephant.IO is https://github.com/ElephantIO. I hope everyone can help me maintains the project. Please contact me with your email address so I can grant you access to those repository.

[Taluu]

It would have been better to wait for @guillaumepotier's input so he could move this repository (to keep issues and pr history), but this is also fine.

I'll make an update on the README (and composer) when I'll have some time to do so (probably within the week).