From fae4c07232989a70f2ee29150fca71186fb18c99 Mon Sep 17 00:00:00 2001 From: "Jordan K. Hubbard" Date: Mon, 9 Sep 1996 01:56:58 +0000 Subject: [PATCH] Close PR#1587 and 1586 Submitted-By: "David E. O'Brien" Incorporate new development section, since Satoshi seems to have wandered off for a bit and I have too much stuff stacking up in my handbook directory. Submitted-By: asami --- handbook/Makefile | 4 +- handbook/bibliography.sgml | 16 ++++-- handbook/contrib.sgml | 7 +-- handbook/development.sgml | 105 +++++++++++++++++++++++++++++++++++++ handbook/handbook.sgml | 3 +- handbook/history.sgml | 47 +++++------------ handbook/sections.sgml | 3 +- 7 files changed, 138 insertions(+), 47 deletions(-) create mode 100644 handbook/development.sgml diff --git a/handbook/Makefile b/handbook/Makefile index 1701854d65..6e2e28acf6 100644 --- a/handbook/Makefile +++ b/handbook/Makefile @@ -1,8 +1,8 @@ -# $Id: Makefile,v 1.16 1996-07-29 07:15:54 jkh Exp $ +# $Id: Makefile,v 1.17 1996-09-09 01:56:54 jkh Exp $ SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml SRCS+= booting.sgml contrib.sgml crypt.sgml ctm.sgml current.sgml -SRCS+= cyclades.sgml dialup.sgml +SRCS+= cyclades.sgml development.sgml dialup.sgml SRCS+= diskless.sgml dma.sgml eresources.sgml esdi.sgml SRCS+= firewalls.sgml glossary.sgml goals.sgml SRCS+= handbook.sgml history.sgml hw.sgml install.sgml isdn.sgml kerberos.sgml diff --git a/handbook/bibliography.sgml b/handbook/bibliography.sgml index 41fd1d8416..6645acb189 100644 --- a/handbook/bibliography.sgml +++ b/handbook/bibliography.sgml @@ -1,4 +1,4 @@ - + @@ -9,7 +9,7 @@ they are notorious for not illustrating how to put the pieces together to make the whole operating system run smoothly. For this, there is no substitute for a good - book on Unix system administration and a good users' + book on UNIX system administration and a good users' manual. @@ -26,7 +26,7 @@ O'Reilly & Associates, Inc., 1994. ISBN 1-56592-076-7 - Unix in a Nutshell. + UNIX in a Nutshell. O'Reilly & Associates, Inc., 1990. ISBN 093717520X @@ -64,7 +64,7 @@ O'Reilly & Associates, Inc., 1992. ISBN 0-937175-82-X - Nemeth, Evi. Unix System Administration + Nemeth, Evi. UNIX System Administration Handbook. 2nd ed. Prentice Hall, 1995. ISBN 0131510517 @@ -226,7 +226,7 @@ - Unix history + UNIX history

@@ -239,6 +239,9 @@ IDG Books Worldwide, Inc., 1994. ISBN 1-56884-203-1 + Don Libes, Sandy Ressler Life with Unix - + special edition. Prentice-Hall, Inc., 1989 + @@ -249,6 +252,9 @@ The C/C++ Users Journal. R&D Publications Inc. ISSN 1075-2838 + Sys Admin - The Journal for UNIX System + Administrators. Miller Freeman, Inc. ISSN 1061-2688 + diff --git a/handbook/contrib.sgml b/handbook/contrib.sgml index bd9e55bdb5..95321dd304 100644 --- a/handbook/contrib.sgml +++ b/handbook/contrib.sgml @@ -1,4 +1,4 @@ - + + + +The FreeBSD development model + +

Contributed by &a.asami;. + +

The development of FreeBSD is a very open and flexible process, +FreeBSD being literally built from the contributions of hundreds of +people around the world, as can be seen from our . We are constantly on the lookout for +new developers and ideas, and those interested in becoming more +closely involved with the project need simply contact us at our + +mailing list. Those who prefer to work more independantly are also +accomodated, and they are free to use our FTP facilities at to distribute their own patches or work-in-progress +sources. Our is also available to those wishing +to make other FreeBSD users aware of major areas of work. + +Whether working independantly or more closely with the project, there +are number of things about how we handle our development which is useful +to know. The first and foremost item of importance in our development +work is: + + +The CVS repository + +

The central source tree for FreeBSD is maintained by +(Concurrent Version System), a freely available source code control +tool which comes bundled with FreeBSD. The primary +resides on a machine in Concord CA, USA from where it is replicated +to numerous mirror machines throughout the world. The CVS tree, as well +as the and trees which are checked out of it, can be easily +replicated to your own machine as well. Please refer to the + +section for more information on doing this. + +The committers list +

The are the people +who have write access to the CVS tree, and are thus +authorized to make modifications to the FreeBSD source (the term +``committer'' comes from the cvs(1) ``commit'' +command, which is used to bring new changes into the CVS repository). +The best way of making submissions for review by the committers list +is to use the command, though if something appears to be jammed +in the system then you may also reach them by sending mail to . + + +The FreeBSD core team + +

