[yocto-ab] [Yocto-Advocacy] Yocto project messaging

[Jeffrey Osier-Mixon]

Thanks for the specific examples, those are very helpful indeed. As we 
rebuild the website to include IoT and other vertical messaging, it does 
make sense to discuss these things and integrate what we find into the 
site.

However, I'm not sure we will have a large immediate impact on the way 
people refer to these things. Most of the references I see to "Yocto" 
rather than "Yocto Project" come from people who are not maintainers or 
otherwise directly involved with the project. We can certainly address 
project documentation and advocacy messaging, but we have no control and 
little influence over most of the presentations out there. Thus, I have 
almost made my peace with the use of "Yocto" by itself.

I think we should reconsider referring to OE as just a build system, as 
it is more than that. An explanation should be easy but also absolutely 
correct, even if not complete.

The reference distro is named "Poky", but what we refer to as Poky is 
actually a reference system - the whole system as a package. If YP is a 
class, Poky is one instance of that class. So it includes:

- OE, which itself provides BitBake and oe-core
- meta-yocto with its baseline BSPs
- several other build tools
- robust documentation

Where OE is DIY, Poky is an off-the-shelf packaged system.

I have debated for years about the best ways to explain these things, 
and thus the messaging.

Re the Edison docs, I have heard about this (from Paul) and I'm still 
looking for the right way to file a bug.


------ Original Message ------
From: "Philip Balister" <philip at balister.org>
To: "yocto-ab at yoctoproject.org" <yocto-ab at yoctoproject.org>
Cc: "yocto-advocacy at yoctoproject.org" <yocto-advocacy at yoctoproject.org>
Sent: 1/29/2015 2:24:18 AM
Subject: [Yocto-Advocacy] Yocto project messaging

>While reading abstracts from FOSDEM and ELC I've noticed that people 
>are
>very confused about what the words Yocto Project, OpenEmbedded, Poky,
>and bitbake mean. Each of these words has a specific meaning:
>
>The Yocto Project is working to make embedded development easier.
>
>OpenEmbedded is a build system used by the Yocto Project.
>
>Poky is the Yocto Project reference distribution.
>
>bitbake is a tool used by OpenEmbedded to create working images and
>sdk's for Poky.
>
>What I read in the wild are seemingly random ways of stringing together
>the words; bitbake, OpenEmbedded, Poky, Project, and Yocto. (sometimes
>mixed up with Tizen, maemo, and other similar but different projects)
>
>From my point of view we need to work from the top down and clean up 
>how
>we talk about the Project in documentation and presentations 
>originating
>from the Yocto Project and provide some guidance on the weg page to
>define these words better. Even at dev day, I've seen slides contradict
>themselves about these words.
>
>What do you guys think? I've included some quotes from FOSDEM, ELC and
>the Edison docs (not picking on Intel specifically, but some of these
>were pointed out to me by a community member) at the end of this email.
>
>Philip
>
>"Building a medical monitoring connected device with Yocto
>Professional OS with yocto"
>
>"We will then show how Yocto and Tizen-meta can be used to create ..."
>
>"The presentation will also provide information about U-Boot, Yocto
>project, the Linux-Sunxi and Linux-Rockchip, Minnowboard communities."
>(This line is pretty good)
>
>"... build images using the Yocto Linux build system."
>
>"Poky has already become one of the most popular build system to make 
>an
>embedded Linux environment. Poky refers to OpenEmbedded originally"
>
>"The set of Yocto recipes necessary ..."
>
>
>
>
>--
>_______________________________________________
>yocto-advocacy mailing list
>yocto-advocacy at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto-advocacy