[yocto-ab] Terminology - Some draft definitions

[Ed Nash]

On 05/16/2011 07:50 AM, Richard Purdie wrote:
> In the last steering group meeting I promised to write something down about what
> some of the words we use mean, particularly what OE, Poky and Yocto all
> mean. What follows is a first draft style start at this:

Thanks Richard for getting this started.

> Yocto Project - The overall project aiming to make Linux on "embedded"
> platforms succeed by providing industry-quality tooling for developers

"industry quality"? How does this differ from "commercial quality"?

> and making Linux easier to use in "embedded" products. It's scope
> includes anything that can further that objective.

cool.

> OpenEmbedded - An architecture and build system technology in the form
> of an open source project.

What does "architecture" apply to? What software components are 
compliant with this architecture? Does this represent choices I have to 
make in my product design? Oh wait, reading below "OpenEmbedded Core", 
it sounds like architecture means "how you write a recipe" - correct?

> Bitbake - The tool used by OpenEmbedded to parse the metadata and
> execute tasks

Crystal clear! :)

> OpenEmbedded Core - A core set of metadata which most embedded style
> systems commonly need and conforms to the OpenEmbedded architecture.
> Shared by Yocto and OpenEmbedded and has an aim of achieving the highest
> metadata quality at the expense of some additional process.

"process"? Can you give an example.

> Meta-OpenEmbedded - Metadata for less commonly used software components
> of embedded systems. Has different submission and quality objectives.

I follow, though it begs the question what are the submission and 
quality objectives?

> Poky - A vetted and QA'd combination of bitbake, OpenEmbedded-Core,
> documentation, some reference board support and any needed glue to
> provide support for a defined architecture list. It is supplied in a
> pre-integrated package which has known QA tests and results for its
> releases which provide a stable base people can build upon. Its provided
> and maintained by the Yocto project.

Frankly, this sounds like a great definition for the yocto project!

>
>
> Cheers,
>
> Richard

Thanks again Richard. I think this really is a great start and is 
desperately needed, Ed

>
>
>
>
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab
>