Subject: Re: Documentation
To: Eric Delcamp <email@example.com>
From: fission <firstname.lastname@example.org>
Date: 04/13/2000 15:11:53
On Thu, 13 Apr 2000, Eric Delcamp wrote:
> Hi !
> I'm angry about NetBSD.
> We need to STOP all current projects, and go to write DOCUMENTATIONS.
Heh, yes! Let's get behind every other free OS on support for new
architectures and drivers!
> But the first writers of documentation should be the programmers. So, STOP
> CODING, MAKE DOCUMENTATIONS ! Oh yes, the subject is sooo vast, the amount
> of work is sooo important. But we need to begin the work.
In all seriousness, I've never found the documentation so lacking that I
coudn't get done what I wanted to do. Most of the time it just meant I
had to do some exploring on my own. If I was really stumped, I would
email the list and better than 90% of the time I would get an answer that
satisfactorily explained my problem and showed the answer.
> tree (it's just an idea, it seems too drastic ;-)
> I'm sure we have plenty of ideas about this, and I'm ok to talk about this.
I am in favor of a "unified NetBSD guide" but I don't think we need to do
the Linux thing and develop HOWTOs for every single aspect of the system.
A certain level of "playing around with the system" should still be
As it is right now (just looking at the documentation page), it looks to
me like we need one central place to start out with. It would be
especially nice if there were certain documentation pages that every
architecture had (somewhat like now, but only more so).
But I don't think we need documentation so bad that it's killing us -
these mailing lists are great! =)