[RFC] Move templates to a separate repository

[aperezdc]

Maybe it would be a good idea to move most of the templates out to a separate repository, and keep only a small curated set in the plug-in repository. My reasoning is that:

• It would encourage people to make their own customized templates (which, at least for me, was the idea behind the plug-in creation at first).
• The additional repository could have every template contributed, like, ever. Users could cherry-pick the ones they want/need, or use them as inspiration for their own.
• The main repository would be kept small and no-frills.

We already allow a list of paths for the g:templates_directory setting, so having one additional directory with more templates from a different repository would not be a problem.

@muff1nman @Lyude: WDYT about this?

[muff1nman]

Biggest drawback I see is that it complicates getting started as you now need to clone two repos to get the full template set and setup the variable. Also who gets to decide which templates are important enough to go in the main repo? With that said, I haven't been using vim recently, so take my thoughts with a grain of salt.

[aperezdc]

@muff1nman: Good points, thanks for commenting! My take one those is:

• The minimum set templates could be decided by checking GitHub (and maybe a couple of places more) to see what are the most used programming languages, and provide templates for those in the same repository as the plug-in; moving the rest to a new one.
• For cloning the extra repository, I would make it work with Vim plug-in managers. If the extra templates repository is available, it would be nice that the plug-in could configure it automatically. The idea would be to make it as easy as possible.
• Also, I would expect that an user who has been able of configuring vim-template to be fetched by their plug-in manager, they will manage to add one extra repository if they want/need the extra templates.