Openembedded.org - User contributions [en]

TSC

2026-02-17T18:09:52Z

Moto-timo: /* 2026 Minutes */

=OE Technical Steering Committee=

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the [[Organization|OpenEmbedded organization]].

Here is the [[TSCCharter | working copy]] of the new TSC charter.

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Tuesday of each month 5PM UTC.

The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.

Note: The Yocto Project also has a TSC. Its responsibilities include repositories hosted on [https://git.yoctoproject.org/ the Yocto Project git server], the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project. For more information on that, go to [https://wiki.yoctoproject.org/wiki/TSC the Yocto Project wiki]

= Members =

In order by name:

* Bruce Ashfield (zeddii) re-elected Sep 2025
* Joshua Watt (JPEW) re-elected Sep 2025
* Richard Purdie (RP) - re-elected Sep 2025
* Tim Orling (moto-timo) - re-elected Sep 2025
* Marta Rybczynska - elected Sep 2025

Each member serves a two-year term.

= Responsibilities =

On a day-to-day basis the TSC is responsible for making
tactical policy decisions, resolving disputes between contributors,
administering access control to the git tree, and generally promoting
good development practice.

= Decision Making =

Decisions are made where necessary by majority vote. Once a decision is made by
the technical steering committee, the decision should be respected as a democratic decision.

= Contacting the TSC =

If you have an issue or would like something discussed at the next TSC meeting, please email tsc@lists.openembedded.org

The item will be added to the TSC topics discussed in the next meeting (or an adhoc meeting will be held is determined to be an urgent issue).

Alternatively, you can contact one of the TSC members listed above and ask them to add it to the list of items to be discussed.

= TSC topics =

This list keeps a running list of topics for the TSC.

* Working Group Definition (https://www.openembedded.org/wiki/Working_Groups)
* (Layer Setup - bitbake-setup)
* Talk about how to acknowledge contributions from community members
* Further discussion on how to increase participation in the project
* OE/YP Training and certification
* Layer Quality
* Overlap between YP initiatives and impact on OE (Compatible v3 - community maintainers)
* nodistro (OE default) vs. poky
* release tags

= TSC mailing list archive =
* Current Groups.io
https://lists.openembedded.org/g/tsc

* old Archive
http://lists.openembedded.org/pipermail/tsc/

= Meeting Minutes =

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

== 2026 Minutes ==

* 2026/02/17
* Attendees : Tim, Richard, Bruce
* Marta is traveling and Joshua had a hard to schedule SPDX meeting conflict
1. Removing old fetchers (ocs, cvs, ...)
2. Dropping the weird year-month.dot-release-yocto-release tags from bitbake
3. Converging oe-core and poky configurations:
* uninative
* CDN enablement
4. Making systemd default in oe-nodistro and poky

* 2026/01/20
* Attendees : Tim, Richard, Joshua, Marta, Bruce
* 1. npm fetcher - next on Richard'a list
* 2. Maintainer recognition - Joshua to discuss with YP Advocacy
* 3. What can we automate?
* Discussion on LTS version updates (blocking an update if we have a known component LTS), CVE products.
AI agents?

== 2025 Minutes ==
* 2025/12/16
* Attendees : Marta, Bruce, Richard, Joshua, Tim
* 1. SPDX backport request - deferred to the Yocto Project TSC (LTS is Yocto
* Project founded and maintained)
* 2. npm fetcher - agreed to Richard add an error when parsing a recipe using the
* npm fetcher that is unsafe to use. Marta will do communication on this subject.

* 2025/11/18
* Attendees : Marta, Tim, Richard, Joshua
* Welcome Marta and questions on how it works
* We communicate minutes of OE TSC minutes.
* How do we prepare the agenda? Agenda prepared from topics from the wiki https://www.openembedded.org/wiki/TSC
* What the TSC is for
* Status of 5.3 and bitbake-setup
* bitbake-setup advancing well. A list of features for the release has been posted to the ML
* npm fetcher issue: the fetcher is taking checksum from the remote source instead of validating it. We're missing people with experience on the subject.
* December 1st meeting: explaining to YP members what is the advantage of the OE membership of individual contributors
* Next meeting: December 16th

* 2025/09/30
* Attendees: RP, Jan-Simon, Joshua, Bruce
* Reviewed topics above for new TSC
* bitbake-setup looks ready
* would be good to have a bitbake-setup 1:1 for new users of the tooling for YPDD late in the year
* YP compatible v3 adds checks on INSANE_SKIPS and no_network
* references for further discussion:
* https://git.yoctoproject.org/yocto-metrics/
* https://dashboard.yoctoproject.org/
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/
* https://valkyrie.yocto.io/pub/non-release/patchmetrics-meta-oe/
* https://autobuilder.yoctoproject.org/valkyrie/#/builders/103

* 2025/01/20
* discussed meta-java and clang
* Autobuilder intermittent issues
* Toolchain
* hardcoded dependency on virtual/<target-prefix>-gcc
* problems integrating meta-clang into core properly (not just copying what is in meta-clang)
* RP has a change that tries a better integration on the list
* discussion wrt integrating above into bitbake proper (instead of anonymous python as on the list)
* bitbake-devel discussion on language specific fetchers
* TSC thinks explicit definition (e.g. .inc file model) is the way to go
* The current patches should be evolved in that direction

== 2024 Minutes ==
* 2024/12/16
* Request for OE Workshop talks https://pretalx.com/openembedded-workshop-2025/
* Josh will send a SPDX talk
* Content/ Interaction w/ audience
* Bruce reworking on container support in meta-virt.
* The CFP closes Dec 21, 2024.
* Alex Kanavin's setup layers/build setup
* Bitbake fragment support merged
* Needs review
* Autobuilder intermittent issues
* New autobuilder performing nicely
* 2-3 issues causing trouble
* CDN
* cve-db
* ...
* Roadmap
* work required for meta-clang inclusion into core
* more work required on integration
* toolchain abstraction needed

* 2024/10/21
* Kanavin's setup layers/build setup
* POC / set of patches, bitbake-setup-layers and bitbake-fragments
* reviews by TSC members requested
* SPDX3
* done, discussed sstate issue
* AutoBuilder
* intermittent issues causing a lot of debug work
* discussing mips, ppc
* Topic for next meeting: Roadmap

* 2024/08/19
Attendees: Bruce, Jan-Simon, Josh, Tim

Topics:
* No topics. Meeting adjourned

Next call September 16th. Might be impacted by EOSS/ELCE/LPC in Vienna.

* 2024/07/15
Attendees: Steve G., Bruce, Tim, Josh, Richard

Topics:
* FIT image patch series
** Some of the easier bits were merged
** Remaining bits are now V2 on mailing list, needs review
* CVE standalone
** Needs review by more experienced developers
* Kanavin's setup layers/build setup
** Needs to be a priority for review
* SPDX3 in time for 5.1M2, may be impacted by JPEW vacation
* AutoBuilder storage and build sizes
** LLVM build size
*** 240GB total, 40GB just for target LLVM package
*** -g1 drops to 4GB, without debug symbols ~700MB
*** General consensus is either option is ok, end user will make decision of when debug symbols are needed
*** Would be nice to have someone work on build-perf analysis as we roll out the new AB cluster
** Next biggest offender is Rust
*** Rust reproducibility remains an issue for 'rustdoc' which continues to block upgrades
* QA Warnings as Errors
** Moving towards YP Compatible requirement for higher quality layers
** TMPDIR/build-path is needed for reproducible builds, but impacts go and rust recipes in meta-virtualization and meta-python
** General consensus is this is moving in the correct direction; layers which have issues in AB will be identified as "help-wanted" recipes.
* meta-java
** There is no CI, but adding to AB (even as a manual job) makes no sense with the current poor state of things
** Will not get much attention until someone either fixes the active branches (kirkstone, scarthgap, master) or funds a dedicated effort to fix it
** At least on Ubuntu 22.04 and Debian 12 hosts, none of those branches are currently buildable, since low level dependencies such as icedtea7-native fail to compile.
* Any outstanding things that should be added to 5.1?
** Consensus is nothing on the radar that is not already in progress

Next call August 19th.

* 2024/6/17
Attendees: Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
** WIP, low prio
* YP and OE
* SPDX3 in time for 5.1M2, no mix-in-layer due to changes in bitbake required
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

Next call jul 15th.

* 2024/3/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
* YP and OE
** Need page for YP/OE in OE and YP wiki
** Weekly Status in wiki: https://wiki.yoctoproject.org/wiki/Weekly_Status
** https://wiki.yoctoproject.org/wiki/TipsAndTricks
* Status of YP LTS 5.0 'scarthgap': on track, advocate maintainers to create the branch now as well
* Post 5.0 release, ideas for STF and how to run
* SPDX3 in time for 5.1M1 , mix-in layer ?
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

== 2023 Minutes ==
* 2023/12/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon
* Making conditional expressions for inherit deferred ?
** issue with perf recipe, different behavior based on conditional inherit
** https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/perf/perf.bb#n57
** this is in-line with https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#inherit-directive
** but it has bad side-effects
* Any specific topic areas we'd like to see developed in future?
** setup tool work open
** https://www.openembedded.org/wiki/Funding_Projects
* Are we trending well to the LTS in April?
** intermittent bugs in AB causing trouble in release process and patch merging
** RP worried ^AB &
*** structural:
**** rust reproducability/ptest
**** qemu
* Working Groups Wiki page
** https://www.openembedded.org/wiki/Working_Groups
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them

* 2023/11/20
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

* Welcomed two new members to the TSC
* Discussed TSC work
** Layerindex, next step to check for LAYERSERIES_COMPAT
*** setup call and review layers that do not have that flag set at all
** new contributors needed, need more maintainers (oe-core, bitbake, meta-*)
*** contact universities with embedded class ?
** patch review process using patchwork, submission model
** rust support , reproducibility issues, tests,
*** Can we phrase the problem so that the jester can send out on social ?
** review other build systems (buildroot, nix, fedora)
** point out strengths
* Topics for OEVDM ( https://www.openembedded.org/wiki/OEDvM_2023.12 )
** LTS in Apr '24
** rust support in OE
** new contributors
* AIs:
** LWN article - Bruce .
** Layerindex call/review - Tim & Jan-Simon
** Topic for next meeting: Syntax change for conditional inheritance

Next meeting is December 18th.

== 2021 Minutes ==
* [https://lists.openembedded.org/g/tsc/message/519 18 January 2021]
* [https://lists.openembedded.org/g/tsc/message/518 15 February 2021]
* [https://lists.openembedded.org/g/tsc/message/555 16 March 2021]
* [https://lists.openembedded.org/g/tsc/message/530 19 April 2021]
* [https://lists.openembedded.org/g/tsc/message/557 17 May 2021]
* [https://lists.openembedded.org/g/tsc/message/544 21 June 2021]
* [https://lists.openembedded.org/g/tsc/message/545 19 July 2021]
* [https://lists.openembedded.org/g/tsc/message/554 16 August 2021]
* [https://lists.openembedded.org/g/tsc/message/553 20 September 2021]
* [https://lists.openembedded.org/g/tsc/message/552 18 October 2021]

== 2020 Minutes ==
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188966 20 January 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72189000 17 March 2020]
* [https://lists.openembedded.org/g/tsc/message/487 20 April 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/74313532 19 May 2020]
* [https://lists.openembedded.org/g/tsc/message/502 20 July 2020]
* [https://lists.openembedded.org/g/tsc/message/508 17 August 2020]
* [https://lists.openembedded.org/g/tsc/message/513 19 October 2020]
* [https://lists.openembedded.org/g/tsc/message/512 16 November 2020]

== 2019 Minutes ==

* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188896 21 October 2019]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188949 16 December 2019]

== 2013 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2013-February/000362.html 29 January 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000363.html 12 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000365.html 26 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000366.html 19 March 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-April/000367.html 8 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/000368.html 23 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/00037.html 7 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000372.html 21 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000373.html 4 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000381.html 18 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-August/000393.html 2 July 2013]
* 16 July 2013
* 30 July 2013 (public meeting)
* 13 August 2013 (cancelled)
* 27 August 2013

== 2012 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-January/000331.html 17-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-February/000332.html 30-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000334.html 15-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000335.html 28-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000336.html 13-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000337.html 27-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000340.html 10-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000342.html 24-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000341.html 08-May-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000343.html 22-May-2012]
* 5-Jun-2012 (no meeting)
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000344.html 19-Jun-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000346.html 3-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000347.html 17-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000348.html 31-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000353.html 14-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000354.html 28-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000355.html 11-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-November/000358.html 23-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-December/000359.html 6-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000360.html 20-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000361.html 4-Dec-2012]

== 2011 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/030355.html 21-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000113.html 28-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000192.html 10-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000193.html 17-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000245.html 12-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000246.html 19-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000249.html 26-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000250.html 02-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000251.html 09-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000258.html 16-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000266.html 23-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000270.html 30-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000272.html 14-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000283.html 21-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000285.html 04-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000298.html 11-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000301.html 01-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000297.html 16-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000299.html 29-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000302.html 06-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000303.html 20-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000304.html 03-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000322.html 17-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000323.html 22-Nov-2011]
* [http://lists.openembedded.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]

== 2010 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-May/020047.html May 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-March/017876.html March 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-February/017094.html February 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-January/015931.html January 2010]

[[Category:Policy]]

OEDEM2025

2025-08-19T15:42:38Z

Moto-timo: /* Agenda */

==Sponsors==

Thanks to our sponsors for helping out with the food for the meeting.

Morning coffee and snacks - [https://redwiretechnologies.us/ Redwire Technologies]

Lunch - [https://www.konsulko.com/ Konsulko]

Afternoon snacks and coffee - [https://pengutronix.de/en/index.html Pengutronix]

==Location and time==

The venue is [https://hotelarena.nl/en/ Hotel Arena] at

Gravesandestraat 55
1092 AA Amsterdam
The Netherlands

The meeting starts at 1000 on August 24, 2025 and runs until we are done, or until 1800 when we have to leave.

==Registration==

Registration is handled at https://pretix.eu/OpenEmbedded/oedem25/

Currently the ticket shop shows the room as full. You can join the waiting list if you are interested and we will try and get people to free up tickets if they can not make it.

==Agenda==

* config file handling on R/O systems, hermetic /usr, https://uapi-group.org/specifications/specs/configuration_files_specification/ (Jan Lübbe)
* handling of static users across distros, https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html (Jan Lübbe)
* boot phase variable naming (Jon Mason)
* What comes after Sato (Ross Burton)
* Megan leads a game to find out how we feel about various parts of the ecosystem, with discussion (Megan)
* Future developer meetings. What do people want, what does the project need, how do we make these happen? (Philip)
* Email is becoming less reliable. Emails from pretix are going to spam, making it hard to organize this meeting. Patches end up tagged as spam by groups.io. Moving forward, what steps can we take to improve communication. Add tools you think might be useful below.(Philip)
** https://community.tmpdir.org/ (Discourse)
* meta-security future plans: user's feedback (Marta & Scott)
* Addressing CRA requirements (secure by default) (Marta)
* bitbake-setup: How do we make progress? What will encourage users to give it a try? (Tim)

==Dinner==

Add your name here if you are interested in dinner after the meeting. We will need someone to find a venue and make a reservation.

# Jon Mason
# Koen Kooi
# Jose Quaresma
# Peter Kjellerstedt
# Jan Lübbe
# Michael Olbrich
# Marta Rybczynska
# Michael Opdenacker
# Joshua Watt
# Chuck Wolber
# Karey Wolber
# Scott Murray
# Vyacheslav Yurkov (Slava)
# Iben Ahlström
# Piotr Buliński
# Philip Balister
# Alexander Sverdlin
# Alessandro Zini
# Stefan Gloor
# Adrian Freihofer
# Nynke Zandstra
# Tim Orling

===Recommended Restaurants===
* [https://www.shivarestaurant.nl/ Shiva] (Indian Food)

===Recommended bars/pubs===
* https://wynand-fockink.nl/

==Minutes==

OEDEM2025

2025-08-19T15:40:45Z

Moto-timo: /* Dinner */

==Sponsors==

Thanks to our sponsors for helping out with the food for the meeting.

Morning coffee and snacks - [https://redwiretechnologies.us/ Redwire Technologies]

Lunch - [https://www.konsulko.com/ Konsulko]

Afternoon snacks and coffee - [https://pengutronix.de/en/index.html Pengutronix]

==Location and time==

The venue is [https://hotelarena.nl/en/ Hotel Arena] at

Gravesandestraat 55
1092 AA Amsterdam
The Netherlands

The meeting starts at 1000 on August 24, 2025 and runs until we are done, or until 1800 when we have to leave.

==Registration==

Registration is handled at https://pretix.eu/OpenEmbedded/oedem25/

Currently the ticket shop shows the room as full. You can join the waiting list if you are interested and we will try and get people to free up tickets if they can not make it.

==Agenda==

* config file handling on R/O systems, hermetic /usr, https://uapi-group.org/specifications/specs/configuration_files_specification/ (Jan Lübbe)
* handling of static users across distros, https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html (Jan Lübbe)
* boot phase variable naming (Jon Mason)
* What comes after Sato (Ross Burton)
* Megan leads a game to find out how we feel about various parts of the ecosystem, with discussion (Megan)
* Future developer meetings. What do people want, what does the project need, how do we make these happen? (Philip)
* Email is becoming less reliable. Emails from pretix are going to spam, making it hard to organize this meeting. Patches end up tagged as spam by groups.io. Moving forward, what steps can we take to improve communication. Add tools you think might be useful below.(Philip)
** https://community.tmpdir.org/ (Discourse)
* meta-security future plans: user's feedback (Marta & Scott)
* Addressing CRA requirements (secure by default) (Marta)

==Dinner==

Add your name here if you are interested in dinner after the meeting. We will need someone to find a venue and make a reservation.

# Jon Mason
# Koen Kooi
# Jose Quaresma
# Peter Kjellerstedt
# Jan Lübbe
# Michael Olbrich
# Marta Rybczynska
# Michael Opdenacker
# Joshua Watt
# Chuck Wolber
# Karey Wolber
# Scott Murray
# Vyacheslav Yurkov (Slava)
# Iben Ahlström
# Piotr Buliński
# Philip Balister
# Alexander Sverdlin
# Alessandro Zini
# Stefan Gloor
# Adrian Freihofer
# Nynke Zandstra
# Tim Orling

===Recommended Restaurants===
* [https://www.shivarestaurant.nl/ Shiva] (Indian Food)

===Recommended bars/pubs===
* https://wynand-fockink.nl/

==Minutes==

TSC

2024-08-19T16:17:11Z

Moto-timo: /* 2024 Minutes */

=OE Technical Steering Committee=

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the [[Organization|OpenEmbedded organization]].

Here is the [[TSCCharter | working copy]] of the new TSC charter.

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.

Note: The Yocto Project also has a TSC. Its responsibilities include repositories hosted on [[https://git.yoctoproject.org/|the Yocto Project git server]], the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project. For more information on that, go to [[https://wiki.yoctoproject.org/wiki/TSC|the Yocto Project wiki]]

= Members =

In order by name:

* Bruce Ashfield (zeddii) re-elected Sep 2023
* Joshua Watt (JPEW) re-elected Sep 2023
* Richard Purdie (RP) - re-elected Sep 2023
* Tim Orling (moto-timo) - elected Sep 2023
* Jan-Simon Möller (dl9pf) - elected Sep 2023

Each member serves a two-year term.

= Responsibilities =

On a day-to-day basis the TSC is responsible for making
tactical policy decisions, resolving disputes between contributors,
administering access control to the git tree, and generally promoting
good development practice.

= Decision Making =

Decisions are made where necessary by majority vote. Once a decision is made by
the technical steering committee, the decision should be respected as a democratic decision.

= Contacting the TSC =

If you have an issue or would like something discussed at the next TSC meeting, please email tsc@lists.openembedded.org

The item will be added to the TSC topics discussed in the next meeting (or an adhoc meeting will be held is determined to be an urgent issue).

Alternatively, you can contact one of the TSC members listed above and ask them to add it to the list of items to be discussed.

= TSC topics =

This list keeps a running list of topics for the TSC.

* Working Group Definition (https://www.openembedded.org/wiki/Working_Groups)
* Layer Setup
* Dublin Meetup
* Talk about how to acknowledge contributions from community members
* Further discussion on how to increase participation in the project
* OE/YP Training and certification
* Layer Quality

= TSC mailing list archive =
* Current Groups.io
https://lists.openembedded.org/g/tsc

* old Archive
http://lists.openembedded.org/pipermail/tsc/

= Meeting Minutes =

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

== 2024 Minutes ==
* 2024/08/19
Attendees: Bruce, Jan-Simon, Josh, Tim

Topics:
* No topics. Meeting adjourned

Next call September 16th. Might be impacted by EOSS/ELCE/LPC in Vienna.

* 2024/07/15
Attendees: Steve G., Bruce, Tim, Josh, Richard

Topics:
* FIT image patch series
** Some of the easier bits were merged
** Remaining bits are now V2 on mailing list, needs review
* CVE standalone
** Needs review by more experienced developers
* Kanavin's setup layers/build setup
** Needs to be a priority for review
* SPDX3 in time for 5.1M2, may be impacted by JPEW vacation
* AutoBuilder storage and build sizes
** LLVM build size
*** 240GB total, 40GB just for target LLVM package
*** -g1 drops to 4GB, without debug symbols ~700MB
*** General consensus is either option is ok, end user will make decision of when debug symbols are needed
*** Would be nice to have someone work on build-perf analysis as we roll out the new AB cluster
** Next biggest offender is Rust
*** Rust reproducibility remains an issue for 'rustdoc' which continues to block upgrades
* QA Warnings as Errors
** Moving towards YP Compatible requirement for higher quality layers
** TMPDIR/build-path is needed for reproducible builds, but impacts go and rust recipes in meta-virtualization and meta-python
** General consensus is this is moving in the correct direction; layers which have issues in AB will be identified as "help-wanted" recipes.
* meta-java
** There is no CI, but adding to AB (even as a manual job) makes no sense with the current poor state of things
** Will not get much attention until someone either fixes the active branches (kirkstone, scarthgap, master) or funds a dedicated effort to fix it
** At least on Ubuntu 22.04 and Debian 12 hosts, none of those branches are currently buildable, since low level dependencies such as icedtea7-native fail to compile.
* Any outstanding things that should be added to 5.1?
** Consensus is nothing on the radar that is not already in progress

Next call August 19th.

* 2024/6/17
Attendees: Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
** WIP, low prio
* YP and OE
* SPDX3 in time for 5.1M2, no mix-in-layer due to changes in bitbake required
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

Next call jul 15th.

* 2024/3/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
* YP and OE
** Need page for YP/OE in OE and YP wiki
** Weekly Status in wiki: https://wiki.yoctoproject.org/wiki/Weekly_Status
** https://wiki.yoctoproject.org/wiki/TipsAndTricks
* Status of YP LTS 5.0 'scarthgap': on track, advocate maintainers to create the branch now as well
* Post 5.0 release, ideas for STF and how to run
* SPDX3 in time for 5.1M1 , mix-in layer ?
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

== 2023 Minutes ==
* 2023/12/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon
* Making conditional expressions for inherit deferred ?
** issue with perf recipe, different behavior based on conditional inherit
** https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/perf/perf.bb#n57
** this is in-line with https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#inherit-directive
** but it has bad side-effects
* Any specific topic areas we'd like to see developed in future?
** setup tool work open
** https://www.openembedded.org/wiki/Funding_Projects
* Are we trending well to the LTS in April?
** intermittent bugs in AB causing trouble in release process and patch merging
** RP worried ^AB &
*** structural:
**** rust reproducability/ptest
**** qemu
* Working Groups Wiki page
** https://www.openembedded.org/wiki/Working_Groups
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them

* 2023/11/20
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

* Welcomed two new members to the TSC
* Discussed TSC work
** Layerindex, next step to check for LAYERSERIES_COMPAT
*** setup call and review layers that do not have that flag set at all
** new contributors needed, need more maintainers (oe-core, bitbake, meta-*)
*** contact universities with embedded class ?
** patch review process using patchwork, submission model
** rust support , reproducibility issues, tests,
*** Can we phrase the problem so that the jester can send out on social ?
** review other build systems (buildroot, nix, fedora)
** point out strengths
* Topics for OEVDM ( https://www.openembedded.org/wiki/OEDvM_2023.12 )
** LTS in Apr '24
** rust support in OE
** new contributors
* AIs:
** LWN article - Bruce .
** Layerindex call/review - Tim & Jan-Simon
** Topic for next meeting: Syntax change for conditional inheritance

Next meeting is December 18th.

== 2021 Minutes ==
* [https://lists.openembedded.org/g/tsc/message/519 18 January 2021]
* [https://lists.openembedded.org/g/tsc/message/518 15 February 2021]
* [https://lists.openembedded.org/g/tsc/message/555 16 March 2021]
* [https://lists.openembedded.org/g/tsc/message/530 19 April 2021]
* [https://lists.openembedded.org/g/tsc/message/557 17 May 2021]
* [https://lists.openembedded.org/g/tsc/message/544 21 June 2021]
* [https://lists.openembedded.org/g/tsc/message/545 19 July 2021]
* [https://lists.openembedded.org/g/tsc/message/554 16 August 2021]
* [https://lists.openembedded.org/g/tsc/message/553 20 September 2021]
* [https://lists.openembedded.org/g/tsc/message/552 18 October 2021]

== 2020 Minutes ==
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188966 20 January 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72189000 17 March 2020]
* [https://lists.openembedded.org/g/tsc/message/487 20 April 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/74313532 19 May 2020]
* [https://lists.openembedded.org/g/tsc/message/502 20 July 2020]
* [https://lists.openembedded.org/g/tsc/message/508 17 August 2020]
* [https://lists.openembedded.org/g/tsc/message/513 19 October 2020]
* [https://lists.openembedded.org/g/tsc/message/512 16 November 2020]

== 2019 Minutes ==

* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188896 21 October 2019]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188949 16 December 2019]

== 2013 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2013-February/000362.html 29 January 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000363.html 12 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000365.html 26 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000366.html 19 March 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-April/000367.html 8 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/000368.html 23 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/00037.html 7 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000372.html 21 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000373.html 4 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000381.html 18 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-August/000393.html 2 July 2013]
* 16 July 2013
* 30 July 2013 (public meeting)
* 13 August 2013 (cancelled)
* 27 August 2013

== 2012 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-January/000331.html 17-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-February/000332.html 30-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000334.html 15-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000335.html 28-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000336.html 13-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000337.html 27-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000340.html 10-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000342.html 24-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000341.html 08-May-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000343.html 22-May-2012]
* 5-Jun-2012 (no meeting)
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000344.html 19-Jun-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000346.html 3-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000347.html 17-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000348.html 31-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000353.html 14-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000354.html 28-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000355.html 11-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-November/000358.html 23-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-December/000359.html 6-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000360.html 20-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000361.html 4-Dec-2012]

== 2011 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/030355.html 21-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000113.html 28-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000192.html 10-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000193.html 17-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000245.html 12-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000246.html 19-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000249.html 26-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000250.html 02-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000251.html 09-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000258.html 16-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000266.html 23-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000270.html 30-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000272.html 14-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000283.html 21-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000285.html 04-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000298.html 11-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000301.html 01-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000297.html 16-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000299.html 29-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000302.html 06-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000303.html 20-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000304.html 03-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000322.html 17-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000323.html 22-Nov-2011]
* [http://lists.openembedded.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]

== 2010 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-May/020047.html May 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-March/017876.html March 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-February/017094.html February 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-January/015931.html January 2010]

[[Category:Policy]]

TSC

2024-08-19T16:16:46Z

Moto-timo: /* 2024 Minutes */

=OE Technical Steering Committee=

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the [[Organization|OpenEmbedded organization]].

Here is the [[TSCCharter | working copy]] of the new TSC charter.

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.

Note: The Yocto Project also has a TSC. Its responsibilities include repositories hosted on [[https://git.yoctoproject.org/|the Yocto Project git server]], the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project. For more information on that, go to [[https://wiki.yoctoproject.org/wiki/TSC|the Yocto Project wiki]]

= Members =

In order by name:

* Bruce Ashfield (zeddii) re-elected Sep 2023
* Joshua Watt (JPEW) re-elected Sep 2023
* Richard Purdie (RP) - re-elected Sep 2023
* Tim Orling (moto-timo) - elected Sep 2023
* Jan-Simon Möller (dl9pf) - elected Sep 2023

Each member serves a two-year term.

= Responsibilities =

On a day-to-day basis the TSC is responsible for making
tactical policy decisions, resolving disputes between contributors,
administering access control to the git tree, and generally promoting
good development practice.

= Decision Making =

Decisions are made where necessary by majority vote. Once a decision is made by
the technical steering committee, the decision should be respected as a democratic decision.

= Contacting the TSC =

If you have an issue or would like something discussed at the next TSC meeting, please email tsc@lists.openembedded.org

The item will be added to the TSC topics discussed in the next meeting (or an adhoc meeting will be held is determined to be an urgent issue).

Alternatively, you can contact one of the TSC members listed above and ask them to add it to the list of items to be discussed.

= TSC topics =

This list keeps a running list of topics for the TSC.

* Working Group Definition (https://www.openembedded.org/wiki/Working_Groups)
* Layer Setup
* Dublin Meetup
* Talk about how to acknowledge contributions from community members
* Further discussion on how to increase participation in the project
* OE/YP Training and certification
* Layer Quality

= TSC mailing list archive =
* Current Groups.io
https://lists.openembedded.org/g/tsc

* old Archive
http://lists.openembedded.org/pipermail/tsc/

= Meeting Minutes =

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

== 2024 Minutes ==
* 2024/08/19
Attendees: Bruce, Jan-Simon, Josh, Tim

Topics:
* No topics. Meeting adjourned

Next call September 16th. Might be impacted by EOSS/ELCE/LPC in Vienna.

* 2024/07/15
Attendees: Steve G., Bruce, Tim, Josh, Richard

Topics:
* FIT image patch series
** Some of the easier bits were merged
** Remaining bits are now V2 on mailing list, needs review
* CVE standalone
** Needs review by more experienced developers
* Kanavin's setup layers/build setup
** Needs to be a priority for review
* SPDX3 in time for 5.1M2, may be impacted by JPEW vacation
* AutoBuilder storage and build sizes
** LLVM build size
*** 240GB total, 40GB just for target LLVM package
*** -g1 drops to 4GB, without debug symbols ~700MB
*** General consensus is either option is ok, end user will make decision of when debug symbols are needed
*** Would be nice to have someone work on build-perf analysis as we roll out the new AB cluster
** Next biggest offender is Rust
*** Rust reproducibility remains an issue for 'rustdoc' which continues to block upgrades
* QA Warnings as Errors
** Moving towards YP Compatible requirement for higher quality layers
** TMPDIR/build-path is needed for reproducible builds, but impacts go and rust recipes in meta-virtualization and meta-python
** General consensus is this is moving in the correct direction; layers which have issues in AB will be identified as "help-wanted" recipes.
* meta-java
** There is no CI, but adding to AB (even as a manual job) makes no sense with the current poor state of things
** Will not get much attention until someone either fixes the active branches (kirkstone, scarthgap, master) or funds a dedicated effort to fix it
** At least on Ubuntu 22.04 and Debian 12 hosts, none of those branches are currently buildable, since low level dependencies such as icedtea7-native fail to compile.
* Any outstanding things that should be added to 5.1?
** Consensus is nothing on the radar that is not already in progress

Next call August 19th.

* 2024/6/17
Attendees: Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
** WIP, low prio
* YP and OE
* SPDX3 in time for 5.1M2, no mix-in-layer due to changes in bitbake required
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

Next call jul 15th.

* 2024/3/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
* YP and OE
** Need page for YP/OE in OE and YP wiki
** Weekly Status in wiki: https://wiki.yoctoproject.org/wiki/Weekly_Status
** https://wiki.yoctoproject.org/wiki/TipsAndTricks
* Status of YP LTS 5.0 'scarthgap': on track, advocate maintainers to create the branch now as well
* Post 5.0 release, ideas for STF and how to run
* SPDX3 in time for 5.1M1 , mix-in layer ?
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

== 2023 Minutes ==
* 2023/12/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon
* Making conditional expressions for inherit deferred ?
** issue with perf recipe, different behavior based on conditional inherit
** https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/perf/perf.bb#n57
** this is in-line with https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#inherit-directive
** but it has bad side-effects
* Any specific topic areas we'd like to see developed in future?
** setup tool work open
** https://www.openembedded.org/wiki/Funding_Projects
* Are we trending well to the LTS in April?
** intermittent bugs in AB causing trouble in release process and patch merging
** RP worried ^AB &
*** structural:
**** rust reproducability/ptest
**** qemu
* Working Groups Wiki page
** https://www.openembedded.org/wiki/Working_Groups
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them

* 2023/11/20
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

* Welcomed two new members to the TSC
* Discussed TSC work
** Layerindex, next step to check for LAYERSERIES_COMPAT
*** setup call and review layers that do not have that flag set at all
** new contributors needed, need more maintainers (oe-core, bitbake, meta-*)
*** contact universities with embedded class ?
** patch review process using patchwork, submission model
** rust support , reproducibility issues, tests,
*** Can we phrase the problem so that the jester can send out on social ?
** review other build systems (buildroot, nix, fedora)
** point out strengths
* Topics for OEVDM ( https://www.openembedded.org/wiki/OEDvM_2023.12 )
** LTS in Apr '24
** rust support in OE
** new contributors
* AIs:
** LWN article - Bruce .
** Layerindex call/review - Tim & Jan-Simon
** Topic for next meeting: Syntax change for conditional inheritance

Next meeting is December 18th.

== 2021 Minutes ==
* [https://lists.openembedded.org/g/tsc/message/519 18 January 2021]
* [https://lists.openembedded.org/g/tsc/message/518 15 February 2021]
* [https://lists.openembedded.org/g/tsc/message/555 16 March 2021]
* [https://lists.openembedded.org/g/tsc/message/530 19 April 2021]
* [https://lists.openembedded.org/g/tsc/message/557 17 May 2021]
* [https://lists.openembedded.org/g/tsc/message/544 21 June 2021]
* [https://lists.openembedded.org/g/tsc/message/545 19 July 2021]
* [https://lists.openembedded.org/g/tsc/message/554 16 August 2021]
* [https://lists.openembedded.org/g/tsc/message/553 20 September 2021]
* [https://lists.openembedded.org/g/tsc/message/552 18 October 2021]

== 2020 Minutes ==
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188966 20 January 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72189000 17 March 2020]
* [https://lists.openembedded.org/g/tsc/message/487 20 April 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/74313532 19 May 2020]
* [https://lists.openembedded.org/g/tsc/message/502 20 July 2020]
* [https://lists.openembedded.org/g/tsc/message/508 17 August 2020]
* [https://lists.openembedded.org/g/tsc/message/513 19 October 2020]
* [https://lists.openembedded.org/g/tsc/message/512 16 November 2020]

== 2019 Minutes ==

* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188896 21 October 2019]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188949 16 December 2019]

== 2013 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2013-February/000362.html 29 January 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000363.html 12 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000365.html 26 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000366.html 19 March 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-April/000367.html 8 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/000368.html 23 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/00037.html 7 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000372.html 21 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000373.html 4 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000381.html 18 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-August/000393.html 2 July 2013]
* 16 July 2013
* 30 July 2013 (public meeting)
* 13 August 2013 (cancelled)
* 27 August 2013

== 2012 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-January/000331.html 17-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-February/000332.html 30-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000334.html 15-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000335.html 28-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000336.html 13-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000337.html 27-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000340.html 10-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000342.html 24-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000341.html 08-May-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000343.html 22-May-2012]
* 5-Jun-2012 (no meeting)
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000344.html 19-Jun-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000346.html 3-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000347.html 17-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000348.html 31-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000353.html 14-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000354.html 28-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000355.html 11-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-November/000358.html 23-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-December/000359.html 6-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000360.html 20-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000361.html 4-Dec-2012]

== 2011 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/030355.html 21-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000113.html 28-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000192.html 10-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000193.html 17-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000245.html 12-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000246.html 19-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000249.html 26-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000250.html 02-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000251.html 09-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000258.html 16-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000266.html 23-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000270.html 30-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000272.html 14-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000283.html 21-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000285.html 04-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000298.html 11-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000301.html 01-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000297.html 16-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000299.html 29-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000302.html 06-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000303.html 20-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000304.html 03-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000322.html 17-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000323.html 22-Nov-2011]
* [http://lists.openembedded.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]

== 2010 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-May/020047.html May 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-March/017876.html March 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-February/017094.html February 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-January/015931.html January 2010]

[[Category:Policy]]

TSC

2024-07-15T17:24:56Z

Moto-timo: /* 2024 Minutes */ 2024-07-15

=OE Technical Steering Committee=

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the [[Organization|OpenEmbedded organization]].

Here is the [[TSCCharter | working copy]] of the new TSC charter.

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.

Note: The Yocto Project also has a TSC. Its responsibilities include repositories hosted on [[https://git.yoctoproject.org/|the Yocto Project git server]], the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project. For more information on that, go to [[https://wiki.yoctoproject.org/wiki/TSC|the Yocto Project wiki]]

= Members =

In order by name:

* Bruce Ashfield (zeddii) re-elected Sep 2023
* Joshua Watt (JPEW) re-elected Sep 2023
* Richard Purdie (RP) - re-elected Sep 2023
* Tim Orling (moto-timo) - elected Sep 2023
* Jan-Simon Möller (dl9pf) - elected Sep 2023

Each member serves a two-year term.

= Responsibilities =

On a day-to-day basis the TSC is responsible for making
tactical policy decisions, resolving disputes between contributors,
administering access control to the git tree, and generally promoting
good development practice.

= Decision Making =

Decisions are made where necessary by majority vote. Once a decision is made by
the technical steering committee, the decision should be respected as a democratic decision.

= Contacting the TSC =

If you have an issue or would like something discussed at the next TSC meeting, please email tsc@lists.openembedded.org

The item will be added to the TSC topics discussed in the next meeting (or an adhoc meeting will be held is determined to be an urgent issue).

Alternatively, you can contact one of the TSC members listed above and ask them to add it to the list of items to be discussed.

= TSC topics =

This list keeps a running list of topics for the TSC.

* Working Group Definition (https://www.openembedded.org/wiki/Working_Groups)
* Layer Setup
* Dublin Meetup
* Talk about how to acknowledge contributions from community members
* Further discussion on how to increase participation in the project
* OE/YP Training and certification
* Layer Quality

= TSC mailing list archive =
* Current Groups.io
https://lists.openembedded.org/g/tsc

* old Archive
http://lists.openembedded.org/pipermail/tsc/

= Meeting Minutes =

Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).

== 2024 Minutes ==
* 2024/07/15
Attendees: Steve G., Bruce, Tim, Josh, Richard

Topics:
* FIT image patch series
** Some of the easier bits were merged
** Remaining bits are now V2 on mailing list, needs review
* CVE standalone
** Needs review by more experienced developers
* Kanavin's setup layers/build setup
** Needs to be a priority for review
* SPDX3 in time for 5.1M2, may be impacted by JPEW vacation
* AutoBuilder storage and build sizes
** LLVM build size
*** 240GB total, 40GB just for target LLVM package
*** -g1 drops to 4GB, without debug symbols ~700MB
*** General consensus is either option is ok, end user will make decision of when debug symbols are needed
*** Would be nice to have someone work on build-perf analysis as we roll out the new AB cluster
** Next biggest offender is Rust
*** Rust reproducibility remains an issue for 'rustdoc' which continues to block upgrades
* QA Warnings as Errors
** Moving towards YP Compatible requirement for higher quality layers
** TMPDIR/build-path is needed for reproducible builds, but impacts go and rust recipes in meta-virtualization and meta-python
** General consensus is this is moving in the correct direction; layers which have issues in AB will be identified as "help-wanted" recipes.
* meta-java
** There is no CI, but adding to AB (even as a manual job) makes no sense with the current poor state of things
** Will not get much attention until someone either fixes the active branches (kirkstone, scarthgap, master) or funds a dedicated effort to fix it
** At least on Ubuntu 22.04 and Debian 12 hosts, none of those branches are currently buildable, since low level dependencies such as icedtea7-native fail to compile.
* Any outstanding things that should be added to 5.1?
** Consensus is nothing on the radar that is not already in progress

Next call August 19th.

* 2024/6/17
Attendees: Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
** WIP, low prio
* YP and OE
* SPDX3 in time for 5.1M2, no mix-in-layer due to changes in bitbake required
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

Next call jul 15th.

* 2024/3/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

Topics:
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them
** Tim started on it. Similar to go-native, download native for bootstrap.
* YP and OE
** Need page for YP/OE in OE and YP wiki
** Weekly Status in wiki: https://wiki.yoctoproject.org/wiki/Weekly_Status
** https://wiki.yoctoproject.org/wiki/TipsAndTricks
* Status of YP LTS 5.0 'scarthgap': on track, advocate maintainers to create the branch now as well
* Post 5.0 release, ideas for STF and how to run
* SPDX3 in time for 5.1M1 , mix-in layer ?
* Tackle bitbake syntax ?= ??= post 5.0 ?
* Rust in kernel build

== 2023 Minutes ==
* 2023/12/18
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon
* Making conditional expressions for inherit deferred ?
** issue with perf recipe, different behavior based on conditional inherit
** https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/perf/perf.bb#n57
** this is in-line with https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#inherit-directive
** but it has bad side-effects
* Any specific topic areas we'd like to see developed in future?
** setup tool work open
** https://www.openembedded.org/wiki/Funding_Projects
* Are we trending well to the LTS in April?
** intermittent bugs in AB causing trouble in release process and patch merging
** RP worried ^AB &
*** structural:
**** rust reproducability/ptest
**** qemu
* Working Groups Wiki page
** https://www.openembedded.org/wiki/Working_Groups
* meta-java
** plan is to use e.g. eclipse binaries for version n-1 and build version n with them

* 2023/11/20
Attendees: Richard, Josh, Tim, Bruce, Jan-Simon

* Welcomed two new members to the TSC
* Discussed TSC work
** Layerindex, next step to check for LAYERSERIES_COMPAT
*** setup call and review layers that do not have that flag set at all
** new contributors needed, need more maintainers (oe-core, bitbake, meta-*)
*** contact universities with embedded class ?
** patch review process using patchwork, submission model
** rust support , reproducibility issues, tests,
*** Can we phrase the problem so that the jester can send out on social ?
** review other build systems (buildroot, nix, fedora)
** point out strengths
* Topics for OEVDM ( https://www.openembedded.org/wiki/OEDvM_2023.12 )
** LTS in Apr '24
** rust support in OE
** new contributors
* AIs:
** LWN article - Bruce .
** Layerindex call/review - Tim & Jan-Simon
** Topic for next meeting: Syntax change for conditional inheritance

Next meeting is December 18th.

== 2021 Minutes ==
* [https://lists.openembedded.org/g/tsc/message/519 18 January 2021]
* [https://lists.openembedded.org/g/tsc/message/518 15 February 2021]
* [https://lists.openembedded.org/g/tsc/message/555 16 March 2021]
* [https://lists.openembedded.org/g/tsc/message/530 19 April 2021]
* [https://lists.openembedded.org/g/tsc/message/557 17 May 2021]
* [https://lists.openembedded.org/g/tsc/message/544 21 June 2021]
* [https://lists.openembedded.org/g/tsc/message/545 19 July 2021]
* [https://lists.openembedded.org/g/tsc/message/554 16 August 2021]
* [https://lists.openembedded.org/g/tsc/message/553 20 September 2021]
* [https://lists.openembedded.org/g/tsc/message/552 18 October 2021]

== 2020 Minutes ==
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188966 20 January 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72189000 17 March 2020]
* [https://lists.openembedded.org/g/tsc/message/487 20 April 2020]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/74313532 19 May 2020]
* [https://lists.openembedded.org/g/tsc/message/502 20 July 2020]
* [https://lists.openembedded.org/g/tsc/message/508 17 August 2020]
* [https://lists.openembedded.org/g/tsc/message/513 19 October 2020]
* [https://lists.openembedded.org/g/tsc/message/512 16 November 2020]

== 2019 Minutes ==

* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188896 21 October 2019]
* [https://lists.openembedded.org/g/tsc/topic/openembedded_tsc_meeting/72188949 16 December 2019]

== 2013 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2013-February/000362.html 29 January 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000363.html 12 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000365.html 26 February 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000366.html 19 March 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-April/000367.html 8 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/000368.html 23 April 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-May/00037.html 7 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000372.html 21 May 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000373.html 4 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000381.html 18 June 2013]
* [http://lists.openembedded.org/pipermail/tsc/2013-August/000393.html 2 July 2013]
* 16 July 2013
* 30 July 2013 (public meeting)
* 13 August 2013 (cancelled)
* 27 August 2013

== 2012 Minutes ==

* [http://lists.openembedded.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-January/000331.html 17-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-February/000332.html 30-Jan-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000334.html 15-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000335.html 28-Feb-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-March/000336.html 13-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000337.html 27-Mar-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-April/000340.html 10-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000342.html 24-Apr-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-May/000341.html 08-May-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000343.html 22-May-2012]
* 5-Jun-2012 (no meeting)
* [http://lists.openembedded.org/pipermail/tsc/2012-June/000344.html 19-Jun-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000346.html 3-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000347.html 17-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000348.html 31-Jul-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-August/000353.html 14-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000354.html 28-Aug-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-September/000355.html 11-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-November/000358.html 23-Oct-2012]
* [http://lists.openembedded.org/pipermail/tsc/2012-December/000359.html 6-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000360.html 20-Nov-2012]
* [http://lists.openembedded.org/pipermail/tsc/2013-January/000361.html 4-Dec-2012]

== 2011 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2011-February/030355.html 21-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000113.html 28-Feb-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000192.html 10-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000193.html 17-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000245.html 12-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000246.html 19-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000249.html 26-May-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000250.html 02-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000251.html 09-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000258.html 16-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-June/000266.html 23-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000270.html 30-Jun-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-July/000272.html 14-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000283.html 21-Jul-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-August/000285.html 04-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000298.html 11-Aug-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000301.html 01-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000297.html 16-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-September/000299.html 29-Sep-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000302.html 06-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-October/000303.html 20-Oct-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000304.html 03-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000322.html 17-Nov-2011]
* [http://lists.openembedded.org/pipermail/tsc/2011-November/000323.html 22-Nov-2011]
* [http://lists.openembedded.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]

== 2010 Minutes ==

* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-May/020047.html May 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-March/017876.html March 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-February/017094.html February 2010]
* [http://lists.openembedded.org/pipermail/openembedded-devel/2010-January/015931.html January 2010]

[[Category:Policy]]

Template:Main page/news

2022-12-10T17:33:10Z

Moto-timo: fix pretalx link

'''Recent News:'''.
* '''''2023-02-06:''''' OpenEmbedded will host a [https://pretalx.com/openembedded-workshop-2023/ Workshop] after [https://fosdem.org/2023/ FOSDEM].
* '''''2022-10-05:''''' [https://www.openembedded.org/wiki/OEDvM_2022.11] OEDvM 2022.11
* '''''2022-10-05:''''' [https://www.yoctoproject.org/yocto-project-summit-2022-11/] Yocto Project Summit 2022.11
* '''''2022-04-28:''''' [https://www.openembedded.org/wiki/OEDVM_2022_05] OEDvM 2022.05
* '''''2022-04-01:''''' [https://www.yoctoproject.org/yocto-project-summit-2022-05/] Yocto Project Summit 2022.05

See [[NewsArchive|News Archive]] for older news.

Template:Main page/news

2022-12-10T17:29:51Z

Moto-timo: Add OE Workshop

'''Recent News:'''.
* '''''2023-02-06:''''' OpenEmbedded will host a [https://pretalx.com/oe-workshop-2023/ Workshop] after [https://fosdem.org/2023/ FOSDEM].
* '''''2022-10-05:''''' [https://www.openembedded.org/wiki/OEDvM_2022.11] OEDvM 2022.11
* '''''2022-10-05:''''' [https://www.yoctoproject.org/yocto-project-summit-2022-11/] Yocto Project Summit 2022.11
* '''''2022-04-28:''''' [https://www.openembedded.org/wiki/OEDVM_2022_05] OEDvM 2022.05
* '''''2022-04-01:''''' [https://www.yoctoproject.org/yocto-project-summit-2022-05/] Yocto Project Summit 2022.05

See [[NewsArchive|News Archive]] for older news.

Membership

2022-12-02T17:14:34Z

Moto-timo:

Development in OpenEmbedded or any of it's sub-projects does not require membership in OpenEmbedded. However, membership does provide some benefits:
* Voting in elections for the OpenEmbedded board
* Voting in elections for the OpenEmbedded Technical Steering Committee
* Voting in elections for the 2 OpenEmbedded seats in the Yocto Project Technical Steering Committee
* Can join the OpenEmbedded mailing list for members

Membership is free

Membership process:
# email [[mailto:board@openembedded.org board@openembedded.org]] with a request to join and a link to [[https://www.linkedin.com linkedin]] or brief CV or something similar
# board will communicate with members to vote on you joining
# board will communicate results to you (2-4 weeks turn around time)

OEDVM 2022 05

2022-05-19T19:58:43Z

Moto-timo: /* Topic Ideas */

==Location and Time==

Held after the [https://pretalx.com/yocto-project-summit-2022-05/ Yocto Project Summit ], The OE Developers Meeting is scheduled for Friday, 20 May 2022 between 12:00 and 20:00 UTC. Exact times for each individual topic are found below in the schedule.

The meeting is held on Zoom https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). We thank [//www.automotivelinux.org/ Automotive Grade Linux] for providing!

==Format==

As always, we will collect topics on the wiki at
https://wiki.openembedded.org/OEDVM_2022_05.

For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.

==Topic Ideas==

These are topics that were suggested for previous OE developer meetings and have not been covered yet. They should be seen as starting ideas on things that can be discussed.

Actual schedule
::{|
! Topic
! Moderator(s)
! Time in UTC (Start is 1200 UTC/0800 EDT)
! Notes
|-
| Introduction
| OE Board
| 1200
|-
| Future of eSDK (inc. bblock/bbunlock commands)
| ?
| 1215
| https://lists.openembedded.org/g/openembedded-architecture/topic/thoughts_on_the_esdk/90990557
|-
| Copyright in OE-Core files
| ?
| 1300
| https://lists.openembedded.org/g/openembedded-architecture/topic/oe_core_copyright_notices/91159593
|-
| layer.conf changes
| ?
| 1330
|-
| Kernel config RFC
| Trevor Woerner
| 1400
|-

| Layer Setup Configuration
| Joshua Watt
| 1430
|-

| Bitbake & OE "Core improvements"
| Joshua Watt
| 1500
|-

| Multiple SBOM formats, both in and out
| Peter Kjellerstedt
| 1530
|-

| Layerindex: quality, tooling, enhancements
| Jan-Simon Möller, Tim Orling
| 1550
|-

| Airing of Grievances
| OpenEmbedded Board
| 1610 (After all other topics covered)
|-

|}

Unassigned ideas for next time
::{|
! Topic
! Moderator(s)
! Estimate of time
! Notes
|-

| Data store operation changes
| ?
| ?
|-

| Syntax removal
| ?
| ?
|-

| Data store internal rewrite
| ?
| ?
|-

| f-string in Python code (and more modern python in general)
| Ross Burton, Tim Orling
| ?
|-

| Merging optional functionality to make it mandatory
| ?
| ?
|-

| Dropping core features
| ?
| ?
|-

| Security (PSiRT)
| ?
| ?
|-

| Layer setup configuration
| ?
| ?
|-

| QA Automation
| ?
| ?
|-

| Code submission process
| ?
| ?
|-

| Software updates
| ?
| ?
|-

| AI/ML
| ?
| ?
|-
|}

Here are some new topic ideas:

::{|
! Topic
! Moderator(s)
! Estimate of time
|-

|}

==Notes==
===Social===
Meet up @ ELC?

==Minutes==

TBD

OEDVM 2022 05

2022-05-19T19:57:50Z

Moto-timo: /* Topic Ideas */

==Location and Time==

Held after the [https://pretalx.com/yocto-project-summit-2022-05/ Yocto Project Summit ], The OE Developers Meeting is scheduled for Friday, 20 May 2022 between 12:00 and 20:00 UTC. Exact times for each individual topic are found below in the schedule.

The meeting is held on Zoom https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). We thank [//www.automotivelinux.org/ Automotive Grade Linux] for providing!

==Format==

As always, we will collect topics on the wiki at
https://wiki.openembedded.org/OEDVM_2022_05.

For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.

==Topic Ideas==

These are topics that were suggested for previous OE developer meetings and have not been covered yet. They should be seen as starting ideas on things that can be discussed.

Actual schedule
::{|
! Topic
! Moderator(s)
! Time in UTC (Start is 1200 UTC/0800 EDT)
! Notes
|-
| Introduction
| OE Board
| 1200
|-
| Future of eSDK (inc. bblock/bbunlock commands)
| ?
| 1215
| https://lists.openembedded.org/g/openembedded-architecture/topic/thoughts_on_the_esdk/90990557
|-
| Copyright in OE-Core files
| ?
| 1300
| https://lists.openembedded.org/g/openembedded-architecture/topic/oe_core_copyright_notices/91159593
|-
| layer.conf changes
| ?
| 1330
|-
| Kernel config RFC
| Trevor Woerner
| 1400
|-

| Layer Setup Configuration
| Joshua Watt
| 1430
|-

| Bitbake & OE "Core improvements"
| Joshua Watt
| 1500
|-

| Multiple SBOM formats, both in and out
| Peter Kjellerstedt
| 1530
|-

| Layerindex: quality, tooling, enhancements
| Jan-Simon Möller, Tim Orling
| 1550
|-

| Airing of Grievances
| OpenEmbedded Board
| 1610 (After all other topics covered)
|-

|}

Unassigned ideas for next time
::{|
! Topic
! Moderator(s)
! Estimate of time
! Notes

| Data store operation changes
| ?
| ?
|-

| Syntax removal
| ?
| ?
|-

| Data store internal rewrite
| ?
| ?
|-

| f-string in Python code (and more modern python in general)
| Ross Burton, Tim Orling
| ?
|-

| Merging optional functionality to make it mandatory
| ?
| ?
|-

| Dropping core features
| ?
| ?
|-

| Security (PSiRT)
| ?
| ?
|-

| Layer setup configuration
| ?
| ?
|-

| QA Automation
| ?
| ?
|-

| Code submission process
| ?
| ?
|-

| Software updates
| ?
| ?
|-

| AI/ML
| ?
| ?
|-
|}

Here are some new topic ideas:

::{|
! Topic
! Moderator(s)
! Estimate of time
|-

|}

==Notes==
===Social===
Meet up @ ELC?

==Minutes==

TBD

OEDVM 2022 05

2022-05-19T18:11:40Z

Moto-timo: /* Topic Ideas */

==Location and Time==

Held after the [https://pretalx.com/yocto-project-summit-2022-05/ Yocto Project Summit ], The OE Developers Meeting is scheduled for Friday, 20 May 2022 between 12:00 and 20:00 UTC. Exact times for each individual topic are found below in the schedule.

The meeting is held on Zoom https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). We thank [//www.automotivelinux.org/ Automotive Grade Linux] for providing!

==Format==

As always, we will collect topics on the wiki at
https://wiki.openembedded.org/OEDVM_2022_05.

For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.

==Topic Ideas==

These are topics that were suggested for previous OE developer meetings and have not been covered yet. They should be seen as starting ideas on things that can be discussed.

(In no particular order)
::{|
! Topic
! Moderator(s)
! Estimate of time
! Notes
|-
| Introduction
| OE Board
| ?
|-
| Future of eSDK (inc. bblock/bbunlock commands)
| ?
| ?
| https://lists.openembedded.org/g/openembedded-architecture/topic/thoughts_on_the_esdk/90990557
|-
| Copyright in OE-Core files
| ?
| ?
| https://lists.openembedded.org/g/openembedded-architecture/topic/oe_core_copyright_notices/91159593
|-
| layer.conf changes
| ?
| ?
|-

| Data store operation changes
| ?
| ?
|-

| Syntax removal
| ?
| ?
|-

| Data store internal rewrite
| ?
| ?
|-

| f-string in Python code (and more modern python in general)
| ?
| ?
|-

| Merging optional functionality to make it mandatory
| ?
| ?
|-

| Dropping core features
| ?
| ?
|-

| Security (PSiRT)
| ?
| ?
|-

| Layer setup configuration
| ?
| ?
|-

| QA Automation
| ?
| ?
|-

| Code submission process
| ?
| ?
|-

| Software updates
| ?
| ?
|-

| AI/ML
| ?
| ?
|-
|}

Here are some new topic ideas:

::{|
! Topic
! Moderator(s)
! Estimate of time
|-

| Kernel config RFC
| Trevor Woerner
| 30
|-

| Layer Setup Configuration
| Joshua Watt
| 30
|-

| Bitbake & OE "Core improvements"
| Joshua Watt
| 30
|-

| Multiple SBOM formats, both in and out
| Peter Kjellerstedt
| 20
|-

| Layerindex: quality, tooling, enhancements
| Jan-Simon Möller, Tim Orling
| 20
|-

| Airing of Grievances
| OpenEmbedded Board
| 30+ (After all other topics covered)
|-

|}

==Notes==
===Social===
Meet up @ ELC?

==Minutes==

TBD

Deprecate distutils

2022-01-14T03:21:47Z

Moto-timo: /* List of recipes inheriting distutils* */

== Deprecating distutils*.bbclass ==

In Python 3.10 `distutils` has been deprecated and is to be removed in Python 3.12. In preparation for this, the `distutils*` classes have been deprecated and nearly all usage in oe-core has been removed.

We still have a few recipes under the meta-openembedded umbrella that inherit one of the `distutils` classes (the lowest common denominator is `distutils-common-base`)

To get a list, you can run the following command:

<blockquote>$ bitbake-layers show-recipes -i distutils-common-base -r</blockquote>

This is a call to arms, please help by picking one of the following.

=== List of recipes inheriting distutils* ===
{| class="wikitable"
!Recipe
!Layer
!Version
!Latest
!Upstream
!Assignee
!Status
|-
|[https://layers.openembedded.org/layerindex/recipe/58445/ cxxtest]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v4.4
|v
|[http://cxxtest.com/ cxxtest.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/1203/ gammu]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v1.32.0
|v1.42.0
|[https://wammu.eu/download/gammu/1.42.0/ wammu.eu]
|Moto-timo
|In progress review
|-
|[https://layers.openembedded.org/layerindex/recipe/853/ iotop]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.6
|v
|[http://guichaz.free.fr/iotop/ guichaz.free.fr]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/33169/ lirc]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.10.1
|v
|[http://www.lirc.org/ lirc.org]
|Oleksandr Kravchuk
|In progress review
|-
|[https://layers.openembedded.org/layerindex/recipe/114060/ python3-dbussy]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.3
|v
|[https://github.com/ldo/dbussy github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/66996/ python3-greenlet]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.1.2
|v
|[https://greenlet.readthedocs.io/en/latest/ greenlet.readthedocs.io]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/163902/ python3-hexdump]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.3
|v
|[https://pypi.org/project/hexdump/ pypi.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/75243/ python3-pycrypto]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v2.6.1
|v2.6.1
|[http://www.pycrypto.org/ pycrypto.org]
|Unassigned
|[https://github.com/pycrypto/pycrypto/blob/master/setup.py setup.py requires distutils]
|-
|[https://layers.openembedded.org/layerindex/recipe/66925/ python3-pyparted]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.11.7
|v
|[https://github.com/rhinstaller/pyparted github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/60953/ python3-smbus]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v4.3
|v
|[https://www.kernel.org/pub/software/utils/i2c-tools/ kernel.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87014/ pyxdg]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.26
|v
|[http://freedesktop.org/wiki/Software/pyxdg freedesktop.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87524/ sanlock]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v3.8.4
|v
|[https://pagure.io/sanlock pagure.io]
|Unassigned
|Not started
|}

Deprecate distutils

2022-01-14T00:35:10Z

Moto-timo: /* List of recipes inheriting distutils* */

== Deprecating distutils*.bbclass ==

In Python 3.10 `distutils` has been deprecated and is to be removed in Python 3.12. In preparation for this, the `distutils*` classes have been deprecated and nearly all usage in oe-core has been removed.

We still have a few recipes under the meta-openembedded umbrella that inherit one of the `distutils` classes (the lowest common denominator is `distutils-common-base`)

To get a list, you can run the following command:

<blockquote>$ bitbake-layers show-recipes -i distutils-common-base -r</blockquote>

This is a call to arms, please help by picking one of the following.

=== List of recipes inheriting distutils* ===
{| class="wikitable"
!Recipe
!Layer
!Version
!Latest
!Upstream
!Assignee
!Status
|-
|[https://layers.openembedded.org/layerindex/recipe/58445/ cxxtest]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v4.4
|v
|[http://cxxtest.com/ cxxtest.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/1203/ gammu]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v1.32.0
|v1.42.0
|[https://wammu.eu/download/gammu/1.42.0/ wammu.eu]
|Moto-timo
|In progress
|-
|[https://layers.openembedded.org/layerindex/recipe/853/ iotop]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.6
|v
|[http://guichaz.free.fr/iotop/ guichaz.free.fr]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/33169/ lirc]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.10.1
|v
|[http://www.lirc.org/ lirc.org]
|Oleksandr Kravchuk
|In progress review
|-
|[https://layers.openembedded.org/layerindex/recipe/114060/ python3-dbussy]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.3
|v
|[https://github.com/ldo/dbussy github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/66996/ python3-greenlet]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.1.2
|v
|[https://greenlet.readthedocs.io/en/latest/ greenlet.readthedocs.io]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/163902/ python3-hexdump]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.3
|v
|[https://pypi.org/project/hexdump/ pypi.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/75243/ python3-pycrypto]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v2.6.1
|v2.6.1
|[http://www.pycrypto.org/ pycrypto.org]
|Unassigned
|[https://github.com/pycrypto/pycrypto/blob/master/setup.py setup.py requires distutils]
|-
|[https://layers.openembedded.org/layerindex/recipe/66925/ python3-pyparted]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.11.7
|v
|[https://github.com/rhinstaller/pyparted github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/60953/ python3-smbus]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v4.3
|v
|[https://www.kernel.org/pub/software/utils/i2c-tools/ kernel.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87014/ pyxdg]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.26
|v
|[http://freedesktop.org/wiki/Software/pyxdg freedesktop.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87524/ sanlock]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v3.8.4
|v
|[https://pagure.io/sanlock pagure.io]
|Unassigned
|Not started
|}

Deprecate distutils

2022-01-14T00:20:39Z

Moto-timo: /* List of recipes inheriting distutils* */

== Deprecating distutils*.bbclass ==

In Python 3.10 `distutils` has been deprecated and is to be removed in Python 3.12. In preparation for this, the `distutils*` classes have been deprecated and nearly all usage in oe-core has been removed.

We still have a few recipes under the meta-openembedded umbrella that inherit one of the `distutils` classes (the lowest common denominator is `distutils-common-base`)

To get a list, you can run the following command:

<blockquote>$ bitbake-layers show-recipes -i distutils-common-base -r</blockquote>

This is a call to arms, please help by picking one of the following.

=== List of recipes inheriting distutils* ===
{| class="wikitable"
!Recipe
!Layer
!Version
!Latest
!Upstream
!Assignee
!Status
|-
|[https://layers.openembedded.org/layerindex/recipe/58445/ cxxtest]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v4.4
|v
|[http://cxxtest.com/ cxxtest.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/1203/ gammu]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v1.32.0
|v1.42.0
|[https://wammu.eu/download/gammu/1.42.0/ wammu.eu]
|Moto-timo
|In progress
|-
|[https://layers.openembedded.org/layerindex/recipe/853/ iotop]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.6
|v
|[http://guichaz.free.fr/iotop/ guichaz.free.fr]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/33169/ lirc]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.10.1
|v
|[http://www.lirc.org/ lirc.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/114060/ python3-dbussy]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.3
|v
|[https://github.com/ldo/dbussy github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/66996/ python3-greenlet]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.1.2
|v
|[https://greenlet.readthedocs.io/en/latest/ greenlet.readthedocs.io]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/163902/ python3-hexdump]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.3
|v
|[https://pypi.org/project/hexdump/ pypi.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/75243/ python3-pycrypto]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v2.6.1
|v2.6.1
|[http://www.pycrypto.org/ pycrypto.org]
|Unassigned
|[https://github.com/pycrypto/pycrypto/blob/master/setup.py setup.py requires distutils]
|-
|[https://layers.openembedded.org/layerindex/recipe/66925/ python3-pyparted]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.11.7
|v
|[https://github.com/rhinstaller/pyparted github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/60953/ python3-smbus]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v4.3
|v
|[https://www.kernel.org/pub/software/utils/i2c-tools/ kernel.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87014/ pyxdg]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.26
|v
|[http://freedesktop.org/wiki/Software/pyxdg freedesktop.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87524/ sanlock]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v3.8.4
|v
|[https://pagure.io/sanlock pagure.io]
|Unassigned
|Not started
|}

Deprecate distutils

2022-01-14T00:15:56Z

Moto-timo: /* Deprecating distutils*.bbclass */

== Deprecating distutils*.bbclass ==

In Python 3.10 `distutils` has been deprecated and is to be removed in Python 3.12. In preparation for this, the `distutils*` classes have been deprecated and nearly all usage in oe-core has been removed.

We still have a few recipes under the meta-openembedded umbrella that inherit one of the `distutils` classes (the lowest common denominator is `distutils-common-base`)

To get a list, you can run the following command:

<blockquote>$ bitbake-layers show-recipes -i distutils-common-base -r</blockquote>

This is a call to arms, please help by picking one of the following.

=== List of recipes inheriting distutils* ===
{| class="wikitable"
!Recipe
!Layer
!Version
!Latest
!Upstream
!Assignee
!Status
|-
|[https://layers.openembedded.org/layerindex/recipe/58445/ cxxtest]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v4.4
|v
|[http://cxxtest.com/ cxxtest.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/1203/ gammu]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v1.32.0
|v1.42.0
|[https://wammu.eu/download/gammu/1.42.0/ wammu.eu]
|Moto-timo
|In progress
|-
|[https://layers.openembedded.org/layerindex/recipe/853/ iotop]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.6
|v
|[http://guichaz.free.fr/iotop/ guichaz.free.fr]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/33169/ lirc]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.10.1
|v
|[http://www.lirc.org/ lirc.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/114060/ python3-dbussy]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.3
|v
|[https://github.com/ldo/dbussy github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/66996/ python3-greenlet]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.1.2
|v
|[https://greenlet.readthedocs.io/en/latest/ greenlet.readthedocs.io]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/163902/ python3-hexdump]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.3
|v
|[https://pypi.org/project/hexdump/ pypi.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/75243/ python3-pycrypto]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v2.6.1
|v
|[http://www.pycrypto.org/ pycrypto.org]
|Unassigned
|[https://github.com/pycrypto/pycrypto/blob/master/setup.py setup.py requires distutils]
|-
|[https://layers.openembedded.org/layerindex/recipe/66925/ python3-pyparted]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.11.7
|v
|[https://github.com/rhinstaller/pyparted github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/60953/ python3-smbus]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v4.3
|v
|[https://www.kernel.org/pub/software/utils/i2c-tools/ kernel.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87014/ pyxdg]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.26
|v
|[http://freedesktop.org/wiki/Software/pyxdg freedesktop.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87524/ sanlock]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v3.8.4
|v
|[https://pagure.io/sanlock pagure.io]
|Unassigned
|Not started
|}

Deprecate distutils

2022-01-14T00:10:32Z

Moto-timo: Add "Deprecating distutils*.bbclass"

== Deprecating distutils*.bbclass ==

In Python 3.10 `distutils` has been deprecated and is to be removed in Python 3.12. In preparation for this, the `distutils*` classes have been deprecated and nearly all usage in oe-core has been removed.

We still have a few recipes under the meta-openembedded umbrella that inherit one of the `distutils` classes (the lowest common denominator is `distutils-common-base`

To get a list, you can run the following command:

<blockquote>$ bitbake-layers show-recipes -i distutils-common-base -r</blockquote>

This is a call to arms, please help by picking one of the following.

=== List of recipes inheriting distutils* ===
{| class="wikitable"
!Recipe
!Layer
!Version
!Latest
!Upstream
!Assignee
!Status
|-
|[https://layers.openembedded.org/layerindex/recipe/58445/ cxxtest]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v4.4
|v
|[http://cxxtest.com/ cxxtest.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/1203/ gammu]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v1.32.0
|v1.42.0
|[https://wammu.eu/download/gammu/1.42.0/ wammu.eu]
|Moto-timo
|In progress
|-
|[https://layers.openembedded.org/layerindex/recipe/853/ iotop]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.6
|v
|[http://guichaz.free.fr/iotop/ guichaz.free.fr]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/33169/ lirc]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.10.1
|v
|[http://www.lirc.org/ lirc.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/114060/ python3-dbussy]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.3
|v
|[https://github.com/ldo/dbussy github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/66996/ python3-greenlet]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v1.1.2
|v
|[https://greenlet.readthedocs.io/en/latest/ greenlet.readthedocs.io]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/163902/ python3-hexdump]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.3
|v
|[https://pypi.org/project/hexdump/ pypi.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/75243/ python3-pycrypto]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v2.6.1
|v
|[http://www.pycrypto.org/ pycrypto.org]
|Unassigned
|[https://github.com/pycrypto/pycrypto/blob/master/setup.py setup.py requires distutils]
|-
|[https://layers.openembedded.org/layerindex/recipe/66925/ python3-pyparted]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v3.11.7
|v
|[https://github.com/rhinstaller/pyparted github.com]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/60953/ python3-smbus]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-python]
|v4.3
|v
|[https://www.kernel.org/pub/software/utils/i2c-tools/ kernel.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87014/ pyxdg]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v0.26
|v
|[http://freedesktop.org/wiki/Software/pyxdg freedesktop.org]
|Unassigned
|Not started
|-
|[https://layers.openembedded.org/layerindex/recipe/87524/ sanlock]
|[https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ meta-oe]
|v3.8.4
|v
|[https://pagure.io/sanlock pagure.io]
|Unassigned
|Not started
|}

Commit Patch Message Guidelines

2020-10-08T19:44:04Z

Moto-timo: Document use of [YOCTO #12345] type syntax for Bugzilla fixes

This set of guidelines is intended to help both the developer and reviewers of
changes determine reasonable patch headers and change commit messages. Often
when working with the code, you forget that not everyone is as familiar with the
problem and/or fix as you are. Often the next person in the code doesn't
understand what or why something is done so they quickly look at patch header
and commit messages. Unless these messages are clear it will be difficult to
understand the relevance of a given change and how future changes may impact
previous decisions.

This policy refers both to patches that are being applied by recipes as well as
commit messages that are part of the source control system, usually git. A patch
file needs a header in order to describe the specific changes that are made
within that patch, while a commit message describes one or more changes to the
overall project or system. Both the patch headers and commit messages require
the same attention and basic details, however the purposes of the messages are
slightly different. A commit message documents all of the changes made as part
of a commit, while a patch header documents items specific to a single patch. In
many cases the patch header can also be used as the commit message.

This policy does not cover the testing of the changes, the technical criteria
for accepting a patch, nor the style requirements for the technical changes. See
the [http://www.openembedded.org/wiki/Styleguide Styleguide] for more information on style requirements.

By following these guidelines we will have a better record of the problems and
solutions made over the course of development. It will also help establish a
clear provenance of all of the code and changes.

Draft version, changes from last approved version:
* Revised General Information section to correct broken link
* Clarify the ''Developer's Certificate of Origin''

== General Information ==

While specific to the Linux kernel development, the following could also be
considered a general guide for any Open Source development:

https://www.linux.com/publications/how-participate-linux-community

Many of the guidelines in this document are related to the items referenced in
the link above.

Pay particular attention to section 5.3 that talks about patch preparation.
The key thing to remember is to break up your changes into logical sections.
Otherwise you run the risk of not being able to even explain the purpose of a
change in the patch headers!

In addition section 5.4 explains the purpose of the Signed-off-by: tag line. The
signed-off-by: tag line is the ''Developer's Certificate of Origin''. The full text
of which can be found in the Linux kernel's Documentation/SubmittingPatches.

Pay particular attention to section 11 of

https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Due to the importance of the ''Developer's Certificate of Origin'', part of section 11
is copied below:

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch. The rules are pretty simple: if you
can certify the below:

Developer's Certificate of Origin 1.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

then you just add a line saying::

Signed-off-by: Random J Developer <random@developer.example.org>

using your real name (sorry, no pseudonyms or anonymous contributions.)

== Patch Headers and Commit Messages ==

There seems to always be a question or two surrounding what a person
should put in a patch header, or commit message.

The general rules always apply, those being that there is a single line
short log or summary of the change (think of this as the subject when the patch
is e-mailed), and then the more detailed long log, and closure with tag lines
such as "Signed-off-by:".

If the bug relates to a bug in the Yocto Project Bugzilla (https://bugzilla.yoctoproject.org/) then a reference to that bugzilla entry should be added to the details in the form:

[YOCTO #12345]

where 12345 is the number of the bug being referenced. The commit message should be understandable in its own right without needing to look at the bug.

It is useful to include a version number in the [PATCH] prefix of the subject line, e.g. [PATCH v2] so that its known to be a new version of an earlier patch. It can also be useful to include information about what changed in the new version. This should either be in the cover letter of the series (if one is present) or be done under the detailed commit message and after a "---" separator line. This will mean git will discard the revision information when the patch is applied. This is because the history of the patch revisions is not usually useful to the information being stored against the change. If it is useful information, it should be in the commit message instead.

== New Development ==

A minimal patch or commit message would be of the format:

Short log / Statement of what needed to be changed.

(Optional pointers to external resources, such as defect tracking)

The intent of your change.

(Optional, if it's not clear from above) how your change resolves the
issues in the first part.

Tag line(s) at the end.

For example:

foobar: Adjusted the foo setting in bar

When using foobar on systems with less than a gigabyte of RAM common
usage patterns often result in an Out-of-memory condition causing
slowdowns and unexpected application termination.

Low-memory systems should continue to function without running into
memory-starvation conditions with minimal cost to systems with more
available memory. High-memory systems will be less able to use the
full extent of the system, a dynamically tunable option may be best,
long-term.

The foo setting in bar was decreased from X to X-50% in order to
ensure we don't exhaust all system memory with foobar threads.

Signed-off-by: Joe Developer <joe.developer@example.com>

The minimal commit message is good for new code development and simple changes.

The single short log message indicates what needed to be changed. It should
begin with an indicator as to the primary item changed by this work,
followed by a short summary of the change. In the above case we're indicating
that we've changed the "foobar" item, by "adjusting the foo setting in bar".

The single short log message is analogous to the git "commit summary". While no
maximum line length is specified by this policy, it is suggested that it remains
under 78 characters wherever possible.

Optionally, you may include pointers to defects this change corrects. Unless
the defect format is specified by the component you are modifying, it is
suggested that you use a full URL to specify the reference to the defect
information. Generally these pointers will precede any long description, but as
an optional item it may be after the long description.

For example, you might refer to an open source defect in the RPM project:

rpm: Adjusted the foo setting in bar

<nowiki>[RPM Ticket #65] -- http://rpm5.org/cvs/tktview?tn=65,5</nowiki>

The foo setting in bar was decreased from X to X-50% in order to
ensure we don't exhaust all system memory with foobar threads.

Signed-off-by: Joe Developer <joe.developer@example.com>

You must then have a full description of the change. Specifying the intent of
your change and if necessary how the change resolves the issue.

As mentioned above this is intended to answer the "what were you thinking"
questions down the road and to know what other impacts are likely to
result of the change needs to be reverted. It also allows for better
solutions if someone comes along later and agrees with paragraph 1
(the problem statement) and either disagrees with paragraph 2
(the design) or paragraph 3 (the implementation).

Finally one or more tag lines should exist. Each developer responsible
for working on the patch is responsible for adding a Signed-off-by: tag line.

It is not acceptable to have an empty or non-existent header, or just a single
line message. The summary and description is required for all changes.

=== Describing license changes ===

When you change the LICENSE or LIC_FILES_CHKSUM lines in the recipe, you need to
briefly explain the reason for the change in via License-Update: tag. Quite often
it's trivial, such as

License-Update: copyright years refreshed

but if the licensing terms themselves changed, do try to include a link to the upstream
making/justifying that decision.

== Importing from Elsewhere ==

If you are importing work from somewhere else, such as a cherry-pick from
another repository or a code patch pulled from a mailing list, the minimum patch
header or commit message is not enough. It does not clearly establish the
provenance of the code.

The following specifies the additional guidelines required for importing changes
from elsewhere.

By default you should keep the original author's summary and description,
along with any tag lines such as, "Signed-off-by:". If the original change that
was imported does not have a summary and/or commit message from the original
author, it is still your responsibility to add the summary and commit message to
the patch header. Just as if you wrote the code, you should be able to clearly
explain what the change does. It is also necessary to document the original
author of the change. You should indicate the original author by simply stating
"written by" or "posted to the ... mailing list by". You must not add a
Signed-off-by: tag line with their name, only the original author may add their
own Signed-off-by: tag line.

It is also required that the origin of the work be fully documented. The origin
should be specified as part of the commit message in a way that an average
developer would be able to track down the original code. URLs should reference
original authoritative sources and not mirrors.

If changes were required to resolve conflicts, they should be documented as
well. When incorporating a commit or patch from an external source, changes to
the functionality not related to resolving conflicts should be made in a
second commit or patch. This preserves the original external commit, and makes
the modifications clearly visible, and prevents confusion over the author of the
code.

Finally you must add a "Signed-off-by:" tag line to indicate that you worked
with the patch.

=== Example: Importing from Elsewhere Unmodified ===

For example, if you were to pull in the patch from the above example unmodified:

foobar: Adjusted the foo setting in bar

When using foobar on systems with less than a gigabyte of RAM common
usage patterns often result in an Out-of-memory condition causing
slowdowns and unexpected application termination.

Low-memory systems should continue to function without running into
memory-starvation conditions with minimal cost to systems with more
available memory. High-memory systems will be less able to use the
full extent of the system, a dynamically tunable option may be best,
long-term.

The foo setting in bar was decreased from X to X-50% in order to
ensure we don't exhaust all system memory with foobar threads.

Signed-off-by: Joe Developer <joe.developer@example.com>

The patch was imported from the OpenEmbedded git server
(<nowiki>git://git.openembedded.org/openembedded</nowiki>) as of commit id
b65a0e0c84cf489bfa00d6aa6c48abc5a237100f.

Signed-off-by: Your Name <your.name@openembedded.org>

The above example shows a clear way for a developer to find the original source
of the change. It indicates that the OpenEmbedded developer simply integrated
the change into the system without making any further modifications.

=== Example: Importing from Elsewhere Modified ===

When importing a patch, occasionally changes have to be made in order to resolve
conflicts. The following is an example of the commit message when the item needed
to be modified:

foobar: Adjusted the foo setting in bar

When using foobar on systems with less than a gigabyte of RAM common
usage patterns often result in an Out-of-memory condition causing
slowdowns and unexpected application termination.

Low-memory systems should continue to function without running into
memory-starvation conditions with minimal cost to systems with more
available memory. High-memory systems will be less able to use the
full extent of the system, a dynamically tunable option may be best,
long-term.

The foo setting in bar was decreased from X to X-50% in order to
ensure we don't exhaust all system memory with foobar threads.

Signed-off-by: Joe Developer <joe.developer@example.com>

The patch was imported from the OpenEmbedded git server
(<nowiki>git://git.openembedded.org/openembedded</nowiki>) as of commit id
b65a0e0c84cf489bfa00d6aa6c48abc5a237100f.

A previous change had modified the memory threshold calculation,
causing a conflict. The conflict was resolved by preserving the
memory threshold calculation from the existing implementation.

Signed-off-by: Your Name <your.name@openembedded.org>

== Patch Header Recommendations: Upstream-Status ==

In order to keep track of patches and ultimately reduce the number of patches
that are required to be maintained, we need to track the status of the patches
that are created. The following items are specific to patches applied by recipes.

In addition to the items mentioned above, we also want to track if it's
appropriate to get this particular patch into the upstream project. Since we
want to track this information, we need a consistent tag and status indicator
that can be searched.

While adding this tracking information to the patch headers is currently
optional, it is highly recommended and some maintainers may require it. It is
optional at this time so that it can be evaluated as to its usefulness over
time. Existing patches will be updated with the tag as they are modified.

As mentioned in the above, be sure to include any URL to bug tracking, mailing
lists or other reference material pertaining to the patch. Then add a new tag
"Upstream-Status:" which contains one of the following items:

'''Pending'''
- No determination has been made yet or not yet submitted to upstream

'''Submitted''' [where]
- Submitted to upstream, waiting approval
- Optionally include where it was submitted, such as the author, mailing
list, etc.

'''Accepted'''
- Accepted in upstream, expect it to be removed at next update, include
expected version info

'''Backport'''
- Backported from new upstream version, because we are at a fixed version,
include upstream version info

'''Denied'''
- Not accepted by upstream, include reason in patch

'''Inappropriate [reason]'''
- The patch is not appropriate for upstream, include a brief reason on the
same line enclosed with []
reason can be:
not author (You are not the author and do not intend to upstream this,
source must be listed in the comments)
native
licensing
configuration
enable feature
disable feature
bugfix (add bug URL here)
embedded specific
no upstream (the upstream is no longer available -- dead project)
other (give details in comments)

The various "Inappropriate [reason]" status items are meant to indicate that the
person responsible for adding this patch to the system does not intend to
upstream the patch for a specific reason. Unless otherwise noted, another
person could submit this patch to the upstream, if they do the status should be
changed to "Submitted [where]", and an additional Signed-off-by: line added to
the patch by the person claiming responsibility for upstreaming.

For example, if the patch has been submitted upstream:

rpm: Adjusted the foo setting in bar

<nowiki>[RPM Ticket #65] -- http://rpm5.org/cvs/tktview?tn=65,5</nowiki>

The foo setting in bar was decreased from X to X-50% in order to
ensure we don't exhaust all system memory with foobar threads.

Upstream-Status: Submitted [rpm5-devel@rpm5.org]

Signed-off-by: Joe Developer <joe.developer@example.com>

A future commit can change the value to "Accepted" or "Denied" as appropriate.

=== CVE Patches ===

In order to have a better control of vulnerabilities, patches that fix CVEs must contain the "CVE:" tag. This tag list all CVEs fixed by the patch. If more than one CVE is fixed, separate them using spaces.

==== Example: CVE patch header ====

This should be the header of patch that fixes grub2 CVE-2015-8370:

grub2: Fix CVE-2015-8370

<nowiki>[No upstream tracking] -- https://bugzilla.redhat.com/show_bug.cgi?id=1286966</nowiki>

Back to 28; Grub2 Authentication

Two functions suffer from integer underflow fault; the grub_username_get() and grub_password_get()located in
grub-core/normal/auth.c and lib/crypto.c respectively. This can be exploited to obtain a Grub rescue shell.

<nowiki>Upstream-Status: Accepted [http://git.savannah.gnu.org/cgit/grub.git/commit/?id=451d80e52d851432e109771bb8febafca7a5f1f2]</nowiki>
CVE: CVE-2015-8370
Signed-off-by: Joe Developer <joe.developer@example.com>

== Patches addressing bugs from Bugzilla ==

If your patch is addressing/fixing a bug from the Yocto Project bugzilla [https://bugzilla.yoctoproject.org/] then please use the <nowiki>[YOCTO #12345]</nowiki> tag in your commit message.
Where 12345 is the bug id e.g. Bug 12345 [https://bugzilla.yoctoproject.org/show_bug.cgi?id=12345]

Consistent use of this syntax allows for automated tracking of bug fixes and enhancements.

=== Example of Bugzilla tag in a commit message===

<nowiki>pseudo: Ignore mismatched inodes from the db

Currently, where pseudo finds a database entry for an inode but the path
doesn't match, it reuses that database entry metadata. This is causing
real world "corruption" of file attributes.

See [YOCTO #14057] for an example of this.

This can happen when files are deleted outside of pseudo context and the
inode is reused by a new file which pseudo then "sees".

Its possible the opposite could happen, it needs to reuse attributes
but this change would prevent it. As far as I can tell, we don't want
pseudo to reuse these attributes though so this code should be safer
and avoid bugs like the above.

</nowiki>Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

== Common Errors in Patch and Commit Messages ==

- Short log does not start with the file or component being modified. Such as
"foo: Update to new upstream version 5.8.9"

- Avoid starting the summary line with a capital letter, unless the component
being referred to also begins with a capital letter.

- Don't have one huge patch, split your change into logical subparts. It's
easier to track down problems afterward using tools such as git bisect. It also
makes it easy for people to cherry-pick changes into things like stable branches.

- Don't simply translate your change into English for a commit log. The log
"Change compare from zero to one" is bad because it describes only the code
change in the patch; we can see that from reading the patch itself. Let the code
tell the story of the mechanics of the change (as much as possible), and let
your comment tell the other details -- i.e. what the problem was, how it
manifested itself (symptoms), and if necessary, the justification for why the
fix was done in manner that it was. In other words, the long commit message
must describe *why* the change was needed (instead of what has changed).

- Don't start your commit log with "This patch..." -- we already know it is a patch.

- Don't repeat your short log in the long log. If you really really don't have
anything new and informational to add in as a long log, then don't put a long
log at all. This should be uncommon -- i.e. the only acceptable cases for no
long log would be something like "Documentation/README: Fix spelling mistakes".

- Don't put absolute paths to source files that are specific to your site, i.e.
if you get a compile error on "fs/exec.c" then tidy up the parts of the compile
output to just show that portion. We don't need to see that it was
/home/wally/src/git/oe-core/meta/classes/insane.bbclass or similar - that full
path has no value to others. Always reduce the path to something more
meaningful, such as oe-core/meta/classes/insane.bbclass.

- Always use the most significant ramification of the change in the words of
your subject/shortlog. For example, don't say "fix compile warning in foo" when
the compiler warning was really telling us that we were dereferencing complete
garbage off in the weeds that could in theory cause an OOPS under some
circumstances. When people are choosing commits for backports to stable or
distro kernels, the shortlog will be what they use for an initial sorting
selection. If they see "Fix possible OOPS in...." then these people will look
closer, whereas they most likely will skip over simple warning fixes.

- Don't put in the full 20 or more lines of a backtrace when really it is just
the last 5 or so function calls that are relevant to the crash/fix. If the entry
point, or start of the trace is relevant (i.e. a syscall or similar), you can
leave that, and then replace a chunk of the intermediate calls in the middle
with a single [...]

- Don't include timestamps or other unnecessary information, unless they are
relevant to the situation (i.e. indicating an unacceptable delay in a driver
initialization etc.)

- Don't use links to temporary resources like pastebin and friends. The commit
message may be read long after this resource timed out.

- Don't reference mirrors, but instead always reference original authoritative
sources.

- Avoid punctuation in the short log.

[[Category:Policy]]

OEDEM 2019

2019-11-01T14:57:41Z

Moto-timo: /* Planning to Attend */

== Location and Time ==

Friday, 1 November 2019 (Part of Yocto Project Summit after ELCE [October 31 - November 1]) 
OEDEM is on Day 2 of the Summit, November 1.

Details on the Yocto Project Summit are here https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019.
And the registration link https://www.cvent.com/events/yocto-project-summit-2019/registration-f185462e4bb240fea6364d2db7a270f4.aspx?fqp=true

== Logistics ==

== Remote conference link ==

== Planning to Attend ==

# Philip Balister (Crofton) [XL]
# Peter Kjellerstedt (Saur) [3XL]
# Ola Nilsson (olani) [M]
# Marco Cavallini (mckoan) [M]
# Jon Mason (jonmason) [L]
# Josef Holzmayr (LetoThe2nd) [XL]
# Mark Hatle (fray) [XL]
# Khem Raj (khem) [M]
# Scott Murray (smurray) [2XL]
# Matt Porter (mdp) [L]
# Michael Halstead (halstead) [L]
# Andrea Galbusera (gizero) [M]
# Paul Barker (paulbarker) [M]
# Jan-Simon Möller [2XL]
# Richard Purdie (RP) [L]
# Alexander Kanavin (kanavin) [S]
# Mauro Salvini [M]
# Manjukumar [S]
# Alejandro Hernandez [M]
# Jan Lübbe (shoragan) [XL]
# Behan Webster (behanw) [3XL]
# Ruslan Bilovol (rbilovol) [XL]
# Grygorii Tertychnyi (gtertych) [L]
# Bruce Ashfield (zeddii) [XL]
# Daniel Gomez (dagmcr) [L]
# Nicolas Dechesne (ndec) [XL]
# Mark Asselstine (marka) [L]
# Tom King (ka6sox) [L]
# Changhyeok Bae (chbae) [S]
# Marek Vasut [2XL]
# Robert Berger [3XL]
# Andrei Gherzan
# Tim Orling (moto-timo) [XL]

== Agenda Items ==

=== OE Developers Meeting ===

# Review and discuss talks from the Yocto Project Summit the day before.
# Have an OE event day after FOSDEM, CFP talks?
## What about SCaLE?
# TSC Report
# OE Board report
# Review of Platform Security Summit (https://www.platformsecuritysummit.com/)
# Automated Testing Summit review
# Report on Yocto Live Streaming. Need more people!
# Results of the Yocto/Openembedded new features survey (http://bit.ly/2kXvdsd) [ results -> http://bit.ly/2oAN9uu ]
# Shrink or expand oe-core?
# Systemd as default init manager (Ruslan)
# Reproducibility status (Ruslan)
# CVE analyzing tools (Ruslan, Gregory)
# Long term support
# Patch submission process (gitlab) or any other technology.
## Are we missing out on contributions by having e-mail only?
## Can we improve the reviewing process by using an actual review tool?
# BSP's carrot versus stick
# How do we help real end users? Status of Eclipse, should we try and revive it.
# Clean-up of wiki and meta layer index
# Ways to recognize corporate sponsors and those who donate hardware (and/or money)
# How do we communicate with users better? Not everyone is on mailing lists. Social Media?
# Hosting "Office hours" like meet ups @ elc(e)
# Next developer meeting?
# Multiconfig/Hetereogenous computing (need proposal on list)

=== Meeting minutes for OEDeM ===

== Minutes ==

SHARED MINUTES AT https://docs.google.com/document/d/1Qm1mJ6xLozWW9NgBnokue7TmhwgFP8b2HR8TUlaQwNs/edit?usp=sharing

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Edinburgh, Oct 2018:
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk/

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDEM 2019

2019-11-01T14:57:14Z

Moto-timo: /* Planning to Attend */

== Location and Time ==

Friday, 1 November 2019 (Part of Yocto Project Summit after ELCE [October 31 - November 1]) 
OEDEM is on Day 2 of the Summit, November 1.

Details on the Yocto Project Summit are here https://wiki.yoctoproject.org/wiki/Yocto_Project_Summit_2019.
And the registration link https://www.cvent.com/events/yocto-project-summit-2019/registration-f185462e4bb240fea6364d2db7a270f4.aspx?fqp=true

== Logistics ==

== Remote conference link ==

== Planning to Attend ==

# Philip Balister (Crofton) [XL]
# Peter Kjellerstedt (Saur) [3XL]
# Ola Nilsson (olani) [M]
# Marco Cavallini (mckoan) [M]
# Jon Mason (jonmason) [L]
# Josef Holzmayr (LetoThe2nd) [XL]
# Mark Hatle (fray) [XL]
# Khem Raj (khem) [M]
# Scott Murray (smurray) [2XL]
# Matt Porter (mdp) [L]
# Michael Halstead (halstead) [L]
# Andrea Galbusera (gizero) [M]
# Paul Barker (paulbarker) [M]
# Jan-Simon Möller [2XL]
# Richard Purdie (RP) [L]
# Alexander Kanavin (kanavin) [S]
# Mauro Salvini [M]
# Manjukumar [S]
# Alejandro Hernandez [M]
# Jan Lübbe (shoragan) [XL]
# Behan Webster (behanw) [3XL]
# Ruslan Bilovol (rbilovol) [XL]
# Grygorii Tertychnyi (gtertych) [L]
# Bruce Ashfield (zeddii) [XL]
# Daniel Gomez (dagmcr) [L]
# Nicolas Dechesne (ndec) [XL]
# Mark Asselstine (marka) [L]
# Tom King (ka6sox) [L]
# Changhyeok Bae (chbae) [S]
# Marek Vasut [2XL]
# Robert Berger [3XL]
# Andrei Gherzan
# Tim Orling [XL]

== Agenda Items ==

=== OE Developers Meeting ===

# Review and discuss talks from the Yocto Project Summit the day before.
# Have an OE event day after FOSDEM, CFP talks?
## What about SCaLE?
# TSC Report
# OE Board report
# Review of Platform Security Summit (https://www.platformsecuritysummit.com/)
# Automated Testing Summit review
# Report on Yocto Live Streaming. Need more people!
# Results of the Yocto/Openembedded new features survey (http://bit.ly/2kXvdsd) [ results -> http://bit.ly/2oAN9uu ]
# Shrink or expand oe-core?
# Systemd as default init manager (Ruslan)
# Reproducibility status (Ruslan)
# CVE analyzing tools (Ruslan, Gregory)
# Long term support
# Patch submission process (gitlab) or any other technology.
## Are we missing out on contributions by having e-mail only?
## Can we improve the reviewing process by using an actual review tool?
# BSP's carrot versus stick
# How do we help real end users? Status of Eclipse, should we try and revive it.
# Clean-up of wiki and meta layer index
# Ways to recognize corporate sponsors and those who donate hardware (and/or money)
# How do we communicate with users better? Not everyone is on mailing lists. Social Media?
# Hosting "Office hours" like meet ups @ elc(e)
# Next developer meeting?
# Multiconfig/Hetereogenous computing (need proposal on list)

=== Meeting minutes for OEDeM ===

== Minutes ==

SHARED MINUTES AT https://docs.google.com/document/d/1Qm1mJ6xLozWW9NgBnokue7TmhwgFP8b2HR8TUlaQwNs/edit?usp=sharing

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Edinburgh, Oct 2018:
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk/

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDEM 2018

2018-08-14T16:15:07Z

Moto-timo: /* Planning to Attend */

== Location and Time ==

Sunday, 21 October 2018 (before ELCE [October 22-24]) 

Expectation is to finish by 1800

Hilton Edinburgh Grosvenor
5-21 Grosvenor Street
EH12 5EF Edinburgh

SAT-NAV: EH12 5EF

5 minute walk to Haymarket Train Station

No onsite car park. Ask Crofton if you need local parking information.

== Logistics ==

Yes, we know it is Sunday. Best we could do this year.

Attendance is capped at 40. Armin is the bouncer.

== Remote conference link ==

== Planning to Attend ==

* Armpit (Akuster)
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Marco Cavallini (mckoan)
* Jan Lübbe (shoragan)
* Peter Kjellerstedt (Saur)
* Jeff Osier-Mixon (Jefro)
* Scott Murray (smurray)
* Ruslan Bilovol
* Phil Blundell
* Ross Burton (rburton)
* Richard Purdie (RP)
* Richard Leitner
* Jan-Simon Möller (dl9pf)
* Koen Kooi
* Robert Berger (will join in afternoon approx. 14:00?)
* Ulrich Ölmann (OnkelUlla)
* Trevor Woerner (tlwoerner)
* Matt Porter (mdp)
* Nicolas Dechesne (ndec)
* Grygorii Tertychnyi
* Behan Webster (behanw)
* Phil Wise (cajun-rat)
* Martin Hundebøll (hundeboll)
* Tim Orling (moto-timo)

== Agenda Items ==

=== OE Developers Meeting ===

== Minutes ==

SHARED MINUTES AT

ACTIONS identified in meeting:

=== Prior minutes ===

Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing

Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

2018 02 General Meeting

2018-01-29T15:21:31Z

Moto-timo: /* Planning to attend */

== Purpose ==
The board would like to have another general meeting before [[OEDAM 2018]].
In addition to general discussion and sharing of technical topics, it will be used to collect items for deeper discussion at [[OEDAM 2018]].

== Date and Time ==
2017-02-21 @ 8am US-CDT(UTC-06:00)/3pm CET(UTC+01:00)

[https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180221T1400 get the date/time in your timezone]

[https://www.timeanddate.com/countdown/generic?p0=1440&iso=20180221T14 countdown]

== Shared Minutes/Notes ==
https://docs.google.com/document/d/1CcYx4llC0MXOm3QYjiB7L59pMIt0gYZgHpx-B8Yshqc/edit

== Teleconference Information ==

Meeting will be held as a teleconference with a IRC channel to allow for background discussion and trouble shooting of audio.

IRC: #oe-meeting on freenode

'''Dial-in Conference'''

WebEx

URL: https://montavista.webex.com/montavista/j.php?MTID=m52131dab2389b280928d4ee131aeddec

Meeting number: 804 189 799

Meeting password: DB4E3Kj3

== Tentative Agenda ==
# Topics for deeper discussion at OEDAM
# General discussion
# Knowledge Sharing/Q&A

== Planning to attend ==
* Sean Hudson (irc:darknighte)
* Tom Rini (irc:Tartarus)
* Trevor Woerner (irc:tlwoerner)
* Denys Dmytriyenko (denix)
* Tim Orling (moto-timo)

OEDAM 2018

2018-01-29T15:20:55Z

Moto-timo: /* Planning to Attend */

== Location and Time ==

Sunday, 11 March 2018 (before ELC [March 12-14]) 
Board meeting to start at 09:30
Developer's meeting to start at 10:30
Expectation is to finish by 1800

Lunch is provided

Location: Mentor Graphics Headquarters, Wilsonville, OR
Carpooling is encouraged, see below

Yes, we know it is Sunday. Best we could do this year.

== Planning to Attend ==

Carpool note: Please add a {#} after your name if you plan to drive and can take # of people in your car other than yourself

* Jeff Osier-Mixon "Jefro" {4}
* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Manjukumar Matha (manju)
* Joshua Watt (JPEWhacker)
* Zachary Booth
* Jim Lodes
* Armin Kuster (Armpit)
* Scott Murray (smurray)
* Tim Orling (moto-timo)

== Agenda Items ==

=== OE Board ===

=== OE Developers Meeting ===

== Minutes ==

=== Prior minutes ===

Minutes from Prague, Oct 2018:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing

Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing

OEDEM 2017

2017-08-31T03:57:07Z

Moto-timo: /* Attendees */

== Location and Time ==

Sunday, 22 October 2017 
(before ELC-E [Oct 23-25])

Yes, we know it is Sunday. Best we could do this year.

Hilton Prague - Prague, Czech Republic
Start at 0900

== Attendees ==

* Jeff Osier-Mixon "Jefro"
* Behan Webster (behanw)
* Philip Balister (Crofton)
* Martin Jansa (JaMa)
* Scott Murray (smurray)
* Peter Kjellerstedt (Saur)
* Armin Kuster (Armpit)
* Marco Cavallini (mckoan)
* Paul Barker (paulbarker)
* Myunghun Chun
* Changhyeok Bae (chbae)
* Adrian Ratiu (aratiu)
* Josef Holzmayr (LetoThe2nd)
* Jan Leupold
* Anders Darander
* Sean Hudson (darknighte)
* Tim Orling (moto-timo)

NOTE: we will make every effort to provide a web/phone link for remote attendees

== Agenda Items ==

# Stack Overflow report (From someone who regularly watches stackoverflow)
# Demos for FOSDEM and other events. Good chance to (discretely) show your companies work. (Philip)

== Minutes ==

=== OEDEM: ===

OEDEM 2017

2017-08-31T03:54:42Z

Moto-timo: /* Attendees */

== Location and Time ==

Sunday, 22 October 2017 
(before ELC-E [Oct 23-25])

Yes, we know it is Sunday. Best we could do this year.

Hilton Prague - Prague, Czech Republic
Start at 0900

== Attendees ==

* Jeff Osier-Mixon "Jefro"
* Behan Webster (behanw)
* Philip Balister (Crofton)
* Martin Jansa (JaMa)
* Scott Murray (smurray)
* Peter Kjellerstedt (Saur)
* Armin Kuster (Armpit)
* Marco Cavallini (mckoan)
* Paul Barker (paulbarker)
* Myunghun Chun
* Changhyeok Bae (chbae)
* Adrian Ratiu (aratiu)
* Josef Holzmayr (LetoThe2nd)
* Jan Leupold
* Anders Darander
* Sean Hudson (darknighte)
* Tim Orling (mototimo)

NOTE: we will make every effort to provide a web/phone link for remote attendees

== Agenda Items ==

# Stack Overflow report (From someone who regularly watches stackoverflow)
# Demos for FOSDEM and other events. Good chance to (discretely) show your companies work. (Philip)

== Minutes ==

=== OEDEM: ===

OEDAM 2017

2017-01-11T04:24:44Z

Moto-timo: /* Attendees */

== Location and Time ==

Monday February 20 2017

Location TBA

(Before ELC [Feb 21-23] and Yocto Project Developer Day [Feb 24])

== Attendees ==

* Armin Kuster (armpit)
* Philip Balister (Crofton)
* Trevor Woerner (tlwoerner)
* Denys Dmytriyenko (denix)
* Stephano Cetola
* Matthew McClintock
* Tim Orling (moto-timo)

== Agenda Items ==

* Review items from last meeting in Berlin (Please add remarks)

== Minutes ==

Patchwork

2016-05-27T18:25:59Z

Moto-timo: /* pwclient */

[http://ozlabs.org/~jk/projects/patchwork/ Patchwork] is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

The URL for OpenEmbedded’s Patchwork installation is http://patches.openembedded.org. The installation is also accessible by the link in the navigation bar under ''oe services''.

== Apply patches ==

To apply a patch from the [http://patchwork.openembedded.org patchwork queue] using [[Git]], download the mbox file and apply it using
git am < file

If the submitter of the patch has not written the ''Subject'' of the email according to the OpenEmbedded policy for commit messages, then use
git commit --amend
to edit the commit message before you push.

You could also use the script in [http://cgit.openembedded.org/cgit.cgi/openembedded/tree/contrib/patchwork/pw-am.sh contrib/patchwork/pw-am.sh] this script will fetch an 'mbox' patch from patchwork and git am it
usage: pw-am.sh <number1> <number2> ...
example: 'pw-am.sh 12 13' will get the patch from http://patchwork.openembedded.org/patch/12/
and http://patches.openembedded.org/patch/13/

It is desirable to update the state of the patch in the patch queue. This could also be added to the script.

== Multiple layers sharing the same oe project on patchwork ==

http://patchwork.openembedded.org/project/oe/list/
is populated from openembedded-devel ML and shared by multiple projects, each project usually defines prefix which should be used when sending patches to ML ([meta-layer-name] tag should be used).

In order to keep main page clean, patches are split to multiple bundles, current list is:
[http://patches.openembedded.org/bundle/jama/2011.03-maintenance/?archive=both 2011.03-maintenance]
[http://patches.openembedded.org/bundle/jama/danny/?archive=both danny]
[http://patches.openembedded.org/bundle/jama/daisy/?archive=both daisy]
[http://patches.openembedded.org/bundle/jama/dizzy/?archive=both dizzy]
[http://patches.openembedded.org/bundle/jama/denzil/?archive=both denzil]
[http://patches.openembedded.org/bundle/jama/master-next/?archive=both master-next]
[http://patches.openembedded.org/bundle/jama/meta-browser/?archive=both meta-browser]
[http://patches.openembedded.org/bundle/jama/meta-efl/?archive=both meta-efl]
[http://patches.openembedded.org/bundle/jama/meta-filesystems/?archive=both meta-filesystems]
[http://patches.openembedded.org/bundle/jama/meta-fsl-arm/?archive=both meta-fsl-arm]
[http://patches.openembedded.org/bundle/jama/meta-gumstix/?archive=both meta-gumstix]
[http://patches.openembedded.org/bundle/jama/meta-handheld/?archive=both meta-handheld]
[http://patches.openembedded.org/bundle/jama/meta-initramfs/?archive=both meta-initramfs]
[http://patches.openembedded.org/bundle/jama/meta-java/?archive=both meta-java]
[http://patches.openembedded.org/bundle/jama/meta-kde/?archive=both meta-kde]
[http://patches.openembedded.org/bundle/jama/meta-networking/?archive=both meta-networking]
[http://patches.openembedded.org/bundle/jama/meta-opie/?archive=both meta-opie]
[http://patches.openembedded.org/bundle/jama/meta-perl/?archive=both meta-perl]
[http://patches.openembedded.org/bundle/jama/meta-python/?archive=both meta-python]
[http://patches.openembedded.org/bundle/jama/meta-qt3/?archive=both meta-qt3]
[http://patches.openembedded.org/bundle/jama/meta-qt5/?archive=both meta-qt5]
[http://patches.openembedded.org/bundle/jama/meta-systemd/?archive=both meta-systemd]
[http://patches.openembedded.org/bundle/jama/meta-webserver/?archive=both meta-webserver]
[http://patches.openembedded.org/bundle/jama/oe-classic-lic/?archive=both oe-classic-lic]
[http://patches.openembedded.org/bundle/jama/oe-classic/?archive=both oe-classic]

master-next bundle is used for meta-efl meta-gnome meta-gpe meta-multimedia meta-oe meta-ruby meta-systemd meta-xfce changes when they are moved to jenkins build for verification build (meta-oe-contrib/jansa/master branch).

When some patch is moved to bundle it's archive status is set to archived, but state is still "New". That's why you need to change default filter to see archived patches in bundles.

== Update the state of patches ==

You have to register to be able to update the state of patches. You can use the Web interface or `pwclient`.

== pwclient ==

`pwclient` can be used for example to retrieve patches, search the queue or update the state.

All necessary information for `pwclient` is linked from the bottom of http://patchwork.openembedded.org/project/oe/. Use

./pwclient --help

for an overview on how to use it.

[[Category:Dev]]
[[Category:Community]]

OEDAM 2016

2016-03-05T15:13:40Z

Moto-timo: /* Location and Time */

== Location and Time ==

Friday April 8 2016 (after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])

== Attendees ==
Armin Kuster (Armpit) 
Tim Orling (Moto-timo) 
Trevor Woerner 

== Agenda Items ==

== Minutes ==

OEDAM 2016

2016-03-05T15:12:58Z

Moto-timo: /* Attendees */

== Location and Time ==

Friday April 8 2016 (after ELC [Aug 4-6] and Yocto Project Developer Day [Aug 7])

== Attendees ==
Armin Kuster (Armpit) 
Tim Orling (Moto-timo) 
Trevor Woerner 

== Agenda Items ==

== Minutes ==

Organization

2015-05-07T15:51:03Z

Moto-timo: /* Current Members */

The current organization for OE is a German e.V. legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.

An 'e.V.' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.

The OpenEmbedded e.V. statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf

A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes | OpenEmbedded e.V. Statutes]]

During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.

= The current board of directors =

* ''Philip Balister''
* Treasurer ''Leon Woestenberg ''
* ''Denys Dmytriyenko''
* ''Sean Hudson''

= Current Members =
(please keep in alphabetical order)

# Alessandro Gardich
# Anders Darander
# Andrea Adami
# Andrea Galbusera
# Andreas Oberritter
# Andrei Gherzan
# Apelete Seketeli
# Chris Larson
# Cliff Brake
# Daniel Willmann
# Dave Stewart
# Denys Dmytriyenko
# Dirk Hohndel
# Dirk Opfer
# Dmitry EreminSolenikov
# Eric Bénard
# Esben Haabendal
# Florian Boor
# Frans Meulenbroeks
# Gary Thomas
# Graeme Gregory
# Graham Gower
# Henning Heinold
# Holger Freyther
# Jan Lübbe
# Jason Kridner
# Jeff Osier-Mixon
# John Willis
# Joshua Lock
# Ken Gilmer
# Khem Raj
# Koen Kooi
# Leon Woestenberg
# Liam Girdwood
# Marcin Juszkiewicz
# Marco Cavallini
# Mark Brown
# Mark Hatle
# Martin Jansa
# Michael Lauer
# Michael Smith
# Nicolas Dechesne
# Otavio Salvador
# Paul Eggleton
# Philip Balister
# Philip Blundell
# Phillip Zabel
# Richard Purdie
# Robert Schuster
# Roman I Khimov
# Saul Wold
# Scott Garman
# Sean Hudson
# Simon Busch
# Stefan Schmidt
# Steve Sakoman
# Tim Orling
# Tom King
# Tom Rini
# Trevor Woerner
# Yu Ke
# Yury Bushmelev

= TSC =
The e.V. installed the [[TSC]] to make technical steering of the project easier.

= OE Developers =
Openembedded Developers are people who have submitted code into any of the OpenEmbedded repositories. Due to the nature of OE, there are many developers, and also many different components. A good place to start is the list of git repositories [http://git.openembedded.org]. See [[OpenEmbedded Developers]] for a list of current developers.

= Todo =
* process for adding new members
* process for voting
* responsibility of the board
* conflict resolution

= Pointers for Board Members =
* [[Checklist for the General Assembly]]

= Online Voting Policy =
* [[Online Voting Policy]]

= Faq =
; Are contributions tax deductible? 
: Yes they are.
; Should I become member of the OE e.V.?
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.
; How do I become member of the OE e.V.?
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers.
; Is there a membership fee?
: Whist an e.V. can define a membership fee, the project has not chosen to set one.

= General Assemblies =
; * [[Prague, 2011]]
; * [[Barcelona, 2012]]
; * [[Edinburgh, 2013]]
; * [[Dusseldorf, 2014]]

[[Category:Verein]]

OEDAM 2015

2015-03-11T17:45:13Z

Moto-timo: /* Attendees */

== Location and Time ==

March 27-28 (after ELC and Yocto Project Developer Day)

2315 North 1st Street, San Jose, CA 95131

https://goo.gl/maps/1pRGR

Now that people are already claiming to attend by Google Hangout, I will announce our intention to also webcast via Google Hangout ;)

== Attendees ==

* Philip Balister (Crofton)
* Denys Dmytriyenko (denix)
* Armin Kuster (Armpit)
* Martin Jansa (JaMa) - 50%
* Michael Halstead (halstead) - Friday only
* Jeff Osier-Mixon (jefro)
* Paul Eggleton (bluelightning)
* Steve Arnold (nerdboy/mr_science)
* Stephanie Lockwood-Childs (wormo/sjl) - via hangout
* Ron Lockwood-Childs (speedy1) - via hangout
* Herb Kuta
* Tim Orling (moto-timo)

== Agenda Items ==

* Progress on items identified during OEDAM 2014
* Development cycle
* Removing the oe-core and meta-oe repos. These repos are now called openembedded-core and meta-openembedded/
* People still use OE-classic from time to time. Should we remove the repo?
* Community Development / Team Building (please add more examples/ideas... almond flour cake is always good...)
** Intro / crash course events
** Coordinated bug day sprints
** Other group/meetup activities