speed-type
speed-type copied to clipboard
Maintainer handover -> MELPA now points to parkouss/speed-type
MELPA is now pointing here...
https://github.com/parkouss/speed-type
@hagleitn - if you'd like to make any updates, please let us know and we'll work it out.
+1 - I created a fork on wich I maintain a version updated with most of the pr availabre since there is no response here... https://github.com/parkouss/speed-type
Maybe we should create a speed-type 2 or something?
I think that's the best way forward.
@purcell what's the MELPA policy (if any) on unmaintained packages?
When packages become unmaintained, I ask potential new maintainers to first contact the author and offer to take over (as per this issue). If the original maintainer is unresponsive for a good while (as appears to be the case here), I'm happy to switch the MELPA recipe to point at an fork made by a motivated new maintainer, with no renaming necessary.
@purcell Thank you Steve. We will figure out what happens next.
I'm happy to take on the project, it's fairly low maintenance.
@parkouss would you like to maintain?
I'm happy either way.
@jasonm23, sorry for the late answer; I'll be happy to maintain it, yes! If I understand well, for the melpa side, all I have to do is create a fork, change the speed-type recipe (https://github.com/melpa/melpa/blob/master/recipes/speed-type) and make a pull request.
So I propose to do that with my current fork of the speed-type project. What do you think?
Sorry for the late response, I emailed the reply two weeks ago and it didn't get picked up.
Basically thumbs up full steam ahead.
Please open up issues on the fork.
Done! there is a new melpa package available. Not sure if I should close this issue, it might help to keep it open so people can easily find the new repo url: https://github.com/parkouss/speed-type
I've updated the title. Let's leave the issue open for visibility.
Go here ...