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

[Osier-mixon, Jeffrey]

Hi Chris,

The Yocto Project Advisory Board is pleased to welcome CyaSSL as Yocto
Project Compatible. You may now use the Yocto Project Compatible badge,
which is located at the download link below.

Please also download the Style Guide, which explains how to use the badges
to stay in compliance. This guide is still a draft, but should be finalized
soon. A guide specific to the badges is in the zip file.

Compatible: http://yoctoproject.org/bulk/Yocto_Project_Badge_Compatible.zip
Style Guide: http://yoctoproject
.org/bulk/Yocto_Project_StyleGuide_Logo_and_Badge_draft.pdf

In addition, I'd like to set up a brief profile page for CyaSSL on the Yocto
 Project website. If you have a logo and some introductory text you'd like
me to use, please send it on.

thanks


On Wed, Oct 10, 2012 at 8:47 AM, Yocto Project
<webmaster at yoctoproject.org>wrote:

> Submitted on Wednesday, 10 October 2012 - 8:47am
> Submitted by anonymous user: [174.45.76.142]
> Submitted values are:
>
>   --Contact information--
>     Organization: yaSSL
>     Project Name: CyaSSL Embedded SSL
>     Contact name: Chris Conlon
>     Contact email address: chris at yassl.com
>     URL to organization or product link:
>     http://yassl.com/yaSSL/**Products-cyassl.html<http://yassl.com/yaSSL/Products-cyassl.html>
>     Registration date: 10 October, 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?: No (explain below)
>  - If present, can the directories containing BitBake and
> OpenEmbedded-Core be clearly identified within the system and only contain
> those components?: No (explain below)
>  - 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?: Yes
>  - Are hardware support, configuration (distro) policy, and recipe
> metadata separated into different layers which do not depend on each
> other?: Yes
>  - 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?: No (explain below)
> Recommendations:
>  - Linux kernels are either based around LTSI kernel versions or a Yocto
> Project kernel version.: Yes
>  - 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: Regarding items 5 and 6, the project does not incude build
> system functionality (it provides Secure Sockets Layer functionality), thus
> does not need to directly include BitBake or OpenEmbedded-Core as
> components.  Regarding items 12 and 13, a test report has not been created
> in the meta-yassl layer yet.  The meta-yassl layer with the CyaSSL embedded
> SSL library recipe can be found on GitHub, here:
> https://github.com/cconlon/**meta-yassl<https://github.com/cconlon/meta-yassl>
> .
>
>
> The results of this submission may be viewed at:
> http://www.yoctoproject.org/**node/183/submission/21<http://www.yoctoproject.org/node/183/submission/21>
> ______________________________**_________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/yocto-ab<https://lists.yoctoproject.org/listinfo/yocto-ab>
>



-- 
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20121213/43bf4f29/attachment.html>