Please read my message. I asked where do I send it to?

I don't think the average user is going to learn enough about Latex or the
documentation to be effective.

There are hundreds of separate files in the IBM documentation. Who will
proof the edits? Or check the technical accuracy, expecially on all the
different architectures suported?

The IBM documentation looks like it was emitted from a very sophisticated
internal documentation system. 

tedc


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jeffrey Hutzelman
Sent: Thursday, June 09, 2005 8:09 PM
To: ted creedon
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] Documentation project

On Thursday, June 09, 2005 01:31:06 PM -0700 ted creedon
<[EMAIL PROTECTED]> wrote:

> ... but I don't think anyone but me will be dong updates anyway.

That doesn't sound like a reasonable assumption to me, either in theory or
in practice.

This is an open-source project, and it needs to be possible for people to
contribute changes to it, including to its documentation.  Not changes of
the form "Ted, please make it say blah".  Changes in the form of patches,
which can be integrated by gatekeepers, without your involvement.


-- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to