On Sun, Nov 2, 2008 at 15:56, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> 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. I don't care for this either, but a lot of people love it. RSS etc as per Caleb's suggestion would not hurt to have. > 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. Rebuilding the site from the ground up based on some CMS would also be an option. Less work on the code site, more time for actual content. > 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. That part should be relatively easy to fix. >> * add an issue tracker > > This can also be separate. A link from the description would be > sufficient. RT aka Request Tracker [1] is extremely powerful in this regard. If you want to use that as the issue tracker, I volunteer to do all work on it. >> * add OpenId to vim.org OpenID is a spam wave waiting to happen. >> * 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. A Big Large Redirection from script a to script b would work with the existing system and be do-able in half an hour. Richard --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
