1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
<chapter id='resources'>
<title>Contributing to the Yocto Project</title>
<section id='resources-intro'>
<title>Introduction</title>
<para>
The Yocto Project team is happy for people to experiment with the Yocto Project.
A number of places exist to find help if you run into difficulties or find bugs.
To find out how to download source code,
see the "<ulink url='&YOCTO_DOCS_DEV_URL;#local-yp-release'>Yocto Project Release</ulink>"
section in the Yocto Project Development Manual.
</para>
</section>
<section id='resources-bugtracker'>
<title>Yocto Project Bugzilla</title>
<para>
The Yocto Project uses its own implementation of
<ulink url='http://www.bugzilla.org/about/'>Bugzilla</ulink> to track
defects (bugs).
Implementations of Bugzilla work well for group development because
they track bugs and code changes, can be used to communicate changes
and problems with developers, can be used to submit and review patches,
and can be used to manage quality assurance.
</para>
<para>
Sometimes it is helpful to submit, investigate, or track a bug against
the Yocto Project itself (e.g. when discovering an issue with some
component of the build system that acts contrary to the documentation
or your expectations).
</para>
<para>
A general procedure and guidelines exist for when you use Bugzilla to
submit a bug.
For information on how to use Bugzilla to submit a bug against the
Yocto Project, see the following:
<itemizedlist>
<listitem><para>
The
"<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-defect-against-the-yocto-project'>Submitting a Defect Against the Yocto Project</ulink>"
section in the Yocto Project Development Manual.
</para></listitem>
<listitem><para>
The Yocto Project
<ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>Bugzilla wiki page</ulink>
</para></listitem>
</itemizedlist>
</para>
</section>
<section id='resources-mailinglist'>
<title>Mailing lists</title>
<para>
A number of mailing lists maintained by the Yocto Project exist
as well as related OpenEmbedded mailing lists for discussion,
patch submission and announcements.
To subscribe to one of the following mailing lists, click on the
appropriate URL in the following list and follow the instructions:
<itemizedlist>
<listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/yocto'></ulink> -
General Yocto Project discussion mailing list. </para></listitem>
<listitem><para><ulink url='&OE_LISTS_URL;/listinfo/openembedded-core'></ulink> -
Discussion mailing list about OpenEmbedded-Core (the core metadata).</para></listitem>
<listitem><para><ulink url='&OE_LISTS_URL;/listinfo/openembedded-devel'></ulink> -
Discussion mailing list about OpenEmbedded.</para></listitem>
<listitem><para><ulink url='&OE_LISTS_URL;/listinfo/bitbake-devel'></ulink> -
Discussion mailing list about the
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
build tool.</para></listitem>
<listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/poky'></ulink> -
Discussion mailing list about
<ulink url='&YOCTO_DOCS_DEV_URL;#poky'>Poky</ulink>.
</para></listitem>
<listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/yocto-announce'></ulink> -
Mailing list to receive official Yocto Project release and milestone
announcements.</para></listitem>
</itemizedlist>
</para>
For more Yocto Project-related mailing lists, see the Yocto Project community mailing lists page
<ulink url='&YOCTO_HOME_URL;/tools-resources/community/mailing-lists'>here</ulink>.
</section>
<section id='resources-irc'>
<title>Internet Relay Chat (IRC)</title>
<para>
Two IRC channels on freenode are available for the Yocto Project and Poky discussions:
<itemizedlist>
<listitem><para><filename>#yocto</filename></para></listitem>
<listitem><para><filename>#poky</filename></para></listitem>
</itemizedlist>
</para>
</section>
<section id='resources-links'>
<title>Links</title>
<para>
Here is a list of resources you will find helpful:
<itemizedlist>
<listitem><para><emphasis>
<ulink url='&YOCTO_HOME_URL;'>The Yocto Project website</ulink>:
</emphasis> The home site for the Yocto
Project.</para></listitem>
<!--
<listitem><para><emphasis>
<ulink url='http://www.intel.com/'>Intel Corporation</ulink>:</emphasis>
The company that acquired OpenedHand in 2008 and began
development on the Yocto Project.</para></listitem>
-->
<listitem><para><emphasis>
<ulink url='&OE_HOME_URL;'>OpenEmbedded</ulink>:</emphasis>
The upstream, generic, embedded distribution used as the basis
for the build system in the Yocto Project.
Poky derives from and contributes back to the OpenEmbedded
project.</para></listitem>
<listitem><para><emphasis>
<ulink url='http://www.openembedded.org/wiki/BitBake'>
BitBake</ulink>:</emphasis> The tool used to process metadata.</para></listitem>
</itemizedlist>
For more links, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#other-information'>Other Information</ulink>"
section in the Yocto Project Development Manual.
</para>
</section>
<section id='resources-contributions'>
<title>Contributions</title>
<para>
The Yocto Project gladly accepts contributions.
You can submit changes to the project either by creating and sending
pull requests,
or by submitting patches through email.
For information on how to do both as well as information on how
to identify the maintainer for each area of code, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
section in the Yocto Project Development Manual.
</para>
</section>
</chapter>
<!--
vim: expandtab tw=80 ts=4
-->
|
