allow rating scripts #48

Open
gmarik opened this Issue Oct 13, 2011 · 4 comments

Projects

None yet

4 participants

Owner
gmarik commented Oct 13, 2011

Rating: the vim.org ratings are fairly useless. Need something more like
http://ruby-toolbox.com/, something that can pit related plugins against each
other.

Owner
bronson commented Oct 13, 2011

Love this.

How would the rating be computed? The ruby toolbox heuristic of github watchers & forks doesn't work so well with vim-scripts... not until we're working with the original repos anyway, just just the mirrors on vim-scripts.

vundle and vim-update-bundles could submit usage counts every time they process a vimrc. With the user's consent of course. :)

moshen commented Oct 13, 2011

This is a great idea! Some thoughts:

  • ++ Ratings on the vim-scripts site ( a la MetaCPAN )
  • of clones of vim-scripts / original repos ( pathogen.vim for example )

  • I don't think this is available via the github apis
Owner
bronson commented Oct 25, 2011

@moshen agree, definitely #1. We need to make vim-scripts keep track of original repos before we can do #2, that's a tough problem.

Node just announced http://toolbox.no.de/ . Vim needs an entry in this fight!

The number of clones is not available via Github's API.

In order to reach some state like RubyToolbox there are a few other issues which we would need to think about:

  • Vim Bundles don't have things like a Gemfile to specify dependencies
  • Forks/Watches are not saying much about the bundle's popularity
  • Bundles which are available from Github by their respective developers should not be available via vim-scripts.

I think the main problem here is that vim-scripts is not a directory of all vim-scripts available but a mirror.
It's nice to have this mirror for scripts which do not comply with pathogen but its not a replacement for a complete listing like these toolbox sites provide it.

I am willing to work on this directory.

Ideally I'd like to see someone join me to stay motivated on the long run... ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment