[seL4] Re: Public TSC meeting on Fri, 29 Jan

Attached the notes from this meeting, they will be added to the TSC website this week. We did not get through all of the agenda and I'll shortly post the time for the meeting where we continue. Cheers, Gerwin

On 29 Jan 2021, at 14:32, Gerwin Klein wrote:

Updated agenda for the TSC meeting today:

- updates from the TSC chair and committees: - seL4 public Jira - Jira + GitHub sync - reviewers who have joined - more GitHub tests

- discussion points: - do we have too many different forums? - bug/issue classification (Jira is now public, we shouldn't call everything a bug) - more in-tree docs - test infrastructure - extend RFC process slightly? (see https://sel4.atlassian.net/browse/RFC-6?focusedCommentId=14886& ) - when/how should Committer/Admin role change for people who have left D61 and had the role based on org membership - endorsement process for training and products - back-porting security fixes to older releases (e.g. fixes to previously unverified features)

- vote on: - Platform Owner proposal

- discuss, potentially vote on RFC proposals: - https://sel4.atlassian.net/browse/RFC-6 - https://sel4.atlassian.net/browse/RFC-5 - https://sel4.atlassian.net/browse/RFC-4

I'm also attaching the Platform Owner proposal that is mentioned above. It mainly defines what a platform owner is and what is expected of them.

Cheers, Gerwin

A platform owner: - is the maintainer of platform specific kernel and library code for that platform - is the “driver” for that platform (setting the direction where things are going for the platform) - is usually one of the main code contributors for that platform

- has the following responsibilities: - keep the platform working, make sure sel4test and sel4bench are passing on the master branch for all supported configurations (esp MCS, but also multicore, and IOMMU/VCPU where relevant/appropriate) - make sure the platform is part of sel4test - write and maintain documentation for the platform, - help to keep the verification passing for verified configurations (only relevant for a few platforms, but might increase in the future) - handle bug reports for that platform on github and devel mailing list (has access to github issues and/or the new sel4 Jira at sel4.atlassian.net for this if desired) - handle support requests/questions for that platform (if low-key, ideally publicly on the mailing list, but also paid support etc for bigger things) - review and help merge PRs for that platform (relevant PRs should have one approving review from the platform owner if possible) - providing binaries for bootloader and load instructions would be desirable

- if other development on the master branch has platform impact (from contributions or D61), it should preferably include relevant platform code updates already, but might need consultation with the platform owner to get done, i.e. the basic expectation would be “you break it, you fix it”, but people sometimes might need help.

- the foundation advertises platform owners on the website, and platform owners would link back to the foundation.