> 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 think this differs for everyone. My suggestion add an rss/atom feed... also I'm not sure how feasible this is but if we could use feedburner automagically with each script and have it's email service. this gives people the option of being notified in various ways is they choose. > 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. >> 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? I'd personally consider it. I'm of the mindset the site may need a complete rebuild. Could we consider using something like drupal for the basis? and then extend as needed. also are we stuck with MySQL? Personally I prefer PostgreSQL but this isn't my project, but I thought I'd raise it as an idea for discussion if we are rebuilding from scratch. > > 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. I think that many script maintainers may want to use the VCS they prefer, I for example like git, while others may prever hg, bzr, etc. However, I think it would be beneficial for us to provide a consistent location on the page for links to offsite resources. > > > * add a webforum to each scripts page > > * add an issue tracker > > > This can also be separate. A link from the description would be > sufficient. I'll once again refer to needing a consistent area for offsite resources. > > > * add OpenId to vim.org OpenID has it's own security problems, personally after thinking about it, I don't care for OpenID, just create an account with the username and password you always use. only once in a great while do I have problems doing that. > > * 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. well the clear point would be when that person uploads a newer script. -- Caleb Cushing --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
