Closed ioquatix closed 2 years ago
I hope this proposal is accepted. This project is not really unmaintained, but it deserves more love than it's getting, and it absolutely should be kept in sync with any important changes in Rack.
Sounds good! @rtomayko is the only one who can move it though
cc @tenderlove
Any updates on this? Improved maintenance would be nice.
I emailed both @grosser and @rtomayko but did not receive any reply.
I'm going to suggest we fork this repo to then rack org. If @grosser is on board with this, can you please add myself as an owner of the gem too so we can handle release management? Thanks!
need your rubygems email
... also there are no issues or PRs here, so doubt this will have much impact 🤷 but better there then here ...
@grosser can you DM me on twitter? @ioquatix
worked via username too :)
On Mon, Feb 21, 2022 at 10:29 PM Samuel Williams @.***> wrote:
@grosser https://github.com/grosser can you DM me on twitter? @ioquatix
— Reply to this email directly, view it on GitHub https://github.com/rtomayko/rack-cache/issues/165#issuecomment-1047468063, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAACYZ6EGQ2OUMDER55QOX3U4MUOBANCNFSM4NI2BDRA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
I've just asked other maintainers to let me know if there are any issues with forking this repo to the rack org. If not, I'll do it later this week.
I've made a temporary "detached" fork https://github.com/ioquatix/rack-cache which I'm going to use for testing, and I can move this to the rack org later. I'll add you as a maintainer.
Hi, it looks like it could be great to move this repo to the rack for for shared maintainership.
Let me know if that's something you are interested in.
We'd still want you to have ownership over the project, but we'd also like to help move it forward w.r.t. the coming changes with Rack 3.