Theo de Raadt: There are no formal relationships of any kind. That said, since it is a free world, there are numerous developers who do talk to their counterparts in the other group. Even when that does not happen, public mailing lists and the mainstay product of our projects -- source code -- is completely visible. What more could one want?
2. Do you incorporate code to OpenBSD from NetBSD or FreeBSD when important changes are made to these OSes?
Theo de Raadt: Sure, why wouldn't we?
3. What goodies the next version of OpenBSD is scheduled to bring us?
Theo de Raadt: First off, I should reiterate what I have been saying for 5 years: OpenBSD development is not revolutionary, but evolutionary. That means that between one release and another, not a lot of big things happen, but instead we should view it as a series of about 10,000 - 20,000 small changes. Over a series of OpenBSD releases, this amounts to a very big deal. Any release from 2 years back feels very different from the current codebase we have, but actually labelling the big changes between two consecutive releases is very difficult. Thousands of these changes are bug fixes, minor conformance improvements... things which I would argue matter MUCH MORE than "new features".
That said, this next release has one big thing that people are waiting to try out: We have written a whole new packet filter / nat engine, and fully integrated it into the system. People who are used to ipf will find that pf is much like ipf, but has some improvements which we have always wanted to make (and which the old ipf license had blocked us from doing).
The alpha port has been significantly improved to support many of the higher end models (kind of funny considering the entire platform is now end of lifed...), and we will be releasing our first ultrasparc beta.
Other than that and the thousands of little fixes and improvements everywhere, and probably a bunch of other things I have already forgotten,
4. OpenBSD's goal is to bring ultimate security to a server. By patching the holes and only accepting proved software do you think that it keeps your development moving slow from implementing something new to the OS level and releasing it pretty fast?
Theo de Raadt: No, I think it does not affect or release schedule or development process.