Comment 115 for bug 240067

> mediawiki

I don't see how this has anything to do with launchpad:

1. It's written in PHP. I know PHP pretty well, and I'm sure I could adapt this to launchpad's needs, but adding mediawiki here will only make it harder to develop launchpad; you'll need to know two programming languages.
2. It doesn't use bzr branches.
3. It's poorly written. I'm sure this is debatable, but in my opinion, it's poorly written. This is a side effect of PHP applications: everyone knows PHP, so sometimes devs aren't that bright.
4. Nightmare integration. Good luck making mediawiki look like it's part of launchpad. I won't be the one doing it.

Now, I'm sure it would be fairly easy to destroy my #2 and #3 arguments. However, #1 and #4 are real problems; I don't see the point of putting in extra work here.

> moin

In order to be as unbiased as possible, I think this could work. However, it doesn't meet this requirement:

Use a standard, existing markup language so that new users have less of a hurdle to learn Launchpad

It also doesn't use bzr to store pages, which is kind of a downside.
> wikkid

Developed by a canonical employee, uses bzr, meets the most requirements out of any of the three wikis.

> rolling our own

Instead of using existing work with wikkid or moin, let's just waste extra time by re-inventing the wheel. If there is any logic in doing this, I fail to see it.