Source string Read only

(itstool) path: varlistentry/term
20/200
Context English State
The FreeBSD core team<anchor xml:id="development-core"/>
<primary>core team</primary>
The <firstterm>FreeBSD core team</firstterm> <_:indexterm-1/> 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. The current core team was elected from a pool of committer candidates in June 2020. Elections are held every 2 years.
Like most developers, most members of the core team are also volunteers when it comes to FreeBSD development and do not benefit from the project financially, so <quote>commitment</quote> should also not be misconstrued as meaning <quote>guaranteed support.</quote> The <quote>board of directors</quote> analogy above is not 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!
Outside 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. The primary way of keeping in touch with FreeBSD's more non-centralized development is to subscribe to the <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers">FreeBSD technical discussions mailing list</link> where such things are discussed. See <xref linkend="eresources"/> for more information about the various FreeBSD mailing lists.
<primary>contributors</primary>
<citetitle><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/article.html">The FreeBSD Contributors List</link></citetitle> <_:indexterm-1/> is a long and growing one, so why not join it by contributing something back to FreeBSD today?
Providing code is not the only way of contributing to the project; for a more complete list of things that need doing, please refer to the <link xlink:href="@@URL_RELPREFIX@@/index.html">FreeBSD Project web site</link>.
In summary, our development model is organized as a loose set of concentric circles. The centralized model is designed for the convenience of the <emphasis>users</emphasis> of FreeBSD, who are provided with an easy way of tracking one central code base, not to keep potential contributors out! Our desire is to present a stable operating system with a large set of coherent <link linkend="ports">application programs</link> that the users can easily install and use — 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!
Third Party Programs
In addition to the base distributions, FreeBSD offers a ported software collection with thousands of commonly sought-after programs. At the time of this writing, there were over 24,000 ports! The list of ports ranges from http servers, to games, languages, editors, and almost everything in between. The entire Ports Collection requires approximately 500 MB. To compile a port, you simply change to the directory of the program you wish to install, type <command>make install</command>, and let the system do the rest. The full original distribution for each port you build is retrieved dynamically so you need only enough disk space to build the ports you want. Almost every port is also provided as a pre-compiled <quote>package</quote>, which can be installed with a simple command (<command>pkg install</command>) by those who do not wish to compile their own ports from source. More information on packages and ports can be found in <xref linkend="ports"/>.
Additional Documentation
All supported FreeBSD versions provide an option in the installer to install additional documentation under <filename>/usr/local/share/doc/freebsd</filename> during the initial system setup. Documentation may also be installed at any later time using packages as described in <xref linkend="doc-ports-install-package"/>. You may view the locally installed manuals with any HTML capable browser using the following URLs:
The FreeBSD Handbook
<link xlink:href="file://localhost/usr/local/share/doc/freebsd/handbook/index.html"><filename>/usr/local/share/doc/freebsd/handbook/index.html</filename></link>
The FreeBSD FAQ
<link xlink:href="file://localhost/usr/local/share/doc/freebsd/faq/index.html"><filename>/usr/local/share/doc/freebsd/faq/index.html</filename></link>
You can also view the master (and most frequently updated) copies at <uri xlink:href="https://www.FreeBSD.org/">https://www.FreeBSD.org/</uri>.
Installing FreeBSD
<personname> <firstname>Gavin</firstname> <surname>Atkinson</surname> </personname> <contrib>Updated for bsdinstall by </contrib>
<personname> <firstname>Warren</firstname> <surname>Block</surname> </personname>
<personname> <firstname>Allan</firstname> <surname>Jude</surname> </personname> <contrib>Updated for root-on-ZFS by </contrib>
<primary>installation</primary>
There are several different ways of getting FreeBSD to run, depending on the environment. Those are:
Virtual Machine images, to download and import on a virtual environment of choice. These can be downloaded from the <link xlink:href="https://www.freebsd.org/where.html">Download FreeBSD</link> page. There are images for KVM (<quote>qcow2</quote>), VMWare (<quote>vmdk</quote>), Hyper-V (<quote>vhd</quote>), and raw device images that are universally supported. These are not installation images, but rather the preconfigured (<quote>already installed</quote>) instances, ready to run and perform post-installation tasks.
Virtual Machine images available at Amazon's <link xlink:href="https://aws.amazon.com/marketplace/pp/B07L6QV354">AWS Marketplace</link>, <link xlink:href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps?search=freebsd&amp;page=1">Microsoft Azure Marketplace</link>, and <link xlink:href="https://console.cloud.google.com/marketplace/details/freebsd-cloud/freebsd-12">Google Cloud Platform</link>, to run on their respective hosting services. For more information on deploying FreeBSD on Azure please consult the relevant chapter in the <link xlink:href="https://docs.microsoft.com/en-us/azure/virtual-machines/linux/freebsd-intro-on-azure">Azure Documentation</link>.
SD card images, for embedded systems such as Raspberry Pi or BeagleBone Black. These can be downloaded from the <link xlink:href="https://www.freebsd.org/where.html">Download FreeBSD</link> page. These files must be uncompressed and written as a raw image to an SD card, from which the board will then boot.
Installation images, to install FreeBSD on a hard drive for the usual desktop, laptop, or server systems.
The rest of this chapter describes the fourth case, explaining how to install FreeBSD using the text-based installation program named <application>bsdinstall</application>.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: varlistentry/term
Flags
read-only
Source string location
book.translate.xml:2768
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 341