Jeremy Smith's blog

Entry Is Labelled


This is completely whimsical and nothing should be read into this. I just wanted to throw it out there and see if any interesting ideas bounce back.

If you were to setup "", what Wiki system would you use? What other services would you want to integrate it with?


  1. gravatar

    I know they use WIKIs in the Center for Regional Economic Issues here at Weatherhead, so you might want to ask them...

    Susan Altshuler is the administrative contact.

  2. gravatar

    I don't have too much experience with Wiki, but I do know that there are a lot of Wiki engines I don't like.

    There are two Wiki engines I can think of that made me think "hey, I actually like this." The first is MediaWiki, used by Wikipedia. The second is part of a project management system called Trac.

    An example of one I hate is WikiWikiWeb.

    At the beginning of the semester I suggested to a friend that we should set up a Wiki for each class we're in together, then use it to take lecture notes or comment on the homework.

  3. gravatar

    MediaWiki, I think, would be a good choice. After all, it definitely shows it can scale.

    But, it is, also, a *huge* base of code. And, in the end, might be overkill.

  4. gravatar

    REI's wiki (didn't even know they had one) is interesting. A very non-Wiki-ish look (in a good way).

    However, it's hosted offsite by SmartMeetingDesign, so it is not something we can use.

    A Wiki@Case type deal would have to be nicely integrated into our architecture i.e. use our LDAP for authentication and authorization, be backed up, etc. Plus, I would like to be able to dig into it a little bit and perform some interesting Blog Wiki integration. Like, check a box on your blog entry and "WikiWords" in the entry are automatically linked into the Wiki@Case.

    Stuff like that.

    But, I do think it's cool that REI has a wiki. And, it's also cool that it is being hosted by a local business.

  5. gravatar

    I'm using PmWiki ( for our lab wiki, with about 15 users, and really like it. It's very lightweight and uses flat file storage. Version 2 is about to come out, and will be a significant improvement on version 1. It also makes a very good lightweight CMS (e.g., and is easy to install. I've also used MoinMoin (, which I also like, but I have no experience of installing that.

    Plone also has a built-in wiki (e.g. And you already use Plone, don't you?

  6. gravatar

    Plone is a big step to maintain and develop for. I definitely wouldn't use it just for a Wiki. The ITS/help site uses it (as well as the EECS department site, which I develop for), but Blog@Case does not (as far as I can tell), which makes me think a Wiki site would also be stand-alone.

    I'm not a huge fan of MoinMoin (again though, I've never been an experienced Wiki user), but I would favor a Python solution in principle. ;)

  7. gravatar

    Ah, so Brian, you're a Python guy... ;)

    Plone is out of the question. I want a Wiki not a publishing platform.

    I want something simple. Something that scales easily. Something that is as easy as possible for the end user ( ← very important). And, something that comes with a full builtin feature set: authentication, authorization, revision control. RSS feeds, etc.

    Like I said, nothing to look into here. I just wanted some ideas to poke around with in my spare time and see if another project proposal might be in order.

    (Integration points are a must-have, too. If I can't integrate it with Blog@Case or anything else, it is useless to me.)

  8. gravatar

    I like the interface for DocuWiki. One of the internal PerceptIS groups uses it.