And we should push vim-pi because we want vim-pi to be the place to discuss vim distribution in general. vim-pi wants to be open to linux distributions and systems like npackd. Nobody did it yet - but we could generate debian/gentoo/nix/... packages. The main issue why we didn't is amount of work - lack of interested - but we have some discussions going on. vim-pi wants to standardize plugin installation, too. 

Eg have a look at : https://bitbucket.org/vimcommunity/vim-pi/issue/95/proposal-declarative-extensible-cross

Anyway: neovim (and lack of intersest) a reason to suspend all work. We should wait and see what's going to happen. Thus please join such discussions - so that we can make NeoBundle, vundle, and VAM have the same interface, such as "Script name, {opts}". - some managers would support some opts, other would not. But in 80% of all simple cases it would just work for all users.

Also compare this: https://github.com/honza/vim-snippets/pull/307
This is one of the reasons why I started that effort - more and more plugin managers get written (see vim-wiki), and making all users have dozens of install instructions doesn't make sense.

That's one of the reasons why I want to "ignore stars" and try pushing the "better solutions". I agree that what is a better solutions depends on personal view. In this case its minimizing overall work and duplication.