-
Notifications
You must be signed in to change notification settings - Fork 748
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
Reviving Ratchet: Let's give Ratchet the love it deserves! #1054
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I have enough time to participate in the development of Ratchet, and we are currently using it. How should I participate in development? |
@clue maybe add write access to people who want to help ? like @userofjack |
I am Using it in my company as well, would like to help - at least a litte if i could :) |
I think that a lot of people would support this post, but no one knows about it, because everyone is used to seeing the message “last modified 3 years ago” and simply do not know that you are going to continue supporting overall this is great news and we are still using ratchet just start making changes or apply pull requests :) |
Since I saw the last commit, I thought it was abandoned. I'm deciding to integrate it into my company. They did a very good job! |
Ditto. Perhaps update the README with a reference to this thread. That will then also reset the last commit time. |
Thank you so much for all the amazing feedback we've received on Ratchet! We are truly grateful for the excitement and the offers to help with the development. Excited to use this momentum to move forward! 🚀
Please help us getting Ratchet up to speed by becoming a sponsor through ReactPHP, we're thankful for every contribution! ❤️ |
Also agree it's a good idea to link more prominently to this ticket, I've updated the readme for the next couple of weeks and will continue posting more updates as soon as possible! |
I just cancelled an old GitHub pro account that was never used. Using that money to sponsor this one. Also let me know how to contribute. |
Sorry to cross over but https://github.com/ratchetphp/Pawl is in exactly the same boat. My company uses Pawl specifically and it's to the point where we're ready to maintain our own fork instead if that official repo is truly unmaintained. To that effect I can participate in development on either Ratchet or Pawl but would like to get an idea of what's going on with Pawl specifically if possible. |
May be it's a good idea to join source an make a common version that's client and server in the same project? |
In a way that is already done in https://github.com/ratchetphp/RFC6455 for the websocket protocol used by both |
The existing repository structure makes sense; RFC6455 defines agnostic components that anyone could use in their Server/Client implementations. These components are separate from the implementations themselves. Pawl is purely an issue of not having any maintainers at the moment. |
|
I look forward to it becoming part of the reactphp middleware, so that it can work together with reactphp/http or framework-x. It is very useful to provide both http service and websocket service on the same port, especially when http and websocket are related, as they are in the same process. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Hello, is there any progress on the revivification of Ratchet? I would like to participate and contribute. |
Ratchet is a great piece of software and it is successfully used in countless projects! But let's be realistic: It could use some love!
At the moment, we're making very good progress with ReactPHP v3 (see e.g. reactphp/event-loop#271) and Framework X. As a next step, we want to achieve the same level of velocity for Ratchet. Supporting the latest PHP and PHPUnit versions feels like a good starting point to bring Ratchet back to speed again, followed by tackling the huge pile of open support requests. So in a gist, we know what to do with Ratchet, the problem is that we have to find the time to actually do it. I've also reached out to the other maintainers, but before spending too much time on the details, I would like to see how much demand there is to work out a sustainable plan for the longer-term development.
As a first step, help us figure out demand by leaving a comment or an emoji reaction:
The text was updated successfully, but these errors were encountered: