So, this project is a ghost ship. Is it worth creating a fork? Has anyone already done so?

[prolixalias]

Hesitate to participate in a project that's as neglected as Vundle.vim... If there's an active fork I'd really like to contribute. Feedback welcome and appreciated.

[davidlowryduda]

I'm not currently aware of an active fork. A while ago I tried to take over (or rather, get added as a maintainer) of vundle, but no one with permissions to enable that (maybe exclusively gmarik) is active.

Between then and now, many things have happened.

• vundle's more featureful descendant vim-plug has grown in popularity.
• Vim 8 came out with a default package manager (:h package). This is more similar to pathogen than vundle, but it's not really that different.
• A number of plugins that require other commands on startup came into existence and people wanted these commands to automatically begin upon sourcing their vimrc (which vundle doesn't support).

[prolixalias]

@davidlowryduda - that's the most concise and helpful response I could imagine. I'll look for VIM solace elsewhere. Thank you for all the detail -- it's much appreciated.

[stefanlasiewski]

I just switched from Vundle to vim-plug and it only required minor edits to my .vimrc.

But if Vim 8+ natively supports packages, I might end up switching to that entirely.