Abandoned Plugins

[Perlkonig]

Is there a protocol for taking over abandoned plugins? I've issued a pull request, but the maintainer hasn't been active for a long time, and there are other open PRs. My plan was to wait a few weeks and then go from there. I just wasn't sure if there was anything somewhat "official" about how to replace a current plugin with a forked repo.

If not, perhaps a protocol can be developed and added to the guidelines?

Thanks!

[rhukster]

We have had to do this a couple of times. When an author steps away and becomes unresponsive, we actually forked it ourselves and switched GPM to point to our version.

Which repo is it? Maybe we can also try to find out if the author is just busy or has actually abandoned the project. Cheers.

[w00fz]

The only thing we can do is take down the plugin from the GPM repository if it's unmaintained and we notice it causes problems or has security issues. For taking them over the policy should be the same as GitHub guidelines which is of asking to the owner for transferring ownership of the plugin or at the very least to ask to get write access to it so that it can keep getting maintained.
If this still doesn't work then my advise is to fork the plugin and make it your own, then open an issue here letting us know all the routes taken to try contacting the owner and if we see the owner has just lost interest in maintaining the plugin then we will update the repository to point to your fork so that people can continue using it.

[Perlkonig]

Thanks. I added a PR to getgrav/grav-learn (#341) with a recommended formal protocol. It's always good to have these sorts of things in writing 😄 Thanks!