i second this. i have been forced to use twiki-based wikis all my ife
until i met the lopsa web site. mediawiki was so much better and easier
to use; 'twas like night and day.
and to my mind almost as important, mediawiki just looks better.
having said that, mediawiki is less good at one thing:
automatic import of files. we often use our wiki to display stats
and other auto-generated stuff and we never figured out a real
smooth way to do that. (it might be solved now, tho.)
On Apr 29, 2010, at 8:29 PM, Chuck McIntyre wrote:
On Tue, Apr 27, 2010 at 12:57 PM, David Parter
<[email protected]> wrote:
Our faculty (and students) want wikis. And they would like us to
support their wikis. They haven't exactly said what that means,
but we
can at least define a plausible service offering, and see if that
works.
IMO, go for mediawiki. It supports replication, database backends,
doesn't use java and is generally easy enough to maintain. Plus, the
UI is nicer than a lot of the other Wikis and it allows editing by
section, which is nice.
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
------------------
Andrew Hume (best -> Telework) +1 732-886-1886
[email protected] (Work) +1 973-360-8651
AT&T Labs - Research; member of USENIX and LOPSA
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
