diff options
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 49 |
1 files changed, 45 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index f0bb08e1da..14f5ca1b56 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -528,15 +528,56 @@ | |||
528 | <title>How to Submit a Change</title> | 528 | <title>How to Submit a Change</title> |
529 | 529 | ||
530 | <para> | 530 | <para> |
531 | During the development process it is necessary to submit your changes to the maintainer | 531 | Contributions to the Yocto Project are very welcome. |
532 | of the project. | 532 | You should send patches to the Yocto Project mailing list to get it in front of the |
533 | Furthermore, in a collaborative environment it is necessary to have some sort of standard | 533 | Yocto Project Maintainer. |
534 | When you send your patch, be sure to include a "signed-off-by:" | ||
535 | line in the same style as required by the Linux kernel. | ||
536 | Adding this line signifies the developer has agreed to the Developer's Certificate of Origin 1.1 | ||
537 | as follows: | ||
538 | <literallayout class='monospaced'> | ||
539 | Developer's Certificate of Origin 1.1 | ||
540 | |||
541 | By making a contribution to this project, I certify that: | ||
542 | |||
543 | (a) The contribution was created in whole or in part by me and I | ||
544 | have the right to submit it under the open source license | ||
545 | indicated in the file; or | ||
546 | |||
547 | (b) The contribution is based upon previous work that, to the best | ||
548 | of my knowledge, is covered under an appropriate open source | ||
549 | license and I have the right under that license to submit that | ||
550 | work with modifications, whether created in whole or in part | ||
551 | by me, under the same open source license (unless I am | ||
552 | permitted to submit under a different license), as indicated | ||
553 | in the file; or | ||
554 | |||
555 | (c) The contribution was provided directly to me by some other | ||
556 | person who certified (a), (b) or (c) and I have not modified | ||
557 | it. | ||
558 | |||
559 | (d) I understand and agree that this project and the contribution | ||
560 | are public and that a record of the contribution (including all | ||
561 | personal information I submit with it, including my sign-off) is | ||
562 | maintained indefinitely and may be redistributed consistent with | ||
563 | this project or the open source license(s) involved. | ||
564 | </literallayout> | ||
565 | A Poky contributions tree (<filename>poky-contrib</filename>, | ||
566 | <filename>git://git.yoctoproject.org/poky-contrib.git</filename>) | ||
567 | exists for contributors to stage contributions. | ||
568 | If people desire such access, please ask on the mailing list. | ||
569 | Usually, the Yocto Project team will grant access to anyone with a proven track | ||
570 | record of good patches. | ||
571 | </para> | ||
572 | |||
573 | <para> | ||
574 | In a collaborative environment, it is necessary to have some sort of standard | ||
534 | or method through which you submit changes. | 575 | or method through which you submit changes. |
535 | Otherwise, things would get quite chaotic. | 576 | Otherwise, things would get quite chaotic. |
536 | </para> | 577 | </para> |
537 | 578 | ||
538 | <para> | 579 | <para> |
539 | When you submit a change or patch to the Yocto Project you must follow certain procedures. | 580 | When you submit a change or patch to the Yocto Project, you must follow certain procedures. |
540 | In particular, the headers in patches and the commit messages must follow a certain standard. | 581 | In particular, the headers in patches and the commit messages must follow a certain standard. |
541 | The general process is the same as described earlier in this chapter. | 582 | The general process is the same as described earlier in this chapter. |
542 | For complete details on how to create proper commit messages and patch headers see | 583 | For complete details on how to create proper commit messages and patch headers see |