The Ångström Distribution

Angstrom is using OpenEmbedded as buildsystem and heavily uses its layer features. Let's take the v2012.05 release (which matches the yocto 1.2 ('denzil') release) as an example. All layers have their patch submission policy documented in a README file in each layer. Here is a summary of those:

• bitbake, the task executor for the build metadata. Send patches to the mailinglist: http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
• meta-angstrom, the angstrom distribution layer. Send patches to the mailinglist: http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-deve...
• meta-openembedded, the openembedded community repository containing a lot of sub layers. Every sublayer has a README on how to handle patches, but the rule of thumb is to send them to http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-oe]' tag.
• meta-ti, the TI BSP and SoC support layer, send patches to the mailinglist: https://lists.yoctoproject.org/listinfo/meta-ti
• meta-ettus, the BSP layer for Ettus products, github pull-requests work best
• meta-efikamx, the BSP layer for the efika-mx board, github pull-requests work best
• meta-nslu2, the BSP layer for ixp4xx based machines, github pull-requests work best
• meta-smartphone, layer for smartphone recipes and BSPs. See the READMEs of the sublayers.
• meta-intel, the BSP layer for intel chipsets, send patches to the mailinglist: https://lists.yoctoproject.org/listinfo/yocto
• meta-xilinx, the BSP layer for xilinx based boards, send patches to the mailinglist: https://lists.yoctoproject.org/listinfo/yocto
• meta-openpandora, the BSP layer for the openpandora device, github pull-requests work best
• meta-raspberrypi, the BSP layer for the raspberry-pi board, github pull-requests work best
• meta-handheld, a BSP layer for old (and not so old) handheld devices. Send patches to the mailinglist http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-handheld]' tag
• meta-opie, a layer with recipes for the OPIE project. Send patches to the mailinglist http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-opie]' tag
• meta-java, a layer with java related recipes (e.g. openjdk), Send patches to the mailinglist http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-java]' tag
• meta-browser, browser related recipes (firefox, chromium, etc). Send patches to the mailinglist http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-browser]' tag
• meta-mono, C# related recipes. Send patches as attachment to the maintainer, Autif Khan (autif.mlist@gmail.com).
• meta-kde, KDE recipes. Send patches to the mailinglist http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel with a '[meta-kde]' tag
• openembedded-core, the core layer, send patches to the mailinglist: http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

For the specific example of the v2012.05 release there are some extra steps involved since only backports are allowed in the release branches of the various layers. Whenever possible do your patch on the 'next' branch of the setup-scripts to track the latest upstream and then get it accepted upstream and ask for a backport to the matching release branch. Policy on that varies, but adding a '[for-denzil]' tag to your emails will usually do the trick.

Of the above layers only the meta-angstrom layer is controlled by angstrom developers, all other layers are out of angstrom control.