Re: Again?: Mouse in console

[Mark Farquaad <markfarquaad@gmail.com>]

558 Words follow:


On Thu, 6 Jan 2005 10:21:27 -0600, eric
<eric-list-openbsd-misc@catastrophe.net> wrote:

> Why don't you send some patches to the man pages, HTML documentation pages,
> and see if they get accepted? That way, instead of wasting our time, and
> yours, you could provide some useful content.

Because I feel it's too difficult to find out how, in what form,
in what order, etc. etc.
It's not because I'm all talk and no do, it's because I'm trying
to faciliate this process for everyone.
I asked Nick if he wanted a correction for the badly out of
alphabetical order packages list on 3.5 i386. I did not get
an answer if yes or no or in what file form or even if he would
have the time or will to look at my contribution. I got the strong
impression he DOES NOT HAVE THE TIME to look at contributions
because he is ALONE.
I'm not trying to just get my own hands to work on the documentation
because that will just be a drop of water on a hot stone. I'm trying
to get a whole lot more hands to work and that I believe can only
be done by making it easier to contribute. And that's all I'm "whining"
about.

> If it talks like a troll, and smells like a troll, it is a troll.

Only to a troll...
It takes a troll to know one after all.

> There is a philosophy of coding and documentation within the OpenBSD
> development community. This, unlike Linux, makes things stay tight and clean
> and not have man pages that say "this page is deprecated since 1995."

Man look, the man pages are probably the best there are out 
there. I'm not criticizing them in the least. My complaint is
about the "printable" or "downloadable" documentation which
can be arranged in chapters and subchapters.
I dig this philosophy of coding in the OpenBSD development
community. I probably has produced one of the finest OSs
there are out there.
But not finest "printable" documentation.
Where a requirement of trusted relationships such as in the
small and good tight dev team of openBSD is great for source
code and the massive requirements for it, it's complete overkill
for "printable" documentation.
That's why the devs don't want to waste their invaluable time
with it, and rightly so. But it's also the reason why someone
else should do it. And not just ONE dummy who everyone in
the dev team laughs about because he's too *stupid* to write
code.
It should be a whole lot of people, more than can ever be
trusted through personal knowledge and friendship, while
at the same time still insuring adequate quality for that
documentation I'm talking about.

> Maybe try:
> 
> <http://www.openbsd.org/cgi-bin/man.cgi>

That one's fine. It has a creation process that's tailored to
make it good.
I want the same for the "printable" documentation.
Not the *same* process, but a tailored-to fit process that
produces plenty and good work.

> You should go use Linux or Windows, it might suit you better.

Yes, the printable documentation especially of Linux, such 
as Slackware or FreeBSD suits me better.
But not the source code. - Even if I don't know all about it I
would like to and probably never will.

Greetings,
Mark