Skip to content
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

Open
clue opened this issue Feb 7, 2024 · 15 comments
Open

Reviving Ratchet: Let's give Ratchet the love it deserves! #1054

clue opened this issue Feb 7, 2024 · 15 comments
Labels

Comments

@clue
Copy link
Member

clue commented Feb 7, 2024

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:

  • 👍 Like the idea, generally interested
  • ❤️ Love the idea and would consider sponsoring further development of Ratchet
  • 🚀 Ratchet is used in our company (let's have a chat!)
  • Anything else, please join the discussion!
@clue clue added the question label Feb 7, 2024
This was referenced Feb 7, 2024
@clue clue pinned this issue Feb 8, 2024
@dvdknaap

This comment was marked as off-topic.

@SimonFrings

This comment was marked as off-topic.

@userofjack
Copy link

I have enough time to participate in the development of Ratchet, and we are currently using it. How should I participate in development?

@neoteknic
Copy link

@clue maybe add write access to people who want to help ? like @userofjack

@mkrasselt1
Copy link

I am Using it in my company as well, would like to help - at least a litte if i could :)

@igorbelikov
Copy link

igorbelikov commented May 5, 2024

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 :)

@rperdomoalhc
Copy link

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!

@johnrix
Copy link

johnrix commented May 7, 2024

Since I saw the last commit, I thought it was abandoned.

Ditto. Perhaps update the README with a reference to this thread. That will then also reset the last commit time.

@clue
Copy link
Member Author

clue commented May 13, 2024

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! 🚀

  1. First we need to get the project up to date with the latest versions, so this is something I personally would like to work on first. Once this is completed, I would love to get more people involved, so we greatly appreciate any help and contributions.

  2. Right now, we are finalizing the project handover with @cboden and hope to get the project up to speed again as soon as possible. In the meantime, we also work on a number of other bigger open-source projects like @reactphp (which Ratchet builds on top of) and need to balance our priorities and find adequate project funding to allow us to keep shipping.

  3. You can help us! For now, I would like to set up a simple sponsorship goal of reaching 10 new sponsors (any amount) to see how much the community is willing to support this project. Once reached, we will start pushing the next PRs to get Ratchet updated to support the latest PHP and PHPUnit versions and use this as a starting point for bigger updates to come. Even just 10 x $1 would help achieve our initial goal, but the more sponsors the better obviously, so especially curious about any company sponsors reaching out!

Please help us getting Ratchet up to speed by becoming a sponsor through ReactPHP, we're thankful for every contribution! ❤️

@clue
Copy link
Member Author

clue commented May 13, 2024

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!

@newmediacrew
Copy link

newmediacrew commented May 14, 2024

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.

@whoisninjaturtle
Copy link

whoisninjaturtle commented May 21, 2024

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.
Thanks

@mkrasselt1
Copy link

mkrasselt1 commented May 22, 2024

Sorry to cross over but https://github.com/ratchetphp/Pawl is in exactly the same boat.

May be it's a good idea to join source an make a common version that's client and server in the same project?

@WyriHaximus
Copy link

Sorry to cross over but https://github.com/ratchetphp/Pawl is in exactly the same boat.

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

@whoisninjaturtle
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests