Meeting 2025-12-02

[adamgreig]

This is the agenda for the next meeting. Please add anything you'd like to discuss below!

• Meetings: Tuesday 8pm Europe/Berlin time
• Join the Matrix chat
• IRC/Matrix logs

[thejpster]

Should we have CoPilot enabled for code reviews in our repositories?

• Yes, by default
• Teams can choose
• No

[BartMassey]

Great question. I don't know what "enabled" means here? I certainly don't want a Copilot review unless I ask for one.

[thejpster]

Actually, I have no idea how copilot integration works and if it can be enabled or disabled on a per-repository basis, or if it just comes with the user account of the reviewer.

It might be at https://github.com/organizations/rust-embedded/settings/models/access-policy, but I cannot see that page.

[adamgreig]

As far as I'm aware all Copilot related settings are disabled organisation-wide (which is the default configuration). As far as I can tell, any user can manually request a Copilot review and there's no specific setting to prevent it, the same as any GitHub user could leave a review and suggestions on a PR. We don't have automatic Copilot reviews enabled so it should only happen if someone specifically requests it.

[eldruin]

I certainly do not think they would help me (although I have not tested them).
I think the current policy makes sense but if other people prefer them always enabled, I am fine with that.

[BartMassey]

rust-embedded/discovery-mb2#80 could use a major review from someone here, for both typo fixes and large issues. I've rewritten a lot of the Serial chapter of the Disco Book, and also hacked up some other stuff, in response to feedback from a reader.

[trappitsch]

Landing page for https://rust-embedded.org

If time, I'd like to discuss the point from last week on the website, see
#886 (comment)

In brief:

I stitched together a Zola page that with the text we discussed at the website meeting a couple of weeks ago. I'd be curious to gather feedback. The proposal page is here:

https://trappitsch.github.io/rust-embedded-www/

Discussion points / further info:

• Home page is a direct copy of what @BartMassey wrote up and everybody edited during the meeting.
• I included the bookshelf and the blog into this page, however, this could also be linked by just adding a link to the current subdomain in the menu (as is done for the showcase).

[trappitsch]

Bookshelf at https://docs.rust-embedded.org/

As pointed out in the comments of #886 (reply in thread), the bookshelf could really need some work. A few questions that came to mind:

• Do we want the bookshelf to only contain WG-owned books or others too? If the latter, how to decide what goes in? (In my opinion, probably the former)
• Where is the difference between the bookshelf and the awesome list? The books are also on the awesome list, but the awesome list contains a lot more entries (also to non-WG driven books discussing embedded).

One natural split here could be the following:

• Updated bookshelf should contain only WG-owned books and a link to the awesomelist
• Awesomelist: Links to books not owned by WG, and a link to the WG-owned bookshelf.

Finally: The bookshelf could be integrated into the website repo (as proposal above) once it is worked over. That would require the docs.rust-embedded.org subdomain to be forwarded properly. My take on this is to do this once it is worked over. This would indicate to the reader: new style / integration into the website -> worked-over content.

[BartMassey]

Information: just added this PR for Rust rust-lang/rust#149553 that adds default_uwtable: true to the aarch64-unknown-none and aarch64-unknown-none-softfloat targets. This will cause DWARF unwinding tables to be generated by default even when panic = abort is set. Can be overridden with -C unwind-tables=no in the weird case that the information is not desired. The core library will be built with the new settings and now unwindable and backtraceable through.