>   Actually, I thought those comments were remarkably restrained, given the
> source.  Theo is, shall we say, not known for tact.  :-)

Theo's tact is concise and straight to the point. That's one of the main
reasons I like the project so much. He doesn't waste time on politics or
talking. Show me the code. It gets stuff done faster.

>   I think it is a big deal, because, as Theo says, this impacts a lot of

It's not a huge deal. OpenBSD 2.9 is being released with IPF, so as long as
they aren't tracking -current, there shouldnt be a problem. That means the
OpenBSD team has 6 months to either come to an agreement with Darren, or
start doing research on their own project. Anyone using -current for
business solutions are asking for trouble in the first place.

> companies who have been using OpenBSD to build their own solutions.  This
> suddenly puts the licensing status of their work in doubt.  One of the
major
> advantages (depending on your POV) of OpenBSD is the right to do whatever
you
> want with it.  I'm not an OpenBSD user myself, but if I were, I'd be
fairly

Which is why they took it out. The developers dont want to waste time (time
== money) on this matter. If Darren decides to start releasing IPF under the
BSD license, then you'll see ipf back in the OpenBSD cvs. If not, then
expect to see some stuff popping up on mailinglists and OpenIPF.org.

> pissed about this.  As it is, it tweaks my sense of justice.

Yes... this razzled _alot_ of people. IMHO, Darren is being a complete jerk
about this. He cries up and down about its 'his' project, and can do
whatever he wants with it (which is very true), but he got PISSED when he
found out that OpenBSD dropped IPF and may start working on their own
project. All people want is Darren to tell us which direction he plans on
going with IPF, and under what license, but it seems as if not even Mr. Reed
knows.

Im not worried about the situation at all. I trust the developers will come
to a solution, but in the meantime, I'm waiting for 2.9 to arrive in my
mailbox.


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to