The interviews idea was to kind of start having some material for future press use. As this is not something we have discussed deeply... I just decided to wiki it here.
Please understand these questions may look/be silly or too simple, but keep in mind Moin is something all kinds of people will read about, so try to give answers as complete as possible.
Thanks,
The some day MoinMarketingTeam 
All the questions and answers provided here may also be posted in a Chilean site in spanish (Pretty soon, I hope I'll be hosting www.moin.cl, so this material will get hosted there, as well)
A little bit about MoinMoin
How old is MoinMoin?
Release 0.1 dates back to 2000-07-29. --ThomasWaldmann
Whose idea was to develop MoinMoin?
Jürgen Hermann's. At the beginning it was a clone of PikiPiki (another Wiki engine in Python). -- ThomasWaldmann
Why develop in Python?
Because it is fun.
--ThomasWaldmann Because its easy, powerful and productive. Did we say fun? --NirSoffer
Because programming Python is a pleasure. --FlorianFesti
How is MoinMoin different from other wikis?
This is hard to answer, as there are many similar wiki engines out there, and evaluating a wiki takes lot of time. We try to make a powerful, easy to maintain and use, and elegant wiki, easily extendable in python. It runs everywere where python runs, no data base or special software needed. -- ThomasWaldmann
It talks Hebrew, from version 1.1, unlike most wiki engines. Also, it lets me do what I want with little work. --NirSoffer
What are the policies you use in order to define a Release?
It should be better than the releases before.
We don't try to make it perfect - in that case we maybe would never do a release. --ThomasWaldmann - We started to develop in branches since 1.1
Releases with a minor version number are bugfix releases that are dropin replacements for releases with the same major number. They might contain minor improvements but should be easy to update. Minors are only released while the new major release is still in development. --FlorianFesti
Releases with new major version number are major feature updates. They may change internal interfaces (with may require changes to external plugins) or even the data format (with may require convertion the data/ directory of each instance with a script). New Features might also have to be turned on in the configuration. So you should read the Changes files and update instructions properly. --FlorianFesti
Volunteers, if any, how can they get involved?
I began with writing some extensions for moin (macros, actions). This is pretty easy, even if you don't know much of the code. With time, you get deeper and deeper in there.
If you don't want to code, you can also help us documenting, translating and finding the bugs. --ThomasWaldmann We use a very wiki-like development style. New developers are welcome. --FlorianFesti
About Moin 1.3
How long did it take you to get to 1.3?
1.3.0 == 2004-12-06, 1.2 == 2004-02-20 (well, that's not the whole truth, much of the code of 1.3 lived in some separate development branches for a while). --ThomasWaldmann
Which words would you choose to sum up the "objective" for 1.3?
The feature list is a bit long to post here. I think it got pretty nice (visually and feature set, too). --ThomasWaldmann
What "security policies" are applied to MoinMoin 1.3?
We have Access Control Lists (since 1.2, iirc). --ThomasWaldmann
We also included an antispam feature that works with a central black list. -- FlorianFesti
In your opinion, what is missing in 1.3 that you would have liked it to include?
We have quite some plans for 1.4, like unifying quite some things, making code easier and more powerful. But that's more about future plans than "missing stuff". The only thing really missing in 1.3 is maybe more i18n, table borders and completely validating html (some minor issues left). Nothing really serious. --ThomasWaldmann
So in which direction will the future development of MoinMoin go?
One big thing will be to get the MoinMoin wikis network aware. With antispam we started to use a central blacklist. But there are some more advanced features in planning like TrackBack support, sharing RecentChanges of some single pages or grouping pages of several wikis as related. --FlorianFesti
Another thing is to finally get export of wikipages in other formats up and running. --FlorianFesti
Of course there will be a lot of internal refactoring and improvements to keep the program structure clean. This is an continously process that is very unlikely to ever stop --FlorianFesti
What could a developer find tempting about MoinMoin 1.3?
That coding in Python is easy and fun. In my case, I even learned Python because I wanted to hack moin (seeing how elegant and easy the moin code and the language looked). --ThomasWaldmann
Its easy to extend. My first macro was only 5 lines and was just enough to implement right to left support for both sections and spans of text. --NirSoffer
Its Free software. You spend your time well when you hack moin, and you can learn a lot from other people involved in the project. --NirSoffer
MoinMoin is great, ok. But besides being useful for text contents, what else can it do? Can pages be imported/exported form/to other formats? Can MoinMoin work with other technologies?
The architecture of MoinMoin is very well suited to easily integrate other formats. Using other formats within MoinMoin works well for a long time. There are numerous parsers/processor - most of them as extention module - which allow using other formats within MoinMoin. Even new formats can be integrated with only a few lines of code if there is a program that can convert them to a format displayable on the web. The other way round is still a problem. In theory it should be possible and easy to write a formatter (the part of MoinMoin that produces the output) to convert pages in any format. In the real life this has turned out to be a bit more difficult, but we have made large steps to make this possible during the 1.3 development. So it is very likly that 1.4 will be able to export pages to other formats like LaTeX, PDF, ... --FlorianFesti
How have you managed to organize translation work? How close are translations from "official Moin"?
Translations are of very different quality. It all depends on how active the moin wiki people of that language are contributing and collaborating. The system and help pages are done on the MoinMaster wiki, the system texts are done by translating *.po files. Coordination is done on MoinDev/Translation. --ThomasWaldmann
Why did you decide to modify the themes?
We all knew that they were not great. Good coders are often not good designers. Nir Soffer did a great work designing some pretty themes (and he even is a good coder, too). --ThomasWaldmann
Themes used to suck. Both the look and the messy code that was scattered around many files. ThomasWaldmann did the hard work of fectching all that code into the theme plug-in system, I just rewrite it and tried to improve the look. I hope it suck less now. --NirSoffer
What components are part of a theme? Are they part of the code?
A theme is made of CSS files, images (png) and a python code file handling the dynamic stuff. --ThomasWaldmann
How do you picture the coming user interface?
I want to see even more streamlined interface, that let you do thing with less steps, prevent common user errors, and don't nag you with useless messages. I also want to have simpler and more powerfull way to design attractive pages, for example, easily design multi coloumn pages, side bars, floating images and like. --NirSoffer
Any chances of getting a modified/changed MoinMoin logo?
I think there are chances, but we should discuss that with Juergen Hermann, too. Problem is he is very busy at work and can't work much on moin recently. --ThomasWaldmann
There is still the ultimate logo missing but some promissing suggestions have already been added to MoinDev/MoinMoinLogo. --FlorianFesti