Paul Irofti write: > I don't understand why Google Wiki is being discussed here as the main > solution. As I see it there are a few _major_ disadvantages of using it:
I can understand that you may have something against using Google, but there is no reason to be paranoid about it. > - it has software limitations that a large community, such as ours, > can't cope with What limitations? Google code has only just started and it's quickly expanding the features offered. Not only is it for free, it's also way more reliable than SourceForge (the shell server was recently out for more than a week :-(). > - it's managed and offered by a third party organization I'm not going to own a Vim webserver and pay for it, thus this will always be so. > - we don't have controls of what features we want in and/or out or the > way the layout/code/roadmap goes There are a few limitations, yes. Reasonable limitations though. > - it's a commercial product and Vim will be asociated with it in the long > run It's not commercial, it's free. > - Google is as corporate as you can get, corporations and OpenSource > don't mix well together (there are tons of examples) There are lots of open source people working for Google, probably more than in any other company. We feel quite happy about that. > - from what I've read in this thread it doesn't even have all the > features needed for a working Vim-tips wiki That might indeed be the bottleneck. And that's why we were trying it out, to see if it would work well enough. > On the other hand mediawiki seems the best solution for something like > this: > > - it's *OpenSource* > - it offers an easy management environment > - it can support high loads of traffic (see wikipedia) > - it has multi-language support > - it's easy to customize and improve > - it's not chown()-ed by any corporation And requires your own webserver, maintenance, etc. Main problem here is to avoid spamming, this has destroyed many wikis already and will only get worse. It's so much easier to join a service that is well maintained than to run your own. > I know I'm not a regular here, but I read most of the mail I get from > vim@ and don't quite get why you people are seriously considering this. > So I thought I'd drop my two cents and hope that someone can shed some > light. Main reason is that all self-made solutions fail eventually. The tips on SourceForge are now closed because of the spamming problems. We need something else. Keep in mind that both Scott Johnston and myself are working for Google, that helps for getting things done. SourceForge is a dead end, it takes them forever to fix problems. -- hundred-and-one symptoms of being an internet addict: 204. You're being audited because you mailed your tax return to the IRC. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
