Skip to content

Maintenance Proposal #187

@chrisidakwo

Description

@chrisidakwo

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions