Difference between revisions of "TSC"

From Openembedded.org
Jump to: navigation, search
(→‎2024 Minutes)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
=OE Technical Steering Committee=
 
=OE Technical Steering Committee=
  
−
The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the OpenEmbedded organisation.
+
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.
 
Here is the [[TSCCharter | working copy]] of the new TSC charter.
Line 65: Line 65:
  
 
Meetings are usually held in #oe-tsc on Libera Chat on 3rd Monday of each month 9PM UTC (10PM UTC during winter time).
 
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 Minutes ==

Latest revision as of 16:17, 19 August 2024

OE Technical Steering Committee

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

Here is the 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 [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 [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
  • 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


  • 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

2020 Minutes

2019 Minutes

2013 Minutes

2012 Minutes

2011 Minutes

2010 Minutes

Retrieved from "https://www.openembedded.org/index.php?title=TSC&oldid=11224"