diff options
| -rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 50 | ||||
| -rw-r--r-- | documentation/ref-manual/ref-development-environment.xml | 60 |
2 files changed, 57 insertions, 53 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index b64036af61..4fae151432 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
| @@ -6,56 +6,6 @@ | |||
| 6 | 6 | ||
| 7 | <title>The Yocto Project Open Source Development Environment</title> | 7 | <title>The Yocto Project Open Source Development Environment</title> |
| 8 | 8 | ||
| 9 | <para> | ||
| 10 | This chapter helps you understand the Yocto Project as an open source development project. | ||
| 11 | In general, working in an open source environment is very different from working in a | ||
| 12 | closed, proprietary environment. | ||
| 13 | Additionally, the Yocto Project uses specific tools and constructs as part of its development | ||
| 14 | environment. | ||
| 15 | This chapter specifically addresses open source philosophy, using the | ||
| 16 | Yocto Project in a team environment, source repositories, Yocto Project | ||
| 17 | terms, licensing, the open source distributed version control system Git, | ||
| 18 | workflows, bug tracking, and how to submit changes. | ||
| 19 | </para> | ||
| 20 | |||
| 21 | <section id='open-source-philosophy'> | ||
| 22 | <title>Open Source Philosophy</title> | ||
| 23 | |||
| 24 | <para> | ||
| 25 | Open source philosophy is characterized by software development directed by peer production | ||
| 26 | and collaboration through an active community of developers. | ||
| 27 | Contrast this to the more standard centralized development models used by commercial software | ||
| 28 | companies where a finite set of developers produces a product for sale using a defined set | ||
| 29 | of procedures that ultimately result in an end product whose architecture and source material | ||
| 30 | are closed to the public. | ||
| 31 | </para> | ||
| 32 | |||
| 33 | <para> | ||
| 34 | Open source projects conceptually have differing concurrent agendas, approaches, and production. | ||
| 35 | These facets of the development process can come from anyone in the public (community) that has a | ||
| 36 | stake in the software project. | ||
| 37 | The open source environment contains new copyright, licensing, domain, and consumer issues | ||
| 38 | that differ from the more traditional development environment. | ||
| 39 | In an open source environment, the end product, source material, and documentation are | ||
| 40 | all available to the public at no cost. | ||
| 41 | </para> | ||
| 42 | |||
| 43 | <para> | ||
| 44 | A benchmark example of an open source project is the Linux kernel, which was initially conceived | ||
| 45 | and created by Finnish computer science student Linus Torvalds in 1991. | ||
| 46 | Conversely, a good example of a non-open source project is the | ||
| 47 | <trademark class='registered'>Windows</trademark> family of operating | ||
| 48 | systems developed by <trademark class='registered'>Microsoft</trademark> Corporation. | ||
| 49 | </para> | ||
| 50 | |||
| 51 | <para> | ||
| 52 | Wikipedia has a good historical description of the Open Source Philosophy | ||
| 53 | <ulink url='http://en.wikipedia.org/wiki/Open_source'>here</ulink>. | ||
| 54 | You can also find helpful information on how to participate in the Linux Community | ||
| 55 | <ulink url='http://ldn.linuxfoundation.org/book/how-participate-linux-community'>here</ulink>. | ||
| 56 | </para> | ||
| 57 | </section> | ||
| 58 | |||
| 59 | <section id="usingpoky-changes-collaborate"> | 9 | <section id="usingpoky-changes-collaborate"> |
| 60 | <title>Using the Yocto Project in a Team Environment</title> | 10 | <title>Using the Yocto Project in a Team Environment</title> |
| 61 | 11 | ||
diff --git a/documentation/ref-manual/ref-development-environment.xml b/documentation/ref-manual/ref-development-environment.xml index a30cefc391..b19058ed03 100644 --- a/documentation/ref-manual/ref-development-environment.xml +++ b/documentation/ref-manual/ref-development-environment.xml | |||
| @@ -5,12 +5,66 @@ | |||
| 5 | <chapter id='ref-development-environment'> | 5 | <chapter id='ref-development-environment'> |
| 6 | <title>The Yocto Project Development Environment</title> | 6 | <title>The Yocto Project Development Environment</title> |
| 7 | 7 | ||
| 8 | <para> | ||
| 9 | This chapter takes a look at the Yocto Project development | ||
| 10 | environment and also provides a detailed look at what goes on during | ||
| 11 | development in that environment. | ||
| 12 | The chapter provides Yocto Project Development environment concepts that | ||
| 13 | help you understand how work is accomplished in an open source environment, | ||
| 14 | which is very different as compared to work accomplished in a closed, | ||
| 15 | proprietary environment. | ||
| 16 | This chapter specifically addresses open source philosophy, using the | ||
| 17 | Yocto Project in a team environment, source repositories, Yocto Project | ||
| 18 | terms, licensing, the open source distributed version control system Git, | ||
| 19 | workflows, bug tracking, and how to submit changes. | ||
| 20 | </para> | ||
| 21 | |||
| 22 | <section id='open-source-philosophy'> | ||
| 23 | <title>Open Source Philosophy</title> | ||
| 24 | |||
| 25 | <para> | ||
| 26 | Open source philosophy is characterized by software development | ||
| 27 | directed by peer production and collaboration through an active | ||
| 28 | community of developers. | ||
| 29 | Contrast this to the more standard centralized development models | ||
| 30 | used by commercial software companies where a finite set of developers | ||
| 31 | produces a product for sale using a defined set of procedures that | ||
| 32 | ultimately result in an end product whose architecture and source | ||
| 33 | material are closed to the public. | ||
| 34 | </para> | ||
| 35 | |||
| 8 | <para> | 36 | <para> |
| 9 | This chapter takes a look at the Yocto Project development | 37 | Open source projects conceptually have differing concurrent agendas, |
| 10 | environment and also provides a detailed look at what goes on during | 38 | approaches, and production. |
| 11 | development in that environment. | 39 | These facets of the development process can come from anyone in the |
| 40 | public (community) that has a stake in the software project. | ||
| 41 | The open source environment contains new copyright, licensing, domain, | ||
| 42 | and consumer issues that differ from the more traditional development | ||
| 43 | environment. | ||
| 44 | In an open source environment, the end product, source material, | ||
| 45 | and documentation are all available to the public at no cost. | ||
| 12 | </para> | 46 | </para> |
| 13 | 47 | ||
| 48 | <para> | ||
| 49 | A benchmark example of an open source project is the Linux kernel, | ||
| 50 | which was initially conceived and created by Finnish computer science | ||
| 51 | student Linus Torvalds in 1991. | ||
| 52 | Conversely, a good example of a non-open source project is the | ||
| 53 | <trademark class='registered'>Windows</trademark> family of operating | ||
| 54 | systems developed by | ||
| 55 | <trademark class='registered'>Microsoft</trademark> Corporation. | ||
| 56 | </para> | ||
| 57 | |||
| 58 | <para> | ||
| 59 | Wikipedia has a good historical description of the Open Source | ||
| 60 | Philosophy | ||
| 61 | <ulink url='http://en.wikipedia.org/wiki/Open_source'>here</ulink>. | ||
| 62 | You can also find helpful information on how to participate in the | ||
| 63 | Linux Community | ||
| 64 | <ulink url='http://ldn.linuxfoundation.org/book/how-participate-linux-community'>here</ulink>. | ||
| 65 | </para> | ||
| 66 | </section> | ||
| 67 | |||
| 14 | <section id="development-concepts"> | 68 | <section id="development-concepts"> |
| 15 | <title>Development Concepts</title> | 69 | <title>Development Concepts</title> |
| 16 | 70 | ||