unicodeveloper
commented
2 weeks ago What are the recurrent issues?
Can you point me to some of the PRs or issues needed to be in?
Depending on the PRs, I can add you as a maintainer so you can also review and merge
Best Regards,
Prosper Otemuyiwa Co-founder, Eden @unicodeveloper https://twitter.com/unicodeveloper | prosper.otemuyiwa1 ( Skype )
On Wed, Jun 19, 2024 at 11:44 AM Chris Idakwo @.***> wrote:
ATTN @unicodeveloper https://github.com/unicodeveloper. This is a proposal for maintenance.
Firstly, thanks for this library. It has definitely done a lot of good for the community. But I see that you might be having a little challenge with maintaining, extending, and responding to issues. I would love to assist with that.
I've used this package a number of times within last year and this year and I've always found myself having to clone it just so I can quickly build specific features which I also see some devs requesting for and I believe should be available on the package.
I'd love to get a response on what you think about this. I mean I could easily just fork the project and build upon it without having to write all of this. But I think it's best to do that on the original project itself.
I'm very much active with PHP and Laravel and don't see that changing anytime soon. Hence, you can be sure that I'll always be available to get the project active.
— Reply to this email directly, view it on GitHub https://github.com/unicodeveloper/laravel-paystack/issues/187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWPNUJ75JVAYVP2AXW3G4TZIFOI5AVCNFSM6AAAAABJRZO2ACVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DEMBSGIYDONA . You are receiving this because you were mentioned.Message ID: @.***>
ATTN @unicodeveloper. This is a proposal for maintenance.
Firstly, thanks for this library. It has definitely done a lot of good for the community. But I see that you might be having a little challenge with maintaining, extending, and responding to issues. I would love to assist with that.
I've used this package a number of times within last year and this year and I've always found myself having to clone it just so I can quickly build specific features which I also see some devs requesting for and I believe should be available on the package.
I'd love to get a response on what you think about this. I mean I could easily just fork the project and build upon it without having to write all of this. But I think it's best to do that on the original project itself.
I'm very much active with PHP and Laravel and don't see that changing anytime soon. Hence, you can be sure that I'll always be available to get the project active.