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

Updated information in advocacy section

Browse source 
* Change the incorrect characters `` to ''
* Correct the URL that refers to the Handbook
* Change the URL of the *BSD conferentes to use https
* Update the number of FreeBSD and OpenBSD ports
* Some corrections with igor

Patch by:	carlavilla@
Approved by:	bcr@(mentor)
Differential Revision:	https://reviews.freebsd.org/D23040
This commit is contained in:
Sergio Carlavilla Delgado 2020-01-05 20:20:33 +00:00
parent 91d96b56e6
commit 79a0717c5f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=53761
2 changed files with 51 additions and 43 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
en_US.ISO8859-1/htdocs/advocacy/index.xml
View file

@ -60,7 +60,7 @@
are using FreeBSD.</li> are using FreeBSD.</li>
<li>A brief list of sites using &os; is maintained <li>A brief list of sites using &os; is maintained
<a href="&base;/handbook/nutshell.html#INTRODUCTION-NUTSHELL-USERS"> <a href="&base;/handbook/nutshell.html#introduction-nutshell-users">
in the handbook</a>.</li> in the handbook</a>.</li>
</ul> </ul>
@ -68,13 +68,13 @@
<h2>FreeBSD conferences</h2> <h2>FreeBSD conferences</h2>
<ul> <ul>
<li><a name="bsdcan" href="http://www.bsdcan.org/">BSDCan</a>, the <li><a name="bsdcan" href="https://www.bsdcan.org/">BSDCan</a>, the
annual BSD Conference held in Ottawa, Canada.</li> annual BSD Conference held in Ottawa, Canada.</li>
<li><a name="eurobsdcon" href="http://www.eurobsdcon.org/">EuroBSDCon</a>, <li><a name="eurobsdcon" href="https://www.eurobsdcon.org/">EuroBSDCon</a>,
the annual BSD Conference in Europe.</li> the annual BSD Conference in Europe.</li>
<li><a name="asiabsdcon" href="http://asiabsdcon.org/">AsiaBSDCon</a>, <li><a name="asiabsdcon" href="https://asiabsdcon.org/">AsiaBSDCon</a>,
the annual BSD Conference held in Asia.</li> the annual BSD Conference held in Asia.</li>
</ul> </ul>

86
en_US.ISO8859-1/htdocs/advocacy/myths.xml
View file

