? diff Index: darwin_doc_howto.xml =================================================================== RCS file: /cvs/Darwin/Documentation/en_US.ISO8859-1/howto/darwin_doc_howto/darwin_doc_howto.xml,v retrieving revision 1.1 diff -u -r1.1 darwin_doc_howto.xml --- darwin_doc_howto.xml 19 Jan 2002 00:35:22 -0000 1.1 +++ darwin_doc_howto.xml 19 Mar 2002 11:33:33 -0000 @@ -71,9 +71,9 @@ - We'd love to have your contribution in any of these areas, or your suggestions for whatever other kinds of documents we should have. For now there is not a Darwin doc-specific mailing list, so please send any suggestions to Darwin-Development@lists.apple.com or to me at rhayden@apple.com. + We'd love to have your contribution in any of these areas, or your suggestions for whatever other kinds of documents we should have. If you are interested in writing documentation about Darwin, please join the darwin-documentation@lists.apple.com mailing list. - To join the Darwin Development list or any other Darwin-related list, see http://opensource.apple.com/projects/mail.html. + To join the Darwin Documentation list or any other Darwin-related list, see http://lists.apple.com/mailman/listinfo. @@ -115,7 +115,7 @@ man pages - man pages are currently going through a number of changes. A man page HOWTO will be released soon, and the man pages themselves are being moved from a centralized project to live with the commands they document. General responsibility for man pages are being moved from the writers to the engineers. + man pages are currently going through a number of changes. The Darwin Man Page HOWTO is essential reading if you are interested in working on man pages. Currently, the man pages themselves are being moved from a centralized project to live with the commands they document. General responsibility for man pages are being moved from the writers to the engineers. @@ -134,7 +134,7 @@ Who can submit documentation? - You! Who better? If you know about a subject that seems to be sorely lacking in documentation, then go ahead and write up a HowTo and send it to Darwin-Development@lists.apple.com or to rhayden@apple.com. If you can only cover part of a subject, do that part and send it in. Someone else is much more likely to help finish it if it's been started. + You! Who better? If you know about a subject that seems to be sorely lacking in documentation, then go ahead and write up a HowTo and send it to darwin-documentation@lists.apple.com or to rhayden@apple.com. If you can only cover part of a subject, do that part and send it in. Someone else is much more likely to help finish it if it's been started. @@ -153,12 +153,12 @@ Who can make changes to existing documents? Although the documentation is maintained as Open Source, we assume that the original author is interested in providing the primary maintenance for the document, and in guiding the nature of any changes and bug fixes. Therefore suggestions, changes, and bug fixes should be sent to the original author so they can decide how best to integrate them. - If there is no response, or the author is no longer interested in maintaining the document, or there's no obvious author, then send your comments to Darwin-Development@lists.apple.com or to rhayden@apple.com and they will get handled. + If there is no response, or the author is no longer interested in maintaining the document, or there's no obvious author, then send your comments to darwin-documentation@lists.apple.com or to rhayden@apple.com and they will get handled. Where is the documentation mailing list? - We don't have a doc-specific mailing list at this time. Until the documentation project gains its own momentum, we will simply use Darwin-Development@lists.apple.com. + A Documentation-specific mailing list is now available. Please join the darwin-documentation@lists.apple.com mailing list, in addition to any general purpose Darwin lists that interest you. Anyone interested in helping develop the HeaderDoc tool should join the HeaderDoc mailing list discussed earlier.