A new vim webseite should support: - password reset (requires email sending, sourceforge did not allow this in the past)
- integrates a wiki. I'd personally like to see a git based one. A very simple draft can be found at http://vim-wiki.mawercer.de/wiki/index.html - fixes the "author of plugins must care about 3 files" issue: github's README(.md/txt/..), install/info section on www.vim.org and doc/* documentation. Thus it should be able to display REDAME.txt / README.md like files - allows browsing plugin files online - allows searching in vim files (also plugin files), eg using github api - integrates vim-addon-manager-known-repository like fatures - allows registering plugins by "git(hub)/hg/..." like urls and be done, then generates zip/.. whatsoever from that info master branches are very stabel more often than not. - should still care about everything which was important on the old site, such as wishes about extensions, who spent how much, Uganda, .... - be very explicit about which operating systems are supported officially, and who is testing features on those. Eg I think that some features can only be "fixed" by introducing threading or similar and I don't have OS2 for testing. - should consider talking about the future of Vim (if known), roadmap - even if its vague and uncertain. - do whatever is necessary to improve collaboration. There are multiple projects such as snipmate, vim-snippets, vim-addon-manager which are maintained by multiple commnunity members. By updating from a github url this "membership" work could be outsourced to external partise such as github or similar. I'm pretty sure that Bram remebers quite a lot of "discussions". The last unanswered very important question by him is whether he would allow a differenting hosting if its guaranteed to be payed for a couple of years so that cloning repositories, caching source files, sending emails and similar features can be implemented. Of course - as always - this is only my limited view about what I think would be good for the Vim project and community. IMHO the first step is to find out what Vim and its community should be tomorrow, then documend and move forward. People will join and help probably. Marc Weber -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
