mirror of
https://git.yoctoproject.org/poky
synced 2026-05-09 17:39:31 +00:00
Scott Rifenbark
ae06e04cd2
Creation involved removing the overview-manual and replacing it with the getting-started manual. All links to the string "&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with "&YOCTO_DOCS_GS_URL" across the entire YP manual set. I renamed files used to create the manual with prefixes suited for the new manual name, which is "Getting Started With Yocto Project". The style sheet for the new manual needed updating to display the new .PNG image for the title page. The mega-manual file had to be updated to include the files. The mega-manual.sed file had to be updated to include the new manual and not use the overview manual. (From yocto-docs rev: 6c7abf9192390121000f577d6c98f259d290d15d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
55 lines
2.8 KiB
HTML
55 lines
2.8 KiB
HTML
<html>
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||
<title>2.2. Open Source Philosophy</title>
|
||
<link rel="stylesheet" type="text/css" href="../book.css">
|
||
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
|
||
<link rel="home" href="index.html" title="Getting Started With Yocto Project">
|
||
<link rel="up" href="overview-development-environment.html" title="Chapter 2. The Yocto Project Development Environment">
|
||
<link rel="prev" href="yp-intro.html" title="2.1. Introduction">
|
||
<link rel="next" href="workflows.html" title="2.3. Workflows">
|
||
</head>
|
||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.2. Open Source Philosophy">
|
||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||
<a name="open-source-philosophy"></a>2.2. Open Source Philosophy</h2></div></div></div>
|
||
<p>
|
||
Open source philosophy is characterized by software development
|
||
directed by peer production and collaboration through an active
|
||
community of developers.
|
||
Contrast this to the more standard centralized development models
|
||
used by commercial software companies where a finite set of developers
|
||
produces a product for sale using a defined set of procedures that
|
||
ultimately result in an end product whose architecture and source
|
||
material are closed to the public.
|
||
</p>
|
||
<p>
|
||
Open source projects conceptually have differing concurrent agendas,
|
||
approaches, and production.
|
||
These facets of the development process can come from anyone in the
|
||
public (community) that has a stake in the software project.
|
||
The open source environment contains new copyright, licensing, domain,
|
||
and consumer issues that differ from the more traditional development
|
||
environment.
|
||
In an open source environment, the end product, source material,
|
||
and documentation are all available to the public at no cost.
|
||
</p>
|
||
<p>
|
||
A benchmark example of an open source project is the Linux kernel,
|
||
which was initially conceived and created by Finnish computer science
|
||
student Linus Torvalds in 1991.
|
||
Conversely, a good example of a non-open source project is the
|
||
<span class="trademark">Windows</span>® family of operating
|
||
systems developed by
|
||
<span class="trademark">Microsoft</span>® Corporation.
|
||
</p>
|
||
<p>
|
||
Wikipedia has a good historical description of the Open Source
|
||
Philosophy
|
||
<a class="ulink" href="http://en.wikipedia.org/wiki/Open_source" target="_self">here</a>.
|
||
You can also find helpful information on how to participate in the
|
||
Linux Community
|
||
<a class="ulink" href="http://ldn.linuxfoundation.org/book/how-participate-linux-community" target="_self">here</a>.
|
||
</p>
|
||
</div></body>
|
||
</html>
|