Apologies everyone, I made a mistake copy/pasting the Zoom link. The correct 
one is:

https://unsw.zoom.us/j/84519532444

(Calendar is updated as well now)

Cheers,
Gerwin


> On 11 Dec 2022, at 16:12, Gerwin Klein <[email protected]> wrote:
> 
> The Technical Steering Committee (TSC) of the seL4 Foundation will hold its 
> next public meting on:
> 
> - Sydney: Fri, 16 Dec, 8am
> - Central Europe: Tue, 15 Dec, 10pm
> - US West Coast: Tue, 15 Dec, 1pm
> 
> See also the seL4 calendar feed available from here: 
> https://sel4.systems/contact/home.pml
> 
> The meeting is by Zoom, and you can join from here:
> 
> https://unsw.zoom.us/j/5510249963
> 
> Anyone interested can join the meeting and listen to the discussion and 
> request to speak, which will be granted if time permits. Only TSC members can 
> vote. The seL4 code of conduct applies to the meeting [1].
> 
> The agenda for the meeting so far is:
> 
> - election (or re-election) of TSC chair
> 
> - split C-Parser/AutoCorres out from l4v repository
> 
> - RFCs:
>  - SMC
>    https://sel4.atlassian.net/browse/RFC-9
> 
>  - MCS: Improve constraints on grant via reply
>    https://sel4.atlassian.net/browse/RFC-13
> 
>  - MCS: set fault and timeout handler parameters while configuring TCBs
>    https://sel4.atlassian.net/browse/RFC-11
> 
>  - The seL4 Core Platform
>    https://sel4.atlassian.net/browse/RFC-5
> 
>  - The seL4 Device Driver Framework
>    https://sel4.atlassian.net/browse/RFC-12
> 
>  - Ability to build additional bootloaders inside the seL4 build system
>    https://sel4.atlassian.net/browse/RFC-4
> 
> - SIG chair nominations
> - discuss process for establishing SIGs
> 
> 
> If there are other items that I missed or you think should be on the agenda, 
> please let me know. If we can't get to an item this time, we can still 
> schedule another meeting.
> 
> Cheers,
> Gerwin (TSC chair)
> 
> [1]: https://docs.sel4.systems/processes/conduct.html
> 

_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to