On Tue, Jul 23, 2024 at 3:53 AM Gerwin Klein wrote:

...

On 12 Jul 2024, at 23:39, Matt Rice wrote:

[You don't often get email from ratmice@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

On Fri, Jul 12, 2024 at 6:19 AM Gerwin Klein via Devel wrote:

...

The Technical Steering Committee (TSC) of the seL4 Foundation will hold its next public meting on:

s/meting/meeting, looking back I notice the same typo me[e]ting in the previous TSC announcement. So presumably this typo needs to be fixed in a meeting announcement template.

It’s less of a template and more of a copy/paste chain :-) Thanks!

I have added cmake to the agenda and will send an updated agenda shortly.

After reading the agenda which references EOL in particular, I should probably clarify my remarks as only now do I realize that the Ubuntu lifecycle timeline has changed since the last time host system requirements for building seL4 were updated. From what I gather starting earlier this year they now have paid 10 & 12 year Pro and Extended support in addition to the previous 5 year LTS window ("Standard support"). My hope is we can essentially ignore these new tiers of paid support and stick with the 5 year LTS window, updating host system requirements from 20.04 after 2025 which is before its extended support window officially ends in 2032.

I'm too far out of the loop with respect to specifics, but I see that Ben Leslie wrote: "I would prefer that seL4 focuses on providing a build system for building the kernel (and libsel4), and leave overall system building to the OS personality designer rather than dictating something for all seL4 based systems. Indeed this is the primary motivation of RFC-6." Whatever people do, I would urge people to be very cautious about committing future development teams to arbitrary choices that canalize ('lock in') technical debt. BobTrower On Mon, Jul 22, 2024 at 11:59 PM Gerwin Klein via Devel wrote:

Agenda updated with feedback from the mailing list and GitHub:

- Action items from last meeting

- Style and CI: - should we mandate rustfmt in style guide and CI? (code formatting, now that there is more Rust code) - should we mandate Rust clippy in CI? (Rust linter) - should we mandate or allow a Python linter in CI? Which one? (Options: ruff, mypy, flake8, pylint) - what level of lint failures do we tolerate? - bump version of cmake-format (will break current formatting) to reduce python dependency hell - should we bump the min version of cmake and when? (E.g. for EOL of Ubuntu 20.04)

- RFCs: - discuss new FPU RFC: https://github.com/seL4/rfcs/pull/26 - hear about progress on PMU, budget limit, device driver framework - make decision on old RFC-4: https://github.com/seL4/rfcs/pull/12 - any feedback on GitHub RFC implementation

Cheers, Gerwin

...

On 12 Jul 2024, at 16:16, Gerwin Klein via Devel wrote:

The Technical Steering Committee (TSC) of the seL4 Foundation will hold its next public meting on:

- Sydney: Thu, 25 Jul, 4pm - Central Europe: Thu, 25 Jul, 8am - US West Coast (LA/SF): Thu, 25 Jul, 0:00h

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/89949317341?pwd=JSC976ciVYmbDJByjSFH0chh78sCsg.1

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:

- action items from last meeting - discuss new FPU RFC: https://github.com/seL4/rfcs/pull/26 - hear about progress on PMU, budget limit, device driver framework - make decision on old RFC-4: https://github.com/seL4/rfcs/pull/12 - any feedback on GitHub RFC implementation - bump version of cmake-format (will break current formatting) to reduce python dependency hell

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 -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems

_______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems

-- Bob Trower --- From Gmail webmail account. ---