[yocto-ab] Form submission from: Yocto Project Compatible Registration

[Yocto Project]

Submitted on Friday, 31 August 2012 - 5:46am
Submitted by anonymous user: [77.162.165.174]
Submitted values are:

   --Contact information--
     Organization: The Angstrom Distribution
     Project Name: The Angstrom Distribution
     Contact name: Koen Kooi
     Contact email address: koen at dominion.thruhere.net
     URL to organization or product link:
     http://www.angstrom-distribution.org
     Registration date: 31 August, 2012
     Yocto Project Compatible Version: 1.2
     Compliance Agreement revision: 1.0


Acceptance Criteria:
  - Working towards and supporting the aims and objectives of the Yocto  
Project. These include decreasing the fragmentation of embedded ecosystem and  
focus around a common shared set of tools, formats and best practices. We  
want to avoid multiple groups of people repeating the same work and have one  
set of great tools rather than multiple tools with drawbacks.: Yes
  - Promoting the OpenEmbedded architecture, layer model, and BSP format.: Yes
  - Making visible contributions in the OpenEmbedded and component projects of  
the Yocto Project.: Yes
  - Be an open source project, non-profit, or member of the Yocto Project  
working group, regardless of organization size.: Yes
  - If the project includes build system functionality, are BitBake and  
OpenEmbedded-Core included as components?: Yes
  - If present, can the directories containing BitBake and OpenEmbedded-Core  
be clearly identified within the system and only contain those components?:  
Yes
  - Have all patches applied to BitBake and OpenEmbedded-Core (if present)  
been submitted to the open source community?: Yes
  - Do all layers contain a README file which details the origin of the layer,  
its maintainer, where to submit changes, and any dependencies or version  
requirements?: Yes
  - Do all layers build without errors against OpenEmbedded-Core with only the  
dependencies/requirements listed in their README file?: Yes
  - (For BSPs) Does the layer follow the format defined in the Yocto Project  
Board Support Package (BSP) Developers Guide?: No (explain below)
  - Are hardware support, configuration (distro) policy, and recipe metadata  
separated into different layers which do not depend on each other?: No  
(explain below)
  - Is a test report document included showing which combinations of layers,  
recipes, and machines have been tested?: No (explain below)
  - If any item in the "Yocto Project Compatible Compliance Recommendations"  
list is not true, is this documented in the testing report?: Yes
Recommendations:
  - Linux kernels are either based around LTSI kernel versions or a Yocto  
Project kernel version.: No (explain below)
  - Everything builds successfully with the standard toolchain from OE-Core,  
where the architecture is one supported by OE-Core as standard. This is to  
ensure that your layers are compatible with OE-Core. It is not required that  
the OE-Core toolchain be provided to customers or any downstream projects.:  
Yes
Explanation:
* Angstrom is not a BSP, so those questions don't apply.

* The angstrom layer depends on a few other layers (e.g. oe-core), so the  
layer *do* depends on eachother. I must admit that I'm confused by the  
question.

* There's not a test report document, but on the build side the buildhistory  
repository is online: https://github.com/Angstrom-distribution/buildhistory.  
The rule of thumb is that only BSP layers that are tested are enabled in the  
angstrom setup-scripts, so the scetup-scripts are the result of the tests.  
I'm not sure how a testing document would look for a distro and how it would  
scale.



The results of this submission may be viewed at:
http://www.yoctoproject.org/node/183/submission/16