Is anyone in the community maintaining an active fork?
deg0nz opened this issue · 8 comments
Hi @ll,
I was wondering if anyone who has forked this repo is actively maintaining their fork to add new features and make bugfixes. The project seems abandoned to me (the last merged PR was almost 2 years ago).
My main goal is to bring goji to async. Maybe I could just implement it and make a PR.
If not, I'm thinking of making a fork that is more or less actively maintained. I'm usually a little short of time, so it would be nice if someone would be willing to co-maintain the fork (help to take care of PRs and so on). I would also try including all the open pull requests.
BR
Beh
@deg0nz, I maintain my fork as it's a dependency in a project I support which requires generic serde Issue types, just haven't bothered submitting a pr since it looked like it wasn't maintained. But I'd be willing to merge and help with maintenance (since I'd definitely be merging your async feature anyway).
@softprops, would you be willing to add collaborators to goji?
Hey, @krscott
I maintain my fork as it's a dependency in a project I support which requires generic serde Issue types, just haven't bothered submitting a pr since it looked like it wasn't maintained.
Exactly the same here. I also added custom issues and bearer authentication.
@softprops, would you be willing to add collaborators to goji?
I would also appreciate if that were possible :)
@krscott @softprops @deg0nz - I'm just did the same. I would happily open PRs somewhere else if there was consensus on a single repo being maintained.
Same for me. I started to merge in from the pull requests and forks. But will not be able to maintain it myself.
I am possibly also forking this project to work on top of it. There is a high chance I will work on it from time to time over the year. I would be happy if anyone can take an iniative to create a fork in a new organization.
I've created so far an organisation and pulled in much of the work around.
Would be happy to use this as a starting point.
That's very nice. Thank you @avrabe!
But just 1 question: Should we make a hard fork, so that issues can be discussed over there at wunderfrucht? I think it could be quite confusing if issues are handled here, since no one is actutally able to manage issues.
I think it would also be nice if gouqi would be released as a new package on crates.io.
@avrabe I think you can also add me and @krscott as collaborators if you like. I myself will try my best and support the maintenance of the new repo.
Edit: Awesome naming choice, btw ;)
I'd say we'd should to the hard fork to have things clean and we can continue now further on the new repository.
On creates.io I've released today a first version and now it can be further improved ;)