Zephyr: TSC Meeting Minutes (7/22/20)

Brett Preston
 

Zephyr Project TSC - 22 July 2020

Location

Join Microsoft Teams Meeting

+1 321-558-6518 United States, Orlando (Toll)

Conference ID: 435 743 999#

Local numbers | Reset PIN | Learn more about Teams | Meeting options


[In blue meeting notes, in purple post meeting addendums]

Voting TSC Members in Attendance [11 = quorum] - Quorum reached.

Voting TSC Member

Attended?

Voting TSC Member

Attended?

Voting TSC Member

Attended?

Amber Hibberd

No

Ioannis Glaropoulos

Yes

Nate Graff

susp

Anas Nashif

Yes

Johan Hedberg

Yes

Piotr Mienkowski

No

Asger Munk Nielsen 

No

Johann Fischer

No

Rasmus Abildgren

susp

Carles Cufi

Yes

Kumar Gala (Kevin Townsend - alternate)

Yes

Ruud Derwig

No

Danny Ørndrup

Yes

Mark Grosen

Yes

Ryan Erickson

No

David Brown

Yes

Maureen Helm

Yes

Scott Shawcroft

Yes

David Eriksson (Joel Westerberg - alternate)

susp

Michael Gielda (Peter Gielda - alternate)

Yes

Stefan Mijovic

susp

David Leach

Yes

Michael Scott

susp



Out of Office / Vacations

  • TSC Member Name - Dates

    • Stefan Mijovic: until July 29

    • Ruud Derwig: until August 7

    • Johan Hedberg: August 3 - August 23 

Opens

  • GitHub Permissions - Next Steps:

    • Map GitHub terms (code owner, member, collaborator, owner) to Zephyr Project charter terms (maintainer, committer, contributor)

    • Define process to grant and revoke merge rights and code ownership

  • Safety Committee [Amber]

Agenda

  • Release update and plan (2.4) [Maureen]

    • Bug Counts

      • High: 2 (threshold 0)

      • Medium: 44 (threshold 20)

      • Low: 256 (threshold 150)

    • PRs: 521

    • Weeks to Feature Freeze: 6.3

    • Weeks to Release: 9.3

    • Feature Freeze: 9/4/2020

    • Release 9/25/2020

    • [David L] Please look at bugs specific to your company/platform. Note that the next Low threshold drops even lower.

    • [Maureen] Features planned for Release

      • Reminder that if you’ve got major features planned, would like to start getting issues filed so that they can be added to the Roadmap

  • Process WG (meeting minutes) [Ioannis]

    • Vote to approve MAINTAINERS.yml in #24152

    • Last week, started discussing how to avoid oppressive language in the Zephyr code base (Issue link: https://github.com/zephyrproject-rtos/zephyr/issues/27000)

    • Zephyr modules - agreed on requirements. Expect to close discussion next Monday

    • MAINTAINERS list - spent an hour reviewing. Took feedback; used original maintainers list -- outcome is the initial .yaml file (see #24152)

      • [Carles] Open question about the format

        • [Kumar] Wouldn’t worry about the format for the vote. More about content.

      • [Danny] What about areas that are unmaintained presently? When maintainers are identified, will that trigger another vote?

        • [Ioannis] I would expect that

        • [Anas] Do we need to vote for every entry in the file?

        • [Ioannis] Can raise in the TSC mail list and if nobody objects, maintainer is added


TSC Voting to approve MAINTAINERS.yml in #24152:


Motion: Ioannis Glaropoulos

Second: Carles Cufi

Result: Vote Passes

  • Voting Members on the call: 12

  • Yes: 12

  • No: 0

  • Abstain: 0

  • Did Not Vote: 0


Voting Status

Name

Y/N/A

Active

Amber Hibberd

-

Active

Anas Nashif

Y

Active

Asger Munk Nielsen

-

Active

Carles Cufi

Y

Active

Danny Ørndrup

Y

Active

David Brown

Y

Active

David Leach

Y

Active

Ioannis Glaropoulos

Y

Active

Johan Hedberg

Y

Active

Johann Fischer

-

Active

Kumar Gala (Kevin Townsend - alternate)

Y

Active

Mark Grosen

Y

Active

Maureen Helm

Y

Active

Michael Gielda (Peter Gielda - alternate)

Y

Active

Piotr Mienkowski

-

Active

Ruud Derwig

-

Active

Ryan Erickson

-

Active

Scott Shawcroft

Y

Suspended

David Eriksson (Joel Westerberg - alternate)

-

Suspended

Michael Scott

-

Suspended

Nate Graff

-

Suspended

Rasmus Abildgren

-

Suspended

Stefan Mijovic

-



  • APIs [Carles]

    • 2 main topics: - stepper motors (https://github.com/zephyrproject-rtos/zephyr/pull/26221); 2nd part was reviewing a series of PRs trying to clean up stragglers device driver APIs (https://github.com/zephyrproject-rtos/zephyr/issues/26923)

    • LVGL Definitions - Changing kconfig options to match LVGL. Whether or not kconfigs are considered APIs or not (have not historically treated as APIs)

      • [Anas] Different levels of kconfig - those that are visible to users and those below the surface (e.g. dependencies). Concerns about kconfigs changing that would change the logic. The tooling that we have would provide some safety net - if something has been renamed, we would have an error.

      • [Carles] Problem is where do you draw the line? Has to be case-by-case

      • [Anas] Recommend having general guidelines

      • [Kumar] Haven’t looked, but there could be GitHub Action logic that exists?

      • Next step: create general guidelines in an upcoming meeting


  • UX Study [Maureen]

    • Next step: Recommend addition to a roll-up GitHub Issue. If we feel something is already addressed, we can mark it as done

    • https://github.com/zephyrproject-rtos/zephyr/issues/27073

    • Documentation for early-phase developers:

      • What is the development model for RTOS (differences from bare metal or standard OS application)?
        development):

        •  

      • What is device tree and how to use it?:

        •  

      • How to integrate sensors, drivers, and set configurations:

        •  

      • Zephyr vs. Linux concepts (where the same, where different); leveraging Linux experience with Zephyr:

        •  

      • Porting to custom boards; step-by-step tutorial:

        •  

      • Memory management, preventing stack overflows, debugging tips:

        •  

      • Document how Bluetooth and TCP/IP stack calls in Zephyr are different than Linux or Windows:

        •  

      • Introduction to new tools like West. Be clear about optional versus required use:

        •  

      • More information about West and how it uses Kconfig, DTS, Cmake:

        •  

      • Create architecture diagrams to help with some of the topics above:

        •  

      • Update error messages to be very specific to the error experienced to enable root cause identification:

        •  

      • Adding tools to help with multi-thread application development and de-bug:

        •  

    • [Scott] Guides for the maintenance side of it?

    • [Scott] https://learn.adafruit.com/blinking-led-with-zephyr-rtos

Resources





--
Brett Preston
The Linux Foundation
+1 (971) 303-9030
bpreston@...

Google Talk: bpreston@...
Skype: bprestoncf

Join tsc@lists.zephyrproject.org to automatically receive all group messages.