The technical leadership structure for the Yocto Project is hierarchical and based on a meritocracy presided over by a "benevolent dictator", similar to that of the Linux kernel. The project architect at the top is responsible for all decisions and actions, and also functions as a default maintainer for those subsystems and layers who do not have a current maintainer. A tree of maintainers works underneath the architect - these maintainers handle the details of many of the bugs, patches, and ideas that come up.

Yocto Project Architect

• Richard Purdie

Sub-system and BSP/Layer Maintainers

Note that not all layers are represented on this list. For up-to-date information on maintainers for individual layers, visit the source code repository, click a layer, click "tree", and then read the README or MAINTAINERS file for that layer.

• Documentation - Scott Rifenbark
• linux-yocto Kernel + Tooling - Bruce Ashfield
• Poky Reference Distribution - Richard Purdie
• Pseudo - Mark Hatle
• Autobuilder - Beth Flanagan
• BitBake - Richard Purdie
• Mentor Graphics Layer - Chris Larson
• SE Linux Layer - Mark Hatle
• Eclipse Integration - Todor Minchev
• Intel BSPs - Saul Wold
• Freescale BSPs - tbd
• TI BSPs - Denys  Dmytriyenk
• Matchbox - Ross Burton
• OpenEmbedded Core - Richard Purdie
  • Build history - Paul Eggleton
  • musl/uclibc - Khem Raj
  • Sato/GTK/Dbus - Ross Burton
  • License Wrangling: Beth Flanagan
  • User Space - Ross Burton
  • User Space & RPM - Mark Hatle
  • Extensible SDK - Paul Eggleton
  • Core Infrastucture - Paul Eggleton
  • Security Contact - Saul Wold
  • Cross-prelink - Mark Hatle
  • Darwin SDK Support - Juro Bystricky
  • MingW SDK Support - Juro Bystricky
  • meta-virtualization - Bruce Ashfield
  • meta-xlinx - Nathan Rossi/Sipke Vriend

Each release also has its own maintainer:

• OE-Core 1.4 - Paul Eggleton
• OE-Core 1.5 - Robert Yang
• OE-Core 1.6 - Saul Wold
• OE-Core 1.7 - Armin Kuster
• OE-Core 1.8 - Joshua Lock
• OE-Core 2.0 - Robert Yang