os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Updates and bug fixes to numerous parts of the website, courtesy of

Browse source 
Mark Linimon.  I added a couple of update to the DocProj page as well.

Submitted by:	mcl
This commit is contained in:
Warren Block 2015-11-25 01:53:10 +00:00
parent 1d828300e0
commit 16ec2b5832
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=47800
10 changed files with 62 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

2
en_US.ISO8859-1/htdocs/docproj/current.xml
View file

@ -84,7 +84,7 @@
task is highly encouraged to carefully read through the existing
(print-output) index, and to have read the Chicago Manual of
Style or other style books that deal with indexing. Please see
the CVS history of some of the chapter.xml files to see some of
the SVN history of some of the chapter.xml files to see some of
the indexing errors that have been corrected in the past.
It is imperative to view the PostScript version of the Handbook
after making any changes to indexterms as many errors, such as

16
en_US.ISO8859-1/htdocs/docproj/doc-set.xml
View file

@ -18,16 +18,14 @@
<ol>
<li><p><a href="&cgibase;/man.cgi"><b>The manual pages</b></a></p>
<p>The Project does not really concern itself with these, since
they are a part of the base system. The exception to this is the
Japanese team, who are translating them. There is no reason other
volunteers could not step in to translate the manual pages to other
languages as well.</p>
<p>The manual pages are part of the base system, but are also
an important component of the documentation. Both the
Documentation project and source committers update and
maintain manual pages.</p>
<p>That is not to say that the manual pages are unimportant, far from
it. It is just that they are intimately tied to specific systems of
FreeBSD, and most of the time the best person to write the manual
page is the person that wrote that part of FreeBSD.</p></li>
<p>At present, the Japanese team has translated many of the
manual pages. Other volunteers could pitch in to translate
the manual pages to other languages as well.</p></li>
<li><p><a href="../docs/books.html"><b>The Books</b></a></p>

10
en_US.ISO8859-1/htdocs/docproj/who.xml
View file

@ -14,25 +14,25 @@
<body class="navinclude.docs">
<p>The project is a fairly loosely knit group of people, and the only thing
we have got in common is that we are subscribed to the mailing list
we have in common is that we are subscribed to the mailing list
<a href="mailto:FreeBSD-doc@FreeBSD.org">FreeBSD-doc@FreeBSD.org</a>.</p>
<p>Some of us can commit changes directly to the FreeBSD
documentation tree. You can view a complete list of <a
documentation tree. There is a complete list of <a
href="../doc/en_US.ISO8859-1/articles/contributors/staff-committers.html">
all FreeBSD developers with commit privileges</a>, as well as a
list of the <a
href="../administration.html#t-doceng">
principal committers for the FreeBSD Documentation Project</a>.</p>
<p>Others do not have commit privileges, but they write and submit
<p>Others do not have commit privileges, but write and submit
documentation nonetheless. Once the documentation has been
submitted according to the <a href="submitting.html">Submit
Documentation</a> page, one of the committers will then
review it and include it in the documentation set.</p>
<p>If you want to help out with the documentation project (and I fervently
hope you do) all you have to do is subscribe to the mailing list and
<p>To help with the documentation project (and we fervently
hope you do), just subscribe to the mailing list and
participate. As soon as you have done that, you're a member of the
project.</p>