Source string Read only

(itstool) path: sect1/title

12/120
Context English State
_ translator-credits
Building Products with FreeBSD
<email>jkoshy@FreeBSD.org</email>
<personname><firstname>Joseph</firstname><surname>Koshy</surname></personname><affiliation> <orgname>The FreeBSD Project</orgname> <_:address-1/> </affiliation>
FreeBSD is a registered trademark of the FreeBSD Foundation.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/building-products/article.xml 54253 2020-06-14 08:10:06Z carlavilla $
Abstract
The FreeBSD project is a worldwide, volunteer based, and collaborative project, which develops a portable and high-quality operating system. The FreeBSD project distributes the source code for its product under a liberal license, with the intention of encouraging the use of its code. Collaborating with the FreeBSD project can help organizations reduce their time to market, reduce engineering costs and improve their product quality.
This article examines the issues in using FreeBSD code in appliances and software products. It highlights the characteristics of FreeBSD that make it an excellent substrate for product development. The article concludes by suggesting a few <quote>best practices</quote> for organizations collaborating with the FreeBSD project.
Introduction
FreeBSD today is well-known as a high-performance server operating system. It is deployed on millions of web servers and internet-facing hosts worldwide. FreeBSD code also forms an integral part of many products, ranging from appliances such as network routers, firewalls, and storage devices, to personal computers. Portions of FreeBSD have also been used in commercial shrink-wrapped software (see <xref linkend="freebsd-intro"/>).
In this article we look at the <link xlink:href="@@URL_RELPREFIX@@/">FreeBSD project</link> as a software engineering resource—as a collection of building blocks and processes which you can use to build products.
While FreeBSD's source is distributed freely to the public, to fully enjoy the benefits of the project's work, organizations need to <emphasis>collaborate</emphasis> with the project. In subsequent sections of this article we discuss effective means of collaboration with the project and the pitfalls that need to be avoided while doing so.
Caveat Reader
The author believes that the characteristics of the FreeBSD Project listed in this article were substantially true at the time the article was conceived and written (2005). However, the reader should keep in mind that the practices and processes used by open-source communities can change over time, and that the information in this article should therefore be taken as indicative rather than normative.
Target Audience
This document would be of interest to the following broad groups of people:
Decision makers in product companies looking at ways to improve their product quality, reduce their time to market and lower engineering costs in the long term.
Technology consultants looking for best-practices in leveraging <quote>open-source</quote>.
Industry observers interested in understanding the dynamics of open-source projects.
Software developers seeking to use FreeBSD and looking for ways to contribute back.
Article Goals
After reading this article you should have:
An understanding of the goals of the FreeBSD Project and its organizational structure.
An understanding of its development model and release engineering processes.
ComponentTranslation
This translation Translated FreeBSD Doc/articles_building-products Introduction
The following strings have the same context and source.
Translated FreeBSD Doc/articles_gjournal-desktop Introduction
Translated FreeBSD Doc/articles_leap-seconds Introduction
Translated FreeBSD Doc/articles_linux-emulation Introduction
Translated FreeBSD Doc/articles_mailing-list-faq Introduction
Translated FreeBSD Doc/articles_pam Introduction
Translated FreeBSD Doc/articles_pr-guidelines Introduction
Translated FreeBSD Doc/articles_freebsd-update-server Introduction
Translated FreeBSD Doc/articles_vm-design Introduction
Translated FreeBSD Doc/articles_linux-users Introduction
Translated FreeBSD Doc/articles_geom-class Introduction
Translated FreeBSD Doc/articles_problem-reports Introduction
Translated FreeBSD Doc/articles_releng Introduction
Translated FreeBSD Doc/articles_committers-guide Introduction
Translated FreeBSD Doc/books_arch-handbook Introduction
Translated FreeBSD Doc/articles_bsdl-gpl Introduction
Translated FreeBSD Doc/books_faq Introduction
Translated FreeBSD Doc/books_developers-handbook Introduction
Translated FreeBSD Doc/books_fdp-primer Introduction
Translated FreeBSD Doc/books_handbook Introduction
Translated FreeBSD Doc/articles_fonts Introduction
Translated FreeBSD Doc/books_porters-handbook Introduction
Translated FreeBSD Doc/articles_rc-scripting Introduction
Translated FreeBSD Doc/articles_remote-install Introduction
Translated FreeBSD Doc/articles_freebsd-questions Introduction

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: sect1/title

Flags
read-only
Source string location
article.translate.xml:50
String age
a year ago
Source string age
a year ago
Translation file
articles/building-products.pot, string 11