MediaWiki vs. wikispaces
"Mark Weber" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <[email protected]> |
I heard from Steven Wood that Sourceforge is now offering Wiki's to projects in collaboration with a Wiki hosting company called wikispaces. He asked me to comment on this possibility. I'm not a wiki expert by any means, but I do have a bit of exposure. I spent a couple of days doing various comparisons (mostly just reading on the web comparisons that others had already done). I recommended to my company to use TWiki, mostly because: o) most popular wiki for intranet use o) has a VMware-based install, making it really easy to start It's worked out fine. For BitPim, I think MediaWiki is a good choice, because o) familiar look and feel (everybody reads wikipedia) o) it's already up and running The main advantage of going with a wiki hosting company is that the administration is done by somebody else. The main disadvantages are: o) pay via ads or real money o) may go out of business: would require porting to another wiki In case you are not aware, there are lots of different wiki mark-up languages. They are all text based and are all easy, but different with somewhat different capabilities. I've looked at the wikispaces mark-up language; it seems very similar to MediaWiki, but I did not see anywhere that claimed compatibility. Their look and feel is similar, so perhaps wikispaces uses a MediaWiki engine, with some customization. Or not. I've also used pbWiki, which has a similar business model to wikispaces. They rolled their own wiki mark-up language. Bottom line: I don't see a compelling reason to change away from MediaWiki administered at BitPim.com Any other comments and/or experience? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/