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

Replace the one-sentence introduction with a slightly paraphrased version

Browse source 
of Robert Watson's introduction (found at the top of the June 2001 status
report).

Reviewed by:	rwatson
This commit is contained in:
Chris Costello 2001-08-03 18:06:03 +00:00
parent 70fcb5ac51
commit 416ba9ac8a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=10145
1 changed files with 22 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
en/news/status/status.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD$">
<!ENTITY date "$FreeBSD: www/en/news/status/status.sgml,v 1.1 2001/08/02 04:26:30 chris Exp $">
<!ENTITY title "FreeBSD Status Reports">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -8,8 +8,27 @@
<html>
&header;
<p>Each month, the FreeBSD project releases a status report to keep users
and developers up to date on the projects in active development.</p>
<p>One of the benefits of the FreeBSD development model is a focus on
centralized design and implementation, in which the operating system is
maintained in a central repository, and discussed on centrally maintained
lists. This allows for a high level of coordination between authors of
various components of the system, and allows policies to be enforced over
the entire system, covering issues ranging from architecture to style.
However, as the FreeBSD developer community has grown, and the rate of
both mailing list traffic and tree modifications has increased, making it
difficult even for the most dedicated developer to remain on top of all
the work going on in the tree.</p>
<p>The FreeBSD Monthly Development Status Report attempts to address this
problem by providing a vehicle that allows developers to make the broader
community aware of their on-going work on FreeBSD, both in and out of the
central source repository. For each project and sub-project, a one
paragraph summary is included, indicating progress since the last summary.
If it is a new project, or if a project has not submitted any prior status
reports, a short description may precede the status information.</p>
<p>These status reports may be reproduced in whole or in part, as long as the
source is clearly identified and appropriate credit given. </p>
<h2>2001</h2>