Link to meeting time in common time zones.
| Search Key | Description |
|---|---|
| [todo] | Action Item |
| [decision] | Something decided on |
| [important] | Key information |
- Solicitation of notetaker
- Acceptance (and approval) of Previous Meeting Minutes
- Introduction of new members
- PSA: Change to meeting weekly at 5 pm CET on Wed
- Monthly meeting Japan mornings time Pete will inform.
- Suggestions for topics & issues/PRs to discuss
- Update on rule inflow, e.g. what about CERT rule translation
- Releasing: Check milestone and discuss timeline / further needed actions.
- Progress on mapping rules to clippy lints (or vice versa?). How to document our desired strategy aka merging the following PRs:
- Handling of uncovered language parts (Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines#394)
- Round table
- Samuel Wright ☕
- Oreste Bernardi 🚶
- Markus Hosch &☕
- Yuchen Shen ☕
- Andrew Herridge
Please add your name, and an emoji that describes your day.
Notetaker:
- Markus Hosch
For tips on how we take notes in the Safety-Critical Rust Consortium, please see the Meeting Notetaker Role doc.
- Document space: coding-guidelines
- Zulip: safety-critical-consortium: Coding Guidelines
- Kanban board
contributor experienceviewcoding guidelineview
- Set up a matrix for CERT C and MISRA rule as PR to add them to the rendered guidelines
- Add the milestone review to the US/EU and US/Asia agendas
- Try to consolidate clippy issues into the two discussed
- Find someone in S-Core who can present the S-Core safety process
- (Not so) temporary notetaker found
- Previous minutes accepted by consensus
- No new members so far
- Asia/Pacific meeting now monthly, Pete will inform next week about EU/Asia meeting
- Additional topics?
- Update on rule status
- Progress on rule topics
- Clippy lints: (find issue, discussed in point 8)
- CERT C tracking issue: Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines#336, progress to be discussed here.
- Question: Would we need to label issues that “import” from other sources?
- Question: How to determine the MVP for the ruleset. Suggestion: Work on adding issues to the milestone, let this be the single point of truth.
- Releasing the rules
- A clear definition of MVP is needed.
- Industry standards like CERT & MISRA have to be mapped, the mapping needs to be “sufficiently good” → All rules have been considered and mapped to SCR coding guidelines.
- Mapping means either mapped to (an) existing rule(s), or it’s naked as not covered → An issue needs to exist to make that rule covered.
- Create issues for remaining missing topics based on the completeness of the MISRA/CERT lists and add them to the MVP milestone.
- A clear definition of MVP is needed.
- Consolidate clippy vs rules
- No more than two issues should exist:
- Translate clippy lints to rules
- Link existing rules to clippy lints Common agreement: Neither of the tasks need to be part of the MVP. Reasoning: Standards are mandatory, rule checking can be done within projects first.
- No more than two issues should exist:
- Dealing with uncovered language parts (skipped)
- Round table
- S-Core wants to release Rust software that is qualifiable by the end of Feb
- S-Core claims safety qualified OSS. Suggestion: Have a presentation at the Rust SIG inside Eclipse
Any material to read before the meeting should be included here.
- Milestone: Prepare for launch to wider Rust community