> Removing the maintainer is fine for me so I will merge the patch.

Sure, we can't force the maintainer to stay.

But as it's a forked plugin nobody would maintain, we might want to consider 
removing it altogether instead of getting an "unmaintained version of a 
maintained plugin" as @techee rightly put it -- which, if it stays that way 
long enough, is rather counter-productive as many people would use an outdated 
version of the plugin while they could use the upstream one (which indeed has 
less visibility than the already established GP, but could be used/packaged 
just fine -- or so I hope).  Maybe just list "this plugin can be found at 
[URL]" in a directory named after the plugin and voila, at least until that 
#440 thing got sorted out.
Just some ¢2.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/435#issuecomment-227282773

Reply via email to