Better feedback mechanism for Vim plugin scripts?

[Hari]

I might reflect the feeling of some of the plugin authors here that it is hard to receive good feedback from the users. Feed-back here, I mean, something more tangible than the Karma rating. I was thinking that if there was a simpler way to leave feedback about the plugin scripts then users might leave a line or two about how the plugin could be made more useful; the only real method of leaving feedback is to mail the author -- a rather arduous task sometimes. Wonder, if anyone feels the same way? I can think of a one way -- perhaps, create a wiki page for each plugin and let users comment there, but its equally superfluous.

[Thomas Koch]

Please see the thread:
"Improvements for vim.org/scripts"

http://groups.google.com/group/vim_use/browse_thread/thread/94ba7d11455f6eeb/2852080108a33077?lnk=gst&q=improvements#2852080108a33077

and the wiki page:
http://vim.wikia.com/wiki/Vim.org_relaunch

I just need the time, to summarize the requirements, get an agreement
and start the design phase.

Best regards, Thomas Koch

--
Thomas Koch, Software Developer
http://www.koch.ro

[Tom Link]

> I might reflect the feeling of some of the plugin authors here that it is
> hard to receive good feedback from the users.

IMHO you could announce your plugin here and link from the vim.sf.net
page to that thread. (I don't know if the others would like that
though. I guess some wouldn't like more traffic on this ML.)

Or you could create a wikia page for your plugin I guess (maybe
somebody from the vim tips team could comment on that) and link to
that page.

To cut a long story short: linking from the plugin page to some easily
accessible forum/wiki would most likely increase the feedback rate.

[John Beckett]

Tom Link wrote:
> IMHO you could announce your plugin here and link from the
> vim.sf.net page to that thread. (I don't know if the others
> would like that though. I guess some wouldn't like more
> traffic on this ML.)
>
> Or you could create a wikia page for your plugin I guess
> (maybe somebody from the vim tips team could comment on that)
> and link to that page.
>
> To cut a long story short: linking from the plugin page to
> some easily accessible forum/wiki would most likely increase
> the feedback rate.

Sorry, but there is no way to get user feedback for scripts, except for the very
rare user who will express their view using whatever means is available. I think
email, to the author or the vim_use mailing list, is the best procedure. However, if
a user is not inclined, you won't get feedback.

By all means experiment: Put up a wiki page, describe a script, and invite comment.
My guess is that there wouldn't be any worthwhile feedback (it's a big and busy
world with a lot of competing attractions; there are over 1200 tip pages and over
2400 scripts). If a wiki page didn't have much worthwhile content after say three
months, I would recommend deletion of the page because we have too many unhelpful
pages already, and that makes it hard for editors to do maintenance, and for users
to find stuff. However, the wiki is open for any attempt to help Vim users, so give
it a go if you like.

Instead of an article on the wiki, you could consider making a user page. On that
page, you could describe any scripts you like, and invite comments on your talk
page. I'm a little irritated by three user pages created in the last couple of
months where it appears the user has no intention of contributing to the wiki; the
user page is simply a link to promote the user's web site. Of course we welcome a
user page with any useful content, or a user page for anyone who makes even a small
contribution; they are welcome.

If anyone makes a user account at vim.wikia.com, remember to enter a bogus date of
birth indicating you are older than 13, and preferably enter a valid email address
so you can be notified if a page you choose to "watch" is edited (such as your talk
page where someone might leave a comment about a script).

We have had a handful of pages created to describe a single script. After
discussion, it was decided to delete the pages (which had not been updated since the
initial creation). Instead, the information was assembled onto one "Vim scripts"
page that is linked to from the main page:
http://vim.wikia.com/wiki/Vim_scripts

There could a line under the description of a script, with a link to the author's
talk page, where readers could leave feedback.

John

[nico]

> Sorry, but there is no way to get user feedback for scripts, except for the very
> rare user who will express their view using whatever means is available. I think
> email, to the author or the vim_use mailing list, is the best procedure. However, if
> a user is not inclined, you won't get feedback.

Take a look at kde-look.org, addons.mozilla.org or freshmeat.net. They
all have comment systems and people use them. Feedback can be useful
for anyone using the script, not just the author.

[Marc Weber]

> a rather arduous task sometimes. Wonder, if anyone feels the same way? I
> can think of a one way -- perhaps, create a wiki page for each plugin and
> let users comment there, but its equally superfluous.

I feel the same. See my other posts.

Marc Weber

[Hari]

Just went through your other post. Like John B mentions, there are 2400 scripts, I believe a good portion of them might
be useful but its very hard to run through each one in the list, install it and see whether it really works -- this is the user
perspective (as nico mentions too). That is where a system of reviews for plugins might make things better. This simplifies looking for plugins that might be beneficial for the person while still keeping the authors motivated enough to keep updating the scripts. It helps the community overall in its attempt to make Vim more powerful and useful. Thomas's Wiki link has a comment that says, a simple thread that allows users to leave comments on the plugin might be the most effective way, IMO. It would be nice if things got underway with that effort.

Incidentally, I did look at Marc's "RunInBackground task" plugin long time ago. Had trouble on figuring how to use it. It seems
to me that these sort of plugins are important extensions to Vim's capabilities. We could open up separate projects on
certain desired "features" and assimilate contributions.

-Hari

[Marc Weber]

> to me that these sort of plugins are important extensions to Vim's
> capabilities. We could open up separate projects on
> certain desired "features" and assimilate contributions.

So each project will reinvent the wheel about:
* How to use custom mappings
* How to configure the system
* ... ?
No! We need to get one configuration sytem which is faster than running
input 10 times (that's what the sql plugin does... If you start that
interaction by accident you're screwed..)
We also need kind of know how transfer.
And this can be done best if everyone can see all changes if he likes.
Thus if someone adds a configuration script and someone else (working on
different "seperate feature projects") will notice it and propose using
the already existing stuff.

That's why I would like to see us using *one* mantained library where we
know the code works.. If I upload rubbish others will tell me so and
remove the code again this way only keeping scritps which can be reused
by many people to the benefit of us all!

If we don't change this I'll propably only continue using vim till
something else (such as yi) has matured.. But that's me. You have to
know what you want and need.

About run task in background: Could you just git clone
git://mawercer.de/vl_repo
or use the latest installer?
http://www.vim.org/scripts/script.php?script_id=1582

add the cloned directory to your runtimepath
(maybe adding a finish at the top of the plugin/vl_plugin.vim)

Then try
call vl#lib#quickfix#runtaskinbackground#RunInBGQFAW(['sh','-c','sleep 3; echo done'],{'onFinish':["let g:done=2",'cope']})

BG= bacground
QF= load result into quickfix
AW= autowrite
You can set errorformat by adding 'efm' : "php" or such to the dict.
(see the file /autoload/vl/dev/errorformat.vim). Yes, this should change
as well.

I was bored about quoting stuff that's why I'm passing a list of args
now. That's more cross platform and more convinient..

Tell me if it still doesn't work, please. It will try using python, if
that doesn't exist it will run sh -c "command" & to get the same
behaviour.. You'll need gvim and has('clientserver') for this all to
work.

Sincerly
Marc Weber