@ -14,29 +14,30 @@
<body class="navinclude.about"> <body class="navinclude.about">
<p>As the BSD projects (including DragonFlyBSD, FreeBSD, NetBSD, and OpenBSD) have grown in size, <p>As the BSD projects (including DragonFlyBSD, &os;, NetBSD, and
a number of persistent myths have grown up around them. Some of these are OpenBSD) have grown in size, a number of persistent myths have
perpetuated by well meaning but misguided individuals, others by people grown up around them. Some of these are perpetuated by well
pursuing their own agendas.</p> meaning but misguided individuals, others by people pursuing
their own agendas.</p>
<p>This page aims to dispel those myths while remaining as dispassionate <p>This page aims to dispel those myths while remaining as
as possible.</p> dispassionate as possible.</p>
<blockquote><b>Note:</b> Throughout this page, ``*BSD'' refers to all <blockquote><b>Note:</b> Throughout this page, ''*BSD'' refers to
of the BSD Projects. Where a myth or response is specific to a all of the BSD Projects. Where a myth or response is specific
particular project it is indicated as such.</blockquote> to a particular project it is indicated as such.</blockquote>
<blockquote>If you are aware of an omission or error on this page, please <blockquote>If you are aware of an omission or error on this page,
let the <a href="mailto:doc@freebsd.org">FreeBSD please let the <a href="mailto:doc@freebsd.org">&os;
documentation project mailing list</a> know.</blockquote> Documentation Project mailing list</a> know.</blockquote>
<h2>Myths</h2> <h2>Myths</h2>
<h2>Index</h2> <h2>Index</h2>
<ul> <ul>
<li><a href="#closed-model">*BSD has a closed development model, <li><a href="#closed-model">*BSD has a closed development
it's more ``Cathedral'' than ``Bazaar''</a></li> model, it's more ''Cathedral'' than ''Bazaar''</a></li>
<li><a href="#own-distro">You can't make your own distributions or <li><a href="#own-distro">You can't make your own distributions or
derivative works of *BSD</a></li> derivative works of *BSD</a></li>
@ -65,20 +66,25 @@
</ul> </ul>
<h3>Myth: <a name="closed-model">*BSD</a> has a closed development <h3>Myth: <a name="closed-model">*BSD</a> has a closed development
model, it's more ``Cathedral'' than ``Bazaar''</h3> model, it's more ''Cathedral'' than ''Bazaar''</h3>
<p>Eric Raymond wrote an influential paper, ``<a href="http://www.catb.org/~esr/writings/cathedral-bazaar/">The <p>Eric Raymond wrote an influential paper,
Cathedral and the Bazaar</a>'' in which the Linux development model ''<a
(and the model Eric used for <tt>fetchmail</tt>) is held up as an href="http://www.catb.org/~esr/writings/cathedral-bazaar/"
example of how to do ``open'' development. By contrast, the model target="_blank"
employed by *BSD is often characterized as closed.</p> rel="noopener">The
Cathedral and the Bazaar</a>'' in which the Linux
development model (and the model Eric used for
<tt>fetchmail</tt>) is held up as an example of how to do
''open'' development. By contrast, the model employed by *BSD
is often characterized as closed.</p>
<p>The implicit value judgment is that ``bazaar'' (open) is good, and <p>The implicit value judgment is that ''bazaar'' (open) is good,
``cathedral'' (closed) is bad.</p> and ''cathedral'' (closed) is bad.</p>
<p>If anything, *BSD's development model is probably <p>If anything, *BSD's development model is probably
<strong>more</strong> akin to the ``bazaar'' that Eric describes than <strong>more</strong> akin to the ''bazaar'' that Eric describes
either Linux or <tt>fetchmail</tt>.</p> than either Linux or <tt>fetchmail</tt>.</p>
<p>Consider the following;</p> <p>Consider the following;</p>
@ -112,20 +118,22 @@
<p>Pointers to this system litter the documentation.</p></li> <p>Pointers to this system litter the documentation.</p></li>
<li><p>Not everyone can commit code changes to the *BSD code. You <li><p>Not everyone can commit code changes to the *BSD code.
need to be a <em>committer</em> first. Typically, people are offered You need to be a <em>committer</em> first. Typically,
``commit privs'' after they have made a few well-thought out people are offered ''commit privs'' after they have made a
submissions to the project using Bugzilla or similar.</p> few well-thought out submissions to the project using
Bugzilla or similar.</p>
<p>This is identical to the Linux mechanism. Only one person is <p>This is identical to the Linux mechanism. Only one person is
(notionally) allowed to change the Kernel, Linus. But specific areas (notionally) allowed to change the Kernel, Linus. But specific areas
(such as the networking code) are delegated to other people.</p> (such as the networking code) are delegated to other people.</p>
<p><i>Aside: Nik (nik@FreeBSD.org) is a case in point. After making <p><i>Aside: Nik (nik@FreeBSD.org) is a case in point. After
several submissions to the FreeBSD Documentation Project and making several submissions to the &os; Documentation
web pages, he was offered ``commit privs'' so that he did not Project and web pages, he was offered ''commit privs'' so
have to keep bothering other committers to commit the changes. He that he did not have to keep bothering other committers to
never had to ask for them, they were freely given.</i></p></li> commit the changes. He never had to ask for them, they
were freely given.</i></p></li>
</ul> </ul>
<hr noshade="noshade" size="1"/> <hr noshade="noshade" size="1"/>
@ -210,8 +218,8 @@
desktop machine.</p> desktop machine.</p>
<p>*BSD has access to the same desktop tools (KDE, GNOME, Firefox, <p>*BSD has access to the same desktop tools (KDE, GNOME, Firefox,
windowmanagers) as Linux. And ``office'' applications such as windowmanagers) as Linux. And ''office'' applications such as
OpenOffice suite work under *BSD too.</p> LibreOffice suite work under *BSD too.</p>
<hr noshade="noshade" size="1"/> <hr noshade="noshade" size="1"/>
@ -294,10 +302,10 @@
systems (SunOS and similar). *BSD users can generally compile software systems (SunOS and similar). *BSD users can generally compile software
written for these systems without needing to make any changes.</p> written for these systems without needing to make any changes.</p>
<p>In addition, each *BSD project uses a ``ports'' system to make the <p>In addition, each *BSD project uses a ''ports'' system to make
building of ported software much easier.</p> the building of ported software much easier.</p>
<p><b>FreeBSD:</b> There are currently more than 26,000 <p><b>FreeBSD:</b> There are currently more than 30,000
applications ready to download and install in the FreeBSD ports applications ready to download and install in the FreeBSD ports
collection. On i386 and AMD64, the Linux emulation layer will collection. On i386 and AMD64, the Linux emulation layer will
also run the vast majority of Linux applications. On the AMD64 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 i386 Linux applications, and the majority of SunOS4 applications can be
run on a SPARCStation.</p> run on a SPARCStation.</p>
<p><b>OpenBSD:</b> There are currently more than 3700 applications <p><b>OpenBSD:</b> There are currently more than 8000 applications
ready to download and install in the OpenBSD ports collection. The Linux ready to download and install in the OpenBSD ports collection. The Linux
emulation layer will also run the vast majority of i386 Linux emulation layer will also run the vast majority of i386 Linux
applications, and the majority of SunOS4 applications can be run on a applications, and the majority of SunOS4 applications can be run on a