Currently all the code of Wonka, OSwald, and Rudolph was written by members of the core team, all of whom work at . Outside contributors will be acknowledged, just as soon as we have any ... in the meantime, meet the members of the Wonka team.

Steven Buytaert, spiritual father of Wonka [Photo of Steven]

Wonka began as a gleam in Steven's eye, accompanied by the refrain "I still think we should invade Sparta". Then the gleam in the eye was backed up with sample code, and next thing we knew we had committed ground troops. Also wholly responsible for OSwald. Is the only team member whose hobbies include being joint CEO of a market-leading company.

Chris Gray, team leader [Photo of Chris]

Presented a paper on a real-time multithreaded interpreter at a conference in Budapest in 1980, and is mildly surprised to do find himself still doing the same thing. Along the way, also did some work with telecommunications, particularly packet switching and ISDN, and collected a few letters (M.B.C.S., C.Eng, Eur. Ing). Mainly responsible for the innards of the Wonka VM, and also originally wrote many of the core class libraries (which others have thankfully corrected since). When not at work, is mostly to be found singing with outfits such as Kalliope and the curiously-named Vocaal Collectief, or studying with the Buqi Institute. Is owned by a large, black, hairy cat.

Dries Buytaert, team member [Photo of Dries]

I am a Ph.D. student in Computer Science at Antwerp University, but I'm full-time employed at ACUNIA. My research interests include run-time optimization of the JVM, and at ACUNIA, my work focuses on the development of an adaptive JIT compiler called J-Spot. I'm also the main responsible for the gory innards of Rudolph, Wonka's AWT implementation, which originally came to existence as my graduate thesis and which I have been maintaining, or helping to maintain, ever since. When not burying my head in bits and bytes, and when my research work leaves me some spare time, I enjoy going out with friends, movies, sailing and doing all kind of nerdy, computer related things.


Jan Dumon, team member [Photo of Jan]

Originally wrote our e2fs filesystem as a student project, now hacks at everything he can get his hands on.

Niklas Oberfeld, team member [Photo of Niklas]

Our resident graphic artist and singer/songwriter. Most of the visual tests that actually look like something are his work, as is a lot of the Java code in Rudolph.

Gerrit Ruelens, team member [Photo of Gerrit]

In modesty he knows no equal. Is responsible for the greater part of those 11000+ tests you read about, as well as large parts of the core libraries (Tests fail, reason: no code written yet. Solution: implement entire class from scratch ...). Plays the kind of sport where being 2 metres tall is an advantage.

Johan Vandeneede, team member [Photo of Johan]

A rare photo of Johan with nothing stuck in his ears. (Perhaps because neither Chris nor Niklas were singing at the time). Another important contributor to Rudolph, and is responsible for testing new releases: he really does run all those tests on all those platforms, and pushes all the buttons in the VisualTestEngine.