Is there a policy for changing the source repository for a package?

[abingham]

It looks like the author of "request" has stopped responding to pull requests, issues, etc...he seems to have stopped paying attention to the project. But there are a few important changes that need to be merged into the project. We can of course fork the project and apply the changes, but that doesn't help users of melpa et al.

So do you have a policy for changing the source repo for a package? I don't know if this will necessarily need to happen (though I'm pretty confident), but I want to get a hand on what needs to get done just in case.

[purcell]

Yes, we strongly prefer not to switch over to forks simply because the maintainer has been unresponsive for a few months: it's the maintainer's call whether particular changes are important, not MELPA.

In this case, @tkf has still been active throughout the year, and is probably just a bit overworked to handle these changes right now. So I'd suggest to @tkf that he might consider giving you or others commit permission so that you can apply the fixes. Alternatively, he could choose to appoint you as the new maintainer, then we would be happy to use your fork.

[milkypostman]

@abingham if you contact @tkf and work things out let us know in a new bug.