> 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. >
Right, and if you ask me the entire site, not just scripts, needs work. I suggested drupal but if anyone has other suggestions I'm open. > >> * 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. I'd not heard of it before now, and don't know any sites that use it? I didn't see any demo's on the homepage, do you know of any? or maybe a site that uses it? I'm only against one issue tracker that I've used and that's Trac, seems to be difficult to set up (never seems to be done right the first time) and I've heard of other interesting issues. > > >> * add OpenId to vim.org > > > OpenID is a spam wave waiting to happen. > I agree with this... I'm surprised we haven't seen it yet since sites can be their own OpenID provider. > > A Big Large Redirection from script a to script b would work with the > existing system and be do-able in half an hour. sounds like a decent short term solution but I think we could do better on the long term. my suggestion is (quoting myself on the wiki) we need to implement a upload permissions system and perhaps something like githubs fork. We could make it so that the script maintainer must allow others to upload scripts, in the event that the script creator can't be reached within a certain period of time an admin could assign a new person as the maintainer. -- Caleb Cushing --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
