Index: head/en_US.ISO8859-1/htdocs/advocacy/index.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/advocacy/index.xml +++ head/en_US.ISO8859-1/htdocs/advocacy/index.xml @@ -60,7 +60,7 @@ are using FreeBSD.
  • A brief list of sites using &os; is maintained - + in the handbook.
    • @@ -68,13 +68,13 @@

    FreeBSD conferences

    Index: head/en_US.ISO8859-1/htdocs/advocacy/myths.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/advocacy/myths.xml +++ head/en_US.ISO8859-1/htdocs/advocacy/myths.xml @@ -14,29 +14,30 @@ -

    As the BSD projects (including DragonFlyBSD, FreeBSD, NetBSD, and OpenBSD) have grown in size, - a number of persistent myths have grown up around them. Some of these are - perpetuated by well meaning but misguided individuals, others by people - pursuing their own agendas.

    +

    As the BSD projects (including DragonFlyBSD, &os;, NetBSD, and + OpenBSD) have grown in size, a number of persistent myths have + grown up around them. Some of these are perpetuated by well + meaning but misguided individuals, others by people pursuing + their own agendas.

    -

    This page aims to dispel those myths while remaining as dispassionate - as possible.

    +

    This page aims to dispel those myths while remaining as + dispassionate as possible.

    -
    Note: Throughout this page, ``*BSD'' refers to all - of the BSD Projects. Where a myth or response is specific to a - particular project it is indicated as such.
    +
    Note: Throughout this page, ''*BSD'' refers to + all of the BSD Projects. Where a myth or response is specific + to a particular project it is indicated as such.
    -
    If you are aware of an omission or error on this page, please - let the FreeBSD - documentation project mailing list know.
    +
    If you are aware of an omission or error on this page, + please let the &os; + Documentation Project mailing list know.

    Myths

    Index

    Myth: *BSD has a closed development - model, it's more ``Cathedral'' than ``Bazaar''

    + model, it's more ''Cathedral'' than ''Bazaar'' -

    Eric Raymond wrote an influential paper, ``The - Cathedral and the Bazaar'' in which the Linux development model - (and the model Eric used for fetchmail) is held up as an - example of how to do ``open'' development. By contrast, the model - employed by *BSD is often characterized as closed.

    +

    Eric Raymond wrote an influential paper, + ''The + Cathedral and the Bazaar'' in which the Linux + development model (and the model Eric used for + fetchmail) is held up as an example of how to do + ''open'' development. By contrast, the model employed by *BSD + is often characterized as closed.

    -

    The implicit value judgment is that ``bazaar'' (open) is good, and - ``cathedral'' (closed) is bad.

    +

    The implicit value judgment is that ''bazaar'' (open) is good, + and ''cathedral'' (closed) is bad.

    If anything, *BSD's development model is probably - more akin to the ``bazaar'' that Eric describes than - either Linux or fetchmail.

    + more akin to the ''bazaar'' that Eric describes + than either Linux or fetchmail.

    Consider the following;

    @@ -112,20 +118,22 @@

    Pointers to this system litter the documentation.

    -

  • Not everyone can commit code changes to the *BSD code. You - need to be a committer first. Typically, people are offered - ``commit privs'' after they have made a few well-thought out - submissions to the project using Bugzilla or similar.

    +

  • Not everyone can commit code changes to the *BSD code. + You need to be a committer first. Typically, + people are offered ''commit privs'' after they have made a + few well-thought out submissions to the project using + Bugzilla or similar.

    This is identical to the Linux mechanism. Only one person is (notionally) allowed to change the Kernel, Linus. But specific areas (such as the networking code) are delegated to other people.

    -

    Aside: Nik (nik@FreeBSD.org) is a case in point. After making - several submissions to the FreeBSD Documentation Project and - web pages, he was offered ``commit privs'' so that he did not - have to keep bothering other committers to commit the changes. He - never had to ask for them, they were freely given.

    • +

    Aside: Nik (nik@FreeBSD.org) is a case in point. After + making several submissions to the &os; Documentation + Project and web pages, he was offered ''commit privs'' so + that he did not have to keep bothering other committers to + commit the changes. He never had to ask for them, they + were freely given.

    @@ -210,8 +218,8 @@ desktop machine.

    *BSD has access to the same desktop tools (KDE, GNOME, Firefox, - windowmanagers) as Linux. And ``office'' applications such as - OpenOffice suite work under *BSD too.

    + windowmanagers) as Linux. And ''office'' applications such as + LibreOffice suite work under *BSD too.

    @@ -294,10 +302,10 @@ systems (SunOS and similar). *BSD users can generally compile software written for these systems without needing to make any changes.

    -

    In addition, each *BSD project uses a ``ports'' system to make the - building of ported software much easier.

    +

    In addition, each *BSD project uses a ''ports'' system to make + the building of ported software much easier.

    -

    FreeBSD: There are currently more than 26,000 +

    FreeBSD: There are currently more than 30,000 applications ready to download and install in the FreeBSD ports collection. On i386 and AMD64, the Linux emulation layer will also run the vast majority of Linux applications. On the AMD64 @@ -307,7 +315,7 @@ i386 Linux applications, and the majority of SunOS4 applications can be run on a SPARCStation.

    -

    OpenBSD: There are currently more than 3700 applications +

    OpenBSD: There are currently more than 8000 applications ready to download and install in the OpenBSD ports collection. The Linux emulation layer will also run the vast majority of i386 Linux applications, and the majority of SunOS4 applications can be run on a