2008/10/26, Thomas Koch <[EMAIL PROTECTED]>: > > Hi, > > there is a vimonline development site[1] on sourceforge. The bugtracker > there states, that the last time an issue was closed was at 2007-07-30 > and the oldest open issue is from 2001-09-13. > Isn't it, that vim.org needs and deserves more attention to reflect the > greatness of VIM? Since I'm a webdeveloper I'd like to volunter to build > a fresh new vim.org site with all the features mentioned below. > But this should not be a one time one man effort but a planed team > effort. So who is the current responsible behind vim.org and who would > like to join the team? > > One new idea for vim.org/scripts: tags for scripts > > [1] http://vimonline.sourceforge.net/ > > Best regards, > > Thomas Koch > > Am Friday 24 October 2008 19:35:11 schrieb Caleb Cushing: >> On 10/22/08, Thomas Koch <[EMAIL PROTECTED]> wrote: >> > Hi, >> > >> > 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: >> > >> > * you won't get informed of updates for your scripts >> > >> > >> > * collaboration on script development is next to impossible, because >> > * I can't upload a new version, must open a new script page >> >> you mean you can't update someone elses script, I agree this is a >> problem as I believe a large number of vim scripts are unmaintained. >> and without comments we can't tell people we've forked it elsewhere. >> >> > * No script I saw is under version control >> >> sql iabbr 2 is :P but there is no way built in for vim.org >> >> > * Many scripts lack licence informations >> >> I'm guessing scripts are public domain unless otherwise stated. >> >> > * scripts can not be browsed online, there are only downloadable >> > zip/rar/tar.gz/vba/vim >> >> I don't see this as a huge problem... >> >> > * User Feedback on scripts is not possible: no comments, mailing list >> > to >> > much a barrier >> >> definitely should have comments below scripts like mozilla has for plugins >> >> > * No issue tracker >> >> yeah something would be nice... >> >> > 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 >> > * add a webforum to each scripts page >> > * add an issue tracker >> > * add OpenId to vim.org >> > * politely inforce a default licence for scripts >> > * allow people to upload patches to scripts they have not initially >> > created >> >> would it be impossible to make a new scripts page? or even just >> consider offloading scripts somewhere else? I'm managing mine on >> github. > > > > -- > Thomas Koch, Software Developer > http://www.koch.ro > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
