Excerpts from Tom Link's message of Sat Jan 01 12:34:39 +0100 2011:
> > Bram was so kind adding me to the list of contributors to the Vim project 
> > which
> > means that I can propose Vim web page changes by sending Bram patches.
> 
> Great to hear.
> 
> >   A:a way to change the script type afterwards (because Bram had to do this 
> > manually using SQL)
> 
> Is the script type of any use at all as long as vim.org's search
> function doesn't work and we have to use google to search it?
Yes: VAM is using it to move /foo.vim into syntax,ftplugin or plugin
folder. Not all plugins have a proper archive containing a "subdir".
That's the only reason I know about. Whether that usage was
intentionally I don't know. It seems to work fine in most cases (for
those where its set wrong I override it)
 
> I'd say only one person should be responsible for maintaining the info
> on vim.org. But there should be a way to transfer that responsibility/
> maintainership.
So you're fine with what I proposed (only reply if I got this wrong)
 
> >   D:change the voting system this way:
> 
> If you actually plan to save votes on a per version basis I'd like to
> suggest to implement some sort of inflation (i.e., loss of value over
> time). E.g. older versions should IMHO have less weight when
> calculating the over-all value. This would also solve/attenuate the
> problem with downvotes for older versions. I think you'd only have to
> store one value for previous votes + a current one and then let the
> over-all value be something like curr + prev * 0.8 or so. And maybe
> multiply all kharma points with 0.8 every year.

For plugin versions? Bad idea. You can manipulate by doing version bumps
only (don't think Vim script authors will do so .. but )

by time? Great idea. Tools change. so 10 year old karma may no longer be
valid. But we should discuss which would be the best way.

So for now I'd like to keep the "old" (stupid ?) value unless more
discussion has taken place.

Maybe its best to show both.

> People will insert dummy text.
You can't protect against that.
spam? How to detect spam? Things like adding a 1x1 pixel input worked
fine in one case I know about. If it contains text a spam bot was used.
Do you think human spammers are a problem?

> There are tools to monitor page changes.
All right. So it should be low priority. Polling causes more traffic
though.
 
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

Reply via email to