documentation/dev-manual/dev-manual-newbie.xml: added more to contributing
The section on how to contribute changes to the YP resides in this development guide. I took additional information from the YP reference manual and merged it into the section here. (From yocto-docs rev: 945dd29417cf51044332114e499b08fe24ef3077) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
79bd1a1518
commit
c3e83278c6
|
@ -528,15 +528,56 @@
|
||||||
<title>How to Submit a Change</title>
|
<title>How to Submit a Change</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
During the development process it is necessary to submit your changes to the maintainer
|
Contributions to the Yocto Project are very welcome.
|
||||||
of the project.
|
You should send patches to the Yocto Project mailing list to get it in front of the
|
||||||
Furthermore, in a collaborative environment it is necessary to have some sort of standard
|
Yocto Project Maintainer.
|
||||||
|
When you send your patch, be sure to include 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>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
In a collaborative environment, it is necessary to have some sort of standard
|
||||||
or method through which you submit changes.
|
or method through which you submit changes.
|
||||||
Otherwise, things would get quite chaotic.
|
Otherwise, things would get quite chaotic.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
When you submit a change or patch to the Yocto Project you must follow certain procedures.
|
When you submit a change or patch to the Yocto Project, you must follow certain procedures.
|
||||||
In particular, the headers in patches and the commit messages must follow a certain standard.
|
In particular, the headers in patches and the commit messages must follow a certain standard.
|
||||||
The general process is the same as described earlier in this chapter.
|
The general process is the same as described earlier in this chapter.
|
||||||
For complete details on how to create proper commit messages and patch headers see
|
For complete details on how to create proper commit messages and patch headers see
|
||||||
|
|
Loading…
Reference in New Issue