I am not able to find documentation (wiki or otherwise) that explains what, where and how to contribute to the Yocto Project, OE-Core and/or bitbake. The documentation should include information: *) Generating git patches using the oe-core "create-pull-request" *) Determining where a patch set needs to be sent [based on directory] General rules: bitbake - bitbake-devel mailing list oe-core components - openembedded-core mailing list yocto components - poky? or yocto? mailing lists
Comments from someone new to yocto: I don't want more nested web pages... As an outsider looking in, I was simply wanting to know if you changed things in these directories submit patch (of course conforming to guidelines hyper link here) to X@X.LIST In kernel land it is easy, they provide a script that tells you who to send things to or you can look at the MAINTAINERS file yourself. You can always link to the MAINTAINERS file in the git tree, if one is created.
Section 3.8 of the Yocto Project Development Manual addresses this bug. I am marking it resolved and fixed.
I believe there is a second aspect to this, not documentation based but an enhancement to the source tree itself. Adding a maintainer -- readme or similar file to the sources. We've had discussions within the Open Embedded TSC on this, but have had no final conclusion. I'm going to reopen this, and assign it to myself to until we resolve that issue.
okay - Let me know if any further enhancements to the docs need to be applied.
I've been harping on the including of maintainers on patches, so I'm interested in helping here as well. For Yocto there is the distro-tracking file, but this really needs to be better integrated into oe-core.
Changing the target milestone to 1.3 as the remaining work will be completed in that timeframe.
Is this bug still supposed to be assigned to me? It still is. Comment history shows that Mark should have it. Scott
We now have readmes in all repos and its part of the Yocto Project Compatible standard.