1*4882a593SmuzhiyunOpenEmbedded-Core and Yocto Project Maintainer Information 2*4882a593Smuzhiyun========================================================== 3*4882a593Smuzhiyun 4*4882a593SmuzhiyunOpenEmbedded and Yocto Project work jointly together to maintain the metadata, 5*4882a593Smuzhiyunlayers, tools and sub-projects that make up their ecosystems. 6*4882a593Smuzhiyun 7*4882a593SmuzhiyunThe projects operate through collaborative development. This currently takes 8*4882a593Smuzhiyunplace on mailing lists for many components as the "pull request on github" 9*4882a593Smuzhiyunworkflow works well for single or small numbers of maintainers but we have 10*4882a593Smuzhiyuna large number, all with different specialisms and benefit from the mailing 11*4882a593Smuzhiyunlist review process. Changes therefore undergo peer review through mailing 12*4882a593Smuzhiyunlists in many cases. 13*4882a593Smuzhiyun 14*4882a593SmuzhiyunThis file aims to acknowledge people with specific skills/knowledge/interest 15*4882a593Smuzhiyunboth to recognise their contributions but also empower them to help lead and 16*4882a593Smuzhiyuncurate those components. Where we have people with specialist knowledge in 17*4882a593Smuzhiyunparticular areas, during review patches/feedback from these people in these 18*4882a593Smuzhiyunareas would generally carry weight. 19*4882a593Smuzhiyun 20*4882a593SmuzhiyunThis file is maintained in OE-Core but may refer to components that are separate 21*4882a593Smuzhiyunto it if that makes sense in the context of maintainership. The README of specific 22*4882a593Smuzhiyunlayers and components should ultimately be definitive about the patch process and 23*4882a593Smuzhiyunmaintainership for the component. 24*4882a593Smuzhiyun 25*4882a593SmuzhiyunRecipe Maintainers 26*4882a593Smuzhiyun------------------ 27*4882a593Smuzhiyun 28*4882a593SmuzhiyunSee meta/conf/distro/include/maintainers.inc 29*4882a593Smuzhiyun 30*4882a593SmuzhiyunComponent/Subsystem Maintainers 31*4882a593Smuzhiyun------------------------------- 32*4882a593Smuzhiyun 33*4882a593Smuzhiyun* Kernel (inc. linux-yocto, perf): Bruce Ashfield 34*4882a593Smuzhiyun* Reproducible Builds: Joshua Watt 35*4882a593Smuzhiyun* Toaster: David Reyna 36*4882a593Smuzhiyun* Hash-Equivalence: Joshua Watt 37*4882a593Smuzhiyun* Recipe upgrade infrastructure: Alex Kanavin 38*4882a593Smuzhiyun* Toolchain: Khem Raj 39*4882a593Smuzhiyun* ptest-runner: Aníbal Limón 40*4882a593Smuzhiyun* opkg: Alex Stewart 41*4882a593Smuzhiyun* devtool: Saul Wold 42*4882a593Smuzhiyun* eSDK: Saul Wold 43*4882a593Smuzhiyun* overlayfs: Vyacheslav Yurkov 44*4882a593Smuzhiyun 45*4882a593SmuzhiyunMaintainers needed 46*4882a593Smuzhiyun------------------ 47*4882a593Smuzhiyun 48*4882a593Smuzhiyun* Pseudo 49*4882a593Smuzhiyun* Layer Index 50*4882a593Smuzhiyun* recipetool 51*4882a593Smuzhiyun* QA framework/automated testing 52*4882a593Smuzhiyun* error reporting system/web UI 53*4882a593Smuzhiyun* wic 54*4882a593Smuzhiyun* Patchwork 55*4882a593Smuzhiyun* Patchtest 56*4882a593Smuzhiyun* Prelink-cross 57*4882a593Smuzhiyun* Matchbox 58*4882a593Smuzhiyun* Sato 59*4882a593Smuzhiyun* Autobuilder 60*4882a593Smuzhiyun 61*4882a593SmuzhiyunLayer Maintainers needed 62*4882a593Smuzhiyun------------------------ 63*4882a593Smuzhiyun 64*4882a593Smuzhiyun* meta-gplv2 (ideally new strategy but active maintainer welcome) 65*4882a593Smuzhiyun 66*4882a593SmuzhiyunShadow maintainers/development needed 67*4882a593Smuzhiyun-------------------------------------- 68*4882a593Smuzhiyun 69*4882a593Smuzhiyun* toaster 70*4882a593Smuzhiyun* bitbake 71*4882a593Smuzhiyun 72*4882a593Smuzhiyun 73