-
Notifications
You must be signed in to change notification settings - Fork 222
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
ws-rs fork #315
Comments
I'm sorry, I hope it's been clear that I haven't been able to maintain this project recently. I've brought the site down. I support any attempt to maintain or support this project, and I hope that I can get back to it at some time. Rust has come a long way since I've had to step back; I think there is a lot people can do with this code if they want to. Best of luck to everyone! |
Hi @housleyjk! Zero need to apologise and no need for any further explaination IMHO. It's a great project and am sure everyone here is very grateful for your work! Thank you ❤️ |
can you put the ws-rs.org docs on this github project? |
I don't think there is a need for a fork, perhaps @housleyjk can just add some new people to the repo as maintainers. |
@Jash11 yep, this was only because we hadn't seen any updates from @housleyjk in a while |
@housleyjk the documentation can be placed in the repository and hosted on github pages |
@Jash11 Yes, I am happy to add maintainers. I think I added one a year or so ago. @jprochazk I've committed the current state of ws-rs.org to https://github.com/housleyjk/ws-site if you want to try to convert that to something that will run on github pages. |
Who will be the new maintainers? I suggest the 3 people who have the most commits. You can also perhaps post on the rust subreddit that ws-rs is looking for new maintainers. |
@housleyjk I converted most of https://ws-rs.org/ to markdown, which can run on github pages. The pull request is awaiting review. For now, anyone who needs access to the website can do so through my fork on github pages https://jprochazk.github.io/ws-rs/ |
Is it possible to add one of the new maintainers to the crates.io crate so the name doesn't have to change? |
@housleyjk: Today I stumbled upon this crate and I really like the design of it. It fits my use case perfectly! :) So far no new maintainer was found, is that correct? If so: Would you be able to create a post on the forum and on the sub-Reddit to find a new maintainer? I think it would be best if you would do this. If that isn't an option (time-wise): Would it be okay if someone else creates a post like that? And – if a new maintainer is found – will you add him or her to this repo and to the crates.io package? I think it would be a real pity if this crate would be discontinued. At the moment I'm working on a (for me) complex crate, therefore I don't have the needed time to maintain this package myself (and I probably also lack the needed skills... :)). But maybe someone else can be found. As I wrote, it would be a real pity if not. |
@housleyjk I saw that you made a release in April. Are you planning to continue to maintain this crate to some extent and are you accepting pull requests? |
If I have time, yes, I will try to maintain this crate "to some extent," but I would say that extent is not very big right now. I don't want you to waste your time, but you are always welcome to send PRs whether I look at them or not. |
Given that we haven't seen any activity from @housleyjk in a few months leading to a number of stuck PRs, and now the website's down, I think it's time a fork is planned.
Could we please get comments from @little-dude, @Eijebong , and @bluetech, as they have the highest commits to the project.
What I'm thinking is a simple fork of something like
ws-rs2
as a crate name, merge all the commits that the community are happy with, and continue there from now on. If @housleyjk pops up again in the future, happy to go back to the originalws-rs
or pass on ownership again.Thoughts?
The text was updated successfully, but these errors were encountered: