Re: Poll: What's good about plugin managers?

> dowvoting due to "textfile"
The main issue is "lack of interaction". Getting down votings for unkown
reason is bad for everybody. So this hurts a lot IMHO. issue trackers
are a lot better, because they create a soft force improving /
documenting the issues.

The text file contains:

linux:
See https://github.com/MarcWeber/vim-addon-manager/blob/master/doc/vim-addon-manager-getting-started.txt
section 2, recommended setup. Then VAM will git clone itself on startup.

I'd still do it the same way today.

The main issue is that plugin maintainers have to care about
- vim.sf.net install intstructions
- README
- doc/*
documentations today. That's one thing gmarik (vundle) got right: Having
a nice shiny README file.

> But vim.org needs work.
Bram should reply to the question whether he would allow a different
hosting. eg vim.sf.net in the past suffered from not being able to send
email.

There have been at least 5 people during the last 3-5 years who would
have spent time on the "next vim.sf.net", but due to hosting it was hard
to find a nice scalable solution.

About github vs vim.sf.net: The best thing would be allowing @
vim.sf.net to just register a github url *and be done*.
vim.sf.net could then just forward to github generating a .zip file for
download.

Simple change, but huge benefit - it would solve almost everything.

Its Bram who should speak up - we've had quite a lot of "private
messages" in the past - but hosting was the bottle neck IMHO that time.

> There is no consistency in versioning.
But is this really a problem in the common case?
Usually you use the latest version, and if upstream differs from what
you want you're likely to fork anyway (IMHO).
The common case is likely to work - and most authors take care and fix
issues in a couple of days.

> There is no support for linking to some repository or issue tracker,
> again, it needs to be given in prose.
I'd say that bitbucket, github work reasonably well, if there was a way
to say "this plugin is hosted at github" those links could be derived
and displayed easily.

> Finally, and that is the crux, there is no API.
You're wrong. I patched vim.sf.net to return a huge json dictionary
containing all plugins. See vim-pi code. Maybe the API is not perfect,
just enough to make vim-pi work reliably.

Marc Weber

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.