Zephyr: TSC Meeting Minutes (5/13/20)

Brett Preston
 

Zephyr Project TSC - 13 May 2020

Location

Meeting link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_OTY0NGZmYjktMGVhYS00ZjI5LTllYjItOWM1NWVkN2FjZDEy%40thread.v2/0?context=%7b%22Tid%22%3a%22686ea1d3-bc2b-4c6f-a92c-d99c5c301635%22%2c%22Oid%22%3a%2262b63b80-05d3-4465-b5a0-f04e4e156f10%22%7d

 

+1 213-437-3346 United States, Los Angeles (Toll)

Conference ID: 317 954 735#

 

Local numbers: https://dialin.teams.microsoft.com/488d1b50-0dd2-4ca1-aee4-92bb50a48081?id=317954735

 


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

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

Voting TSC Member

Attended?

Voting TSC Member

Attended?

Voting TSC Member

Attended?

Amber Hibberd

Yes

Johan Hedberg

Yes

Piotr Mienkowski

Yes

Anas Nashif

Yes

Johann Fischer

No

Rasmus Abildgren

susp

Asger Munk Nielsen 

Yes

Kumar Gala (Kevin Townsend - alternate)

Yes

Ruud Derwig

Yes

Carles Cufi

Yes

Mark Grosen

Yes

Ryan Erickson

Yes

Danny Ørndrup

Yes

Maureen Helm

Yes

Scott Shawcroft

Yes

David Brown

Yes

Michael Gielda (Peter Gielda - alternate)

No

Stefan Mijovic

No

David Leach

Yes

Michael Scott

susp



Ioannis Glaropoulos

Yes

Nate Graff

susp




Out of Office / Vacations

  • TSC Member Name - Dates

    • x

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.3) [Carles]

    • Release Plan is up to date for 2.3

    • Focus is now on bug fixing

      • Target: 20 medium bugs or less by May 29

      • Bug fixes coming in -- Please keep tagging 2.3 milestone

    • Release Notes - Contributions welcome / Carles will send email to the mail list

    • We are currently in the 2.3 stabilization period, therefore new features require TSC approval to be included in the release. Please review this list before the meeting.

      • [Anas] In general, needs more than just submitting and CI passing. Sanity Check?

      • Leave 24949 out of vote for now

      • Vote to approve 24949, 25214, 25248, 25158, 25056, 23682, 25199, 25167

        • Motion: Maureen

        • Second: Kumar

    • Vote Results: Vote Passes

      • Voting Members: 15

      • Yes: 13

      • No: None

      • Abstain: 2

  • GDB python support in the SDK [Kumar]

  • Coding Guidelines [Amber]

    • Email sent out a week ago following up on action items, including approximate number of violations for the rules group is putting forth; which of these rules will be checked by a scanning tool; 1.1, 15.5 removed; clarification around what TSC will be voting on (voting to approve ~150 rules according to the stages implementation). How will we publish the rules? As a first step, just listing the MISRA rule (without any summary; nor enforcement). Next step - publish our own summary.

    • [Carles] ACRN has their own set of coding guidelines. Any chance Zephyr can leverage?

      • [Amber] ACRN coding guideline is based off of MISRA; tied to LDRA. 

      • [Flavio] While initially based off of MISRA, they are now more tied to LDRA. Not as straightforward to do the mapping.

      • [Flavio] Still investigating the best tool to use right now

      • Considering options including IAR, Verisoft, PVS Studio…

    • [Amber] Would publish just the rule number, potentially referencing publicly available snippets

    • (from chat - Scott) Don't implement the rules until the CI can enforce it.

    • [Maureen] When is it appropriate to vote on this?

      • [Amber] Have been giving time for questions/concerns. 

    • [Anas] Vote is about the recommendation. Additional discussion/decisions down the road.

    • Example Suite: https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite

      • This is an official MISRA repo with rules examples

    • [Kumar] Funding for community members to have access?

      • Yes - need to establish process to request; criteria

    • AI - Amber: Bring to TSC call next week a summary in preparation for a vote

  • Toolchain WG (meeting minutes) [Torsten]

  • Process WG (meeting minutes) [Ioannis]

  • APIs [Carles]

Resources



*** Previous minutes available at: 
https://docs.google.com/document/d/1xiO721JwqW_H_BpGMOJ4PY3vLVy7nxW2fhy841nsP10/edit#heading=h.x36xe8bnwr9r


--
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.