Thomas Koch wrote:
> by revising my .vim dir and creating a list of usefull vim scripts for > my collegues, I started thinking about vim.org/scripts. Let me assume, > that the many high quality scripts are a very important part of vim, > which makes vim the almighty tool you use every day. > > Then the quality of vim in a whole depends on the quality not only of > individual scripts, but also on the ease of installing, updating, > maintaining and finding scripts. > > The current vim.org/scripts site seems to have several critical flaws, > IMHO: Overal good observations. A few comments below. > * you won't get informed of updates for your scripts My personal preference is not to get interrupted by "new thing available" messages. They mostly distract me from what I was actually doing. Typing some command to check for updates is usually more convenient. And as others noted: this already exists. :help getscript. > * collaboration on script development is next to impossible, because > * I can't upload a new version, must open a new script page > * No script I saw is under version control > * Many scripts lack licence informations > * scripts can not be browsed online, there are only downloadable > zip/rar/tar.gz/vba/vim > * User Feedback on scripts is not possible: no comments, mailing list to > much a barrier > * No issue tracker Currently nobody is actively updating the PHP and MySQL code of www.vim.org. I've been fixing problems, just because nobody else does it. It would be great to have an active maintainer again. Note that this requires knowledge of: - PHP - MySQL - security issues - spammers Especially the "add comment" feature will be sensitive for spamming. I also suspect we need to make the creation of a login more safe, it's only a matter of time until a spammer writes a script to work around the current simple procedure and starts uploading garbage. > Do you agree with me on this points? Should we do something about it? > Should we do build a better vim.org/scripts? Who would like to join the > effort? > > Things that could be done: > * save scripts in a VCS This doesn't need to be on www.vim.org. You can do it on any separate site and only upload the result to www.vim.org. That gives a much more convenient way to control access for each script separately. > * add a webforum to each scripts page > * add an issue tracker This can also be separate. A link from the description would be sufficient. > * add OpenId to vim.org > * politely inforce a default licence for scripts > * allow people to upload patches to scripts they have not initially > created Some way to take over maintenance would be best. With some way to make clear at what point it was taken over. -- hundred-and-one symptoms of being an internet addict: 168. You have your own domain name. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
