documentation/poky-ref-manual/resources.xml: re-write for today's world.

This chapter was quite old as it had not been touched since the original
Poky Handbook days.  I re-wrote the sub-sections with today in mind.

(From yocto-docs rev: e59bede734a8fe3e9b41698e2b42ba487ec80595)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2011-08-25 15:20:56 -07:00 committed by Richard Purdie
parent dd92838748
commit ffbed4c03a
1 changed files with 88 additions and 116 deletions

View File

@ -7,19 +7,22 @@
<section id='resources-intro'>
<title>Introduction</title>
<para>
We're happy for people to experiment with Poky and there are a number of places to
find help if you run into difficulties or find bugs. To find out how to download
source code see the <link linkend='intro-getit'>Obtaining Poky</link> section of
the Introduction.
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='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#local-yp-release'>
Yocto Project Release</ulink> list item in
<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>The Yocto
Project Development Manual</ulink>.
</para>
</section>
<section id='resources-bugtracker'>
<title>Bugtracker</title>
<title>Tracking Bugs</title>
<para>
Problems with Poky should be reported using the Bugzilla application at
<ulink url='http://bugzilla.yoctoproject.org/'></ulink>.
If you find problems with the Yocto Project, you should report them using the
Bugzilla application at <ulink url='http://bugzilla.yoctoproject.org/'></ulink>.
</para>
</section>
@ -27,26 +30,17 @@
<title>Mailing lists</title>
<para>
To subscribe to the mailing lists click on the following URLs and follow the instructions:
To subscribe to the Yocto Project mailing lists, click on the following URLs and follow the instructions:
<itemizedlist>
<listitem><para><ulink url='http://lists.yoctoproject.org/listinfo/yocto'></ulink> for a
Yocto Discussions mailing list.</para></listitem>
<listitem><para><ulink url='http://lists.yoctoproject.org/listinfo/poky'></ulink> for a
Yocto Project Discussions mailing list.</para></listitem>
<listitem><para><ulink url='http://lists.yoctoproject.org/listinfo/yocto-announce'></ulink> for a
mailing list to receive offical Yocto Project announcements for developments and
as well as Yocto Project milestones.</para></listitem>
</itemizedlist>
</para>
<itemizedlist>
<listitem><para>
<ulink url='http://lists.yoctoproject.org/listinfo/yocto'></ulink> for a Yocto Discussions
mailing list.
</para></listitem>
<listitem><para>
<ulink url='http://lists.yoctoproject.org/listinfo/poky'></ulink> for a Poky Discussions
mailing list.
</para></listitem>
<listitem><para>
<ulink url='http://lists.yoctoproject.org/listinfo/yocto-announce'></ulink> for a mailing list
to receive offical Yocto Project announcements for developments and milestones.
</para></listitem>
</itemizedlist>
</section>
<section id='resources-irc'>
@ -54,111 +48,89 @@
<para>
Two IRC channels on freenode are available for Yocto Project and Poky discussions:
<itemizedlist>
<listitem><para>
#yocto
</para></listitem>
<listitem><para>
#poky
</para></listitem>
</itemizedlist>
<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>
<itemizedlist>
<listitem><para>
<ulink url='http://yoctoproject.org'>The Yocto Project website</ulink> - The home site
for the Yocto Project.
</para></listitem>
<!-- <listitem><para>
<ulink url='http://pokylinux.org'>The Poky website</ulink> - The home site
for Poky Linux.
</para></listitem>
-->
<listitem><para>
<ulink url='http://www.openedhand.com/'>OpenedHand</ulink> - The
original company behind Poky.
</para></listitem>
<listitem><para>
<ulink url='http://www.intel.com/'>Intel Corporation</ulink> - The
company who acquired OpenedHand in 2008.
</para></listitem>
<listitem><para>
<ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>
- The upstream generic embedded distribution Poky derives
from (and contributes to).
</para></listitem>
<listitem><para>
<ulink url='http://developer.berlios.de/projects/bitbake/'>Bitbake</ulink>
- The tool used to process Poky metadata.
</para></listitem>
<listitem><para>
<ulink url='http://bitbake.berlios.de/manual/'>BitBake User
Manual</ulink> - A comprehensive guide to the BitBake tool.
</para></listitem>
<listitem><para>
<ulink url='http://pimlico-project.org/'>Pimlico</ulink> - A
suite of lightweight Personal Information Management (PIM)
applications designed primarily for handheld and mobile
devices.
</para></listitem>
<listitem><para>
<ulink url='http://fabrice.bellard.free.fr/qemu/'>QEMU</ulink>
- An open source machine emulator and virtualizer.
</para></listitem>
</itemizedlist>
<para>
Following is a list of resources you will find helpful:
<itemizedlist>
<listitem><para><emphasis><ulink url='http://yoctoproject.org'>The Yocto Project website</ulink>:
</emphasis> The home site for the Yocto Project.</para></listitem>
<listitem><para><emphasis><ulink url='http://www.openedhand.com/'>OpenedHand</ulink>:</emphasis>
The company where the Yocto Project build system Poky was first developed.
OpenedHand has since been acquired by Intel Corporation.</para></listitem>
<listitem><para><emphasis><ulink url='http://www.intel.com/'>Intel Corporation</ulink>:</emphasis>
The company who acquired OpenedHand in 2008 and continues development on the
Yocto Project.</para></listitem>
<listitem><para><emphasis><ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>:</emphasis>
The upstream, generic, embedded distribution the Yocto Project build system (Poky) derives
from and to which it contributes.</para></listitem>
<listitem><para><emphasis><ulink url='http://developer.berlios.de/projects/bitbake/'>
Bitbake</ulink>:</emphasis> The tool used to process Yocto Project metadata.</para></listitem>
<listitem><para><emphasis><ulink url='http://bitbake.berlios.de/manual/'>
BitBake User Manual</ulink>:</emphasis> A comprehensive guide to the BitBake tool.
</para></listitem>
<listitem><para><emphasis><ulink url='http://pimlico-project.org/'>Pimlico</ulink>:</emphasis>
A suite of lightweight Personal Information Management (PIM) applications designed
primarily for handheld and mobile devices.</para></listitem>
<listitem><para><emphasis><ulink url='http://wiki.qemu.org/Index.html'>QEMU</ulink>:
</emphasis> An open source machine emulator and virtualizer.</para></listitem>
</itemizedlist>
</para>
</section>
<section id='resources-contributions'>
<title>Contributions</title>
<para>
Contributions to Poky are very welcome. Patches should be sent to the Poky mailing list along with a Signed-off-by: line in the same style as the Linux kernel. Adding this line signifies the developer has agreed to the Developer's Certificate of Origin 1.1:
Contributions to the Yocto Project are very welcome.
You should send patches to the Yocto Project mailing list along with a "signed-off-by:"
line in the same style as required by the Linux kernel.
Adding this line signifies the developer has agreed to the Developer's Certificate of Origin 1.1
as follows:
<literallayout class='monospaced'>
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
</literallayout>
A Poky contributions tree (<filename>poky-contrib</filename>,
<filename>git://git.yoctoproject.org/poky-contrib.git</filename>)
exists for contributors to stage contributions.
If people desire such access, please ask on the mailing list.
Usually, the Yocto Project team will grant access to anyone with a proven track
record of good patches.
</para>
<programlisting>
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
</programlisting>
<para>
A Poky contributions tree (poky-contrib, git://git.yoctoproject.org/poky-contrib.git)
exists for people to stage contributions in, for regular contributors.
If people desire such access, please ask on the mailing list. Usually
access will be given to anyone with a proven track record of good patches.
</para>
</section>
</appendix>
<!--
vim: expandtab tw=80 ts=4