The would be +equivalent to the board of directors if the FreeBSD Project were a +company. The primary task of the core team is to make sure the +project, as a whole, is in good shape and is heading in the right +directions. Inviting dedicated and responsible developers to join our +group of committers is one of the functions of the core team, as is +the recruitment of new core team members as others move on. Most +current members of the core team started as committers who's addiction +to the project got the better of them. + +

Some core team members also have specific , meaning that they are committed to +ensuring that some large portion of the system works as advertised. +Note that most members of the core team are volunteers when it comes +to FreeBSD development and do not benefit from the project +financially, so "committment" should also not be misconstrued as +meaning "guaranteed support." The ``board of directors'' analogy +above is not actually very accurate, and it may be more suitable to +say that these are the people who gave up their lives in favor of +FreeBSD against their better judgement! ;) + +Additional contributors + +

Last, but definitely not least, the largest group of developers are +the users themselves who provide feedback and bug-fixes to us on an +almost constant basis. Here are of the people who contributed something which made +its way into our source tree. Why not join this list too by +contributing something back to FreeBSD? :-) + +

Providing code is not the only way to contribute to the project; +for a more complete list of things we need, please refer to the section in this handbook. + + + +In summary, our development model is organized as a loose set of +concentric circles. The centralized model is designed for the +convenience of the users of FreeBSD, who are thereby provided +with an easy way of tracking one central code base, not to keep +potential contributors out! Our desire is to to present a stable +operating system with a large set of coherent that the users can easily install and +use, and this model works very well in accomplishing that. + +All we ask of those who would join us as FreeBSD developers is some of +the same dedication its current people have to its continued success! diff --git a/handbook/handbook.sgml b/handbook/handbook.sgml index 80514c84ba..791bb24f63 100644 --- a/handbook/handbook.sgml +++ b/handbook/handbook.sgml @@ -1,4 +1,4 @@ - + or one of the numerous &nutshell; &history; &goals; + &development; &relnotes; &install; diff --git a/handbook/history.sgml b/handbook/history.sgml index 17d0570b29..0d79e5bd1f 100644 --- a/handbook/history.sgml +++ b/handbook/history.sgml @@ -1,4 +1,4 @@ - + A brief history of FreeBSD @@ -78,39 +78,16 @@ easier to install FreeBSD 2.0.5 release in June of 1995. Where to from here? -We just released FreeBSD 2.1.0 on November 19th, 1995 and, by all -accounts, people are pretty happy with it. We will therefore continue -with the 2.1-STABLE branch of FreeBSD (which actually began with 2.0.5) -well into Q1 of 1996 with at least one additional release: -FreeBSD 2.1.1. +We just released FreeBSD 2.1.5 in August of 1996, and it appears to be +doing well enough for us that one last release along the -stable +branch, 2.1.6, is merited. This is scheduled for release some time in +November. -A 2.1.2 release may follow 2.1.1, though this will depend heavily on the -status of FreeBSD 2.2 in Q2 of 1996. 2.2 is our development branch, -where long term projects for everything from NFS v3 to PCCARD support -are currently taking place. Preliminary timelines suggest that development -in 2.2 will begin slowing down and early release engineering simulations -(2.2 SNAPshots) started in Q1 of 1996. Given a favorable prognosis for 2.2's -general health, a migration to 2.2 will then begin in early Q2 of 1996 and -a new 2.3 branch created for next-generation development. Around the -time that 2.2-RELEASE is produced (late Q2 1996), the 2.1.x lineage will -also be phased out. +2.2, our development branch where long term projects for everything +from NFS v3 to PCCARD support is currently taking place, will continue +to have snapshot releases made of it right up until initial 2.2 code +freeze, which is scheduled for January of 1997. -We also intend to focus on any remaining areas of weakness, like documentation -or missing drivers, and steadily increase the overall quality and feature set -of the system well into 1996 and beyond. - -Now might also be a good time to note that the development of FreeBSD is -not a closed process, despite some popular misconceptions to the -contrary, and anyone is free to contribute code or ideas. Once a contributor -has established a reasonable track record for reliability, we generally, in -fact, give them write access to the project's CVS repository, where their -changes can propagate automatically to other users of FreeBSD. Our -centralized development model is designed for the convenience of the -users of FreeBSD, who are thereby provided with an easy way of -tracking one central code base, not to keep potential contributors out! -Individuals who hae shown a consistent and significant dedication to the project -are even often asked to join the FreeBSD core team to help in setting -the project's overall directions and goals, so truly no part of the project -is closed to additional members. All we ask of those wishing for closer -ties to this project is some of the same dedication its current members have -to its continued success! +We also intend to focus on any remaining areas of weakness, like +documentation or missing drivers, and steadily increase the overall +quality and feature set of the system well into 1997 and beyond. diff --git a/handbook/sections.sgml b/handbook/sections.sgml index f48409ac32..bb102f47a8 100644 --- a/handbook/sections.sgml +++ b/handbook/sections.sgml @@ -1,4 +1,4 @@ - + @@ -12,6 +12,7 @@ +