Low maintenance activity?

[mshibuya]

@jasdeepsingh and other authors/contributors

Hello guys, I'm @mshibuya a maintainer of the CarrierWave project.
Looks like this project carrierwave-google-storage is not so actively maintained. It's sad for me, because I think this project deserves more attention.
As the CarrierWave project, currently I'm thinking of the possibility to move away from the Fog gem. Fog comes with a lot of features that CarrierWave doesn't need, and the maintenance status is not so ideal (varies among cloud providers). So the idea is to encourage users to use CarrierWave integration libraries, which depends on not Fog but the cloud provider's official libraries, just like carrierwave-google-storage does.

Hence here's my question, is there anything I can help to maintain this project? If you're fine with it, I'm willing to become a maintainer to support managing dependencies and releasing. Or in case you don't have enough bandwidth to keep maintaining this, it may be worth considering transfer of the maintenance ownership to the carrierwaveuploader organization, just like what was done to carrierwave-aws.

Thank you for your attention, looking forward to hearing back from you!

[jamalawd]

@mshibuya, Thank you for the initiative, and I hope the owners agree with you on ways forward. I am currently using this gem in one of our production ends. Still, due to its low maintenance state, I had to fork it and make it compatible with ruby > 3 and do some small custom changes, but we were about to deprecate it along with carrierwave gem and use the official google gem with a simple in-house handler. However, we would be glad to keep using it for the benefits you mentioned if it takes some attention.

[jasdeepsingh]

@mshibuya Our team at Metaware is currently very busy and do not have the bandwidth to actively maintain this project. We are more than happy to transfer maintenance ownership of this project to Carrierwave org.

Let me know what steps are required to organize them.

[mshibuya]

@jasdeepsingh Thank you for the quick response, I really appreciate it!
For the transfer, the steps will be:

1. I've sent you the invitation to carrierwaveuploader organization. It's needed to allow the repository transfer, please accept.
2. Then you can take the the repository transfer process.
3. Finally, please add my rubygems user mshibuya as a gem owner, by using Rubygems UI.

That's it. If there's anything unclear, please let me know 🙏

[mshibuya]

@jasdeepsingh Hi! I know you are busy but is there anything I can help?

[jasdeepsingh]

@mshibuya Sorry for the delay on this, I was away and quite busy. I'll have this organized today.

[jasdeepsingh]

@mshibuya Looks like the invitation has expired, can you resend please?

[mshibuya]

Re-sent the invitation and I saw you accepted it.

[mshibuya]

@jasdeepsingh Hi, how's going with the Rubygems ownership? 😃

[mshibuya]

@jasdeepsingh Are you still busy...?

[mshibuya]

@jasdeepsingh
Sorry for pinging repeatedly, but only remaining is just one step 🙇
Please add my Rubygems user mshibuya as an owner of the carrierwave-google-storage gem, following this guide!
https://guides.rubygems.org/managing-owners-using-ui/

[niborg]

Looks like this repo is behind on Ruby gems, e.g., change here lightening some dependencies has not been pushed to RubyGems, requiring I specify git in my Gemfile.

@jasdeepsingh if you have time can you kindly add @mshibuya as RubyGems owner?