Yocto Project - User contributions [en]

Release calendar

2026-04-07T12:16:16Z

2021-07-27T16:06:27Z

Paul Barker: Created page with "== Yocto Project related talks at ELC 2021 == * [https://osselc21.sched.com/event/lAUP/bof-the-yocto-project-and-embedded-linux-armin-kuster-montavista-llc-nicolas-dechesne-l..."

== Yocto Project related talks at ELC 2021 ==

* [https://osselc21.sched.com/event/lAUP/bof-the-yocto-project-and-embedded-linux-armin-kuster-montavista-llc-nicolas-dechesne-linaro?iframe=no BoF: The Yocto Project and Embedded Linux - Armin Kuster, MontaVista, LLC & Nicolas Dechesne, Linaro]

* [https://osselc21.sched.com/event/lAMf/securing-a-yocto-based-distribution-the-case-of-allscenariosos-marta-rybczynska?iframe=no Securing a Yocto-based Distribution: The Case of AllScenariosOS - Marta Rybczynska]

* [https://osselc21.sched.com/event/lAMl/yocto-continuous-integration-in-a-kube-joshua-watt-garmin?iframe=no Yocto Continuous Integration in a Kube - Joshua Watt, Garmin]

* [https://osselc21.sched.com/event/lC8w/the-5-key-success-factors-to-deploy-yocto-for-production-grade-embeddediot-devices-adrien-leravat-witekio?iframe=no The 5 Key Success Factors to Deploy Yocto for “Production Grade” Embedded/IoT Devices - Adrien Leravat, Witekio]

* [https://osselc21.sched.com/event/lAMT/binary-artifacts-and-the-ease-of-use-onramp-for-the-yocto-project-bruce-ashfield-xilinx?iframe=no Binary Artifacts and the Ease of Use Onramp for the Yocto Project - Bruce Ashfield, Xilinx]

* [https://osselc21.sched.com/event/lAMW/a-tale-of-three-build-systems-building-a-custom-linux-os-for-beaglev-starlight-with-buildroot-isar-and-yocto-project-tim-orling-intel-corporation?iframe=no A Tale of Three Build Systems: Building a Custom Linux OS for BeagleV Starlight with Buildroot, Isar and Yocto Project - Tim Orling, Intel Corporation]

* [https://osselc21.sched.com/event/lAMi/practical-experience-with-linux-ab-upgrades-leon-anavi-konsulko-group?iframe=no Practical Experience with Linux A/B Upgrades - Leon Anavi, Konsulko Group]

* [https://osselc21.sched.com/event/lAMc/yocto-project-and-android-compare-and-contrast-chris-simmonds-2net?iframe=no Yocto Project and Android – Compare and Contrast - Chris Simmonds, 2net]

Project Users

2020-01-17T11:12:02Z

Paul Barker: /* Projects that use the Yocto Project */

It's hard to know which companies or projects use the Yocto Project since there is no requirement to tell us. This list is here to informally collate the companies, projects and products that use the Yocto Project in some way.

= Companies using the Yocto Project =

Semiconductor Vendors:
* AMD (Silver Member)
* ARM (Platinum Member)
* Intel (Platinum Member)
* NXP (Silver Member)
* Qualcomm
* Renesas (Gold Member)
* STMicroelectronics (Silver Member)
* Texas Instruments (Platinum Member)
* Xilinx (Platinum Member)

OSVs:
* ENEA (Silver Member)
* Linaro (Silver Member)
* Lineo (Silver Member)
* Mentor Graphics (Gold Member)
* Montavista (Silver Member)
* Wind River (Gold Member)

Others:
* Cisco (Platinum Member)
* Comcast (Platinum Member)
* Dell (Silver Member)
* Facebook (Platinum Member)
* Juniper (Gold Member)
* LG (Silver Member)
* Microsoft

= Products that use the Yocto Project =

* Comcast set top boxes
* LG TVs

= Projects that use the Yocto Project =

* [https://www.automotivelinux.org/ Automotive Grade Linux (AGL)]
* Comcast RDK
* OpenBMC
* Windows Subsystem Linux (v1+v2)
* [https://oryx-linux.org/ Oryx Linux]

Janitors

2013-09-19T13:11:33Z

Paul Barker: /* Style and Formatting */

__TOC__

The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

When adding tasks, please be sure to follow this format:
* Task Title
** Difficulty: (Hard|Moderate|Easy)
** Estimate: 0-9 (Day|Hour)s?
** Submitter: IRC Handle
** Task item detail
** Task item detail

As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list.

= Tasks =
== Kernel ==
* Build kernel modules on target
** Difficulty: Moderate
** Estimate: 3 Days
** Submitter: dvhart
** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

== Build ==
* Ability to archive work dir
** Difficulty: Easy
** Estimate: 2 Days
** Submitter: LCS suggestion
** Add the ability to archive the work directory to handle the GPL compliance issue.

== Documentation ==
* Document undocumented variables according to bbvars.py
** Difficulty: Moderate
** Estimate: 1 Hour (per variable)
** Submitter: dvhart
** Start with the variables with the highest count
** First add a doctag to meta/conf/documentation.conf
** Second prepare a patch to documentation/poky-ref-manual/poky-ref-manual.xml
$ scripts/contrib/bbvars.py -d documentation/poky-ref-manual/poky-ref-manual.xml -t meta/conf/documentation.conf -m meta

* Rewrite bbvars.py to use bitbake to find variables
** Difficulty: Hard
** Estimate: 3 Days
** Submitter: dvhart
** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

== Compliance ==
* Fix compliance issues
** Difficulty: Moderate
** Estimate: 3 days
** Submitter: jnfleisc
** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.

== Style and Formatting ==
* Review recipes for compliance with the [[Recipe & Patch Style Guide]]
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly look at reviving the old stylisation script (http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py). It would need bringing up-to-date with the current styleguide and then submitting to oe-core

* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly write a script to use 'bitbake -e' to get the DESCRIPTION value and then check it's length

* Review naming of "files" directories
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** If there is only one recipe in the containing directory (like x_0.bb and x_1.bb) the files directory should be called x, if the patches are only for version 1 of x then the files directory should be called x-1. Also check if the patches in it are still applied or only deadwood.
** Possibly start by running "find -type d -name files" at the root of openembedded-core and meta-openembedded

* Run a spell checker on descriptive variables and comments
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Probably not the most interesting task!

== Misc ==
* Write a friendly IRC bot for the #yocto channel
** Difficultly: Moderate
** Estimate: 1 Week (requires feedback and iterative development)
** Submitter: dvhart
** Possibly named "yocti"
** The bot should be either snarky or obsequious
** The bot should respond to at least the following commands:
*** yocti help (send help privately to user on commands)
*** yocti quiet (no more public output, should still respond to private msgs)
*** yocti speak (start responding again)
*** bug ### (provide a URL to the bug)
*** bzinfo ### (display the bug summary, and possibly whiteboard)
*** git ### (display the git commit subject)
*** bbvar VAR_NAME (display the doctag)
** The bot could also respond to things like:
*** user++ (track kudos points per user per day)
*** user-- (remove kudos points)
*** kudos (display the current kudos scoreboard)
*** .*someday.* (suggest the user add a task to the Janitors list)
*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.

== Janitor entries in Bugzilla ==

{{#bugzilla:
|columns=id,to,estimated,summary,whiteboard,milestone,status
|noresultsmessage=None
|status=NEW,ACCEPTED,IN PROGRESS DESIGN,NEEDINFO
|severity=janitors
}}

Janitors

2013-09-19T13:10:12Z

Paul Barker:

__TOC__

The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

When adding tasks, please be sure to follow this format:
* Task Title
** Difficulty: (Hard|Moderate|Easy)
** Estimate: 0-9 (Day|Hour)s?
** Submitter: IRC Handle
** Task item detail
** Task item detail

As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list.

= Tasks =
== Kernel ==
* Build kernel modules on target
** Difficulty: Moderate
** Estimate: 3 Days
** Submitter: dvhart
** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

== Build ==
* Ability to archive work dir
** Difficulty: Easy
** Estimate: 2 Days
** Submitter: LCS suggestion
** Add the ability to archive the work directory to handle the GPL compliance issue.

== Documentation ==
* Document undocumented variables according to bbvars.py
** Difficulty: Moderate
** Estimate: 1 Hour (per variable)
** Submitter: dvhart
** Start with the variables with the highest count
** First add a doctag to meta/conf/documentation.conf
** Second prepare a patch to documentation/poky-ref-manual/poky-ref-manual.xml
$ scripts/contrib/bbvars.py -d documentation/poky-ref-manual/poky-ref-manual.xml -t meta/conf/documentation.conf -m meta

* Rewrite bbvars.py to use bitbake to find variables
** Difficulty: Hard
** Estimate: 3 Days
** Submitter: dvhart
** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

== Compliance ==
* Fix compliance issues
** Difficulty: Moderate
** Estimate: 3 days
** Submitter: jnfleisc
** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.

== Style and Formatting ==
* Review recipes for compliance with the [[Recipe & Patch Style Guide]]
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly look at reviving the old stylisation script ([[http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py]]). It would need bringing up-to-date with the current styleguide and then submitting to oe-core

* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly write a script to use 'bitbake -e' to get the DESCRIPTION value and then check it's length

* Review naming of "files" directories
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** If there is only one recipe in the containing directory (like x_0.bb and x_1.bb) the files directory should be called x, if the patches are only for version 1 of x then the files directory should be called x-1. Also check if the patches in it are still applied or only deadwood.
** Possibly start by running "find -type d -name files" at the root of openembedded-core and meta-openembedded

* Run a spell checker on descriptive variables and comments
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Probably not the most interesting task!

== Misc ==
* Write a friendly IRC bot for the #yocto channel
** Difficultly: Moderate
** Estimate: 1 Week (requires feedback and iterative development)
** Submitter: dvhart
** Possibly named "yocti"
** The bot should be either snarky or obsequious
** The bot should respond to at least the following commands:
*** yocti help (send help privately to user on commands)
*** yocti quiet (no more public output, should still respond to private msgs)
*** yocti speak (start responding again)
*** bug ### (provide a URL to the bug)
*** bzinfo ### (display the bug summary, and possibly whiteboard)
*** git ### (display the git commit subject)
*** bbvar VAR_NAME (display the doctag)
** The bot could also respond to things like:
*** user++ (track kudos points per user per day)
*** user-- (remove kudos points)
*** kudos (display the current kudos scoreboard)
*** .*someday.* (suggest the user add a task to the Janitors list)
*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.

== Janitor entries in Bugzilla ==

{{#bugzilla:
|columns=id,to,estimated,summary,whiteboard,milestone,status
|noresultsmessage=None
|status=NEW,ACCEPTED,IN PROGRESS DESIGN,NEEDINFO
|severity=janitors
}}