Subject: Re: History of the NetBSD Foundation
To: None <netbsd-users@NetBSD.org>
From: Stefan Bozhilov <firstname.lastname@example.org>
Date: 09/02/2006 12:45:14
--- Peter Eisch <email@example.com> wrote:
> Then hire a lawyer and litigate properly. Take this
> thread to -advocacy if
> you feel it necessary to continue.
I like this thread. It's on the right place, at the
right time, between the right people. I learned a lot
of very important things from it and I gained a lot of
respect for Charles Hannum. We as engineers, tend to
overlook and mishandle organizational issues.
Unfortunately such issues are of paramount importance
- they should be discussed more, not less.
I'm patiently reading through the history review (like
many others, I suppose) - I would ask that it
continues and grows into a discussion about the future
One thing is clear even at this point - the current
project management is broken. It should be fully
transparent and very effective. Now it's neither. Mr.
Hannum is absolutely right about keeping development
and administration separate. Mixing them together
inevitably turns the project into a political circus.
Well, these problems are not unique. A lot of "open
source" projects end up with "closed" project
management. The situation is usually cured by a fork -
a simple solution at the end of all other options.
NetBSD has forked other projects before - as any well
written codebase should. What makes it forkable, also
makes it desirable for users. Clarity and elegance are
of central importance to any piece of infrastructure.
The truly open license attracts developers and
business. Add some honest project management and
you'll get an operating system that everyone wants to
write drivers for. This is the key, and it can be
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around