Safety Critical C++

Minutes Repository

This repository contains minutes from meetings of the Safety Critical C++ group.

Guidelines

• You don't need to record everything verbatim, but record the essence of each comment.
• The minute taker always has priority; it's not rude to interrupt if you need information or time.
  • If you don't know someone's name, interrupt and ask.
  • If you aren't sure that you captured or heard something correctly, interrupt and ask.
  • If you've fallen behind, interrupt and ask for a pause.
  • If you aren't ready to start, tell the chair; they'll wait.
• Always take attendance.
• Record polls verbatim; the specific wording is important.
• Use GitHub Flavored Markdown or Bikeshed.
• Minutes should be named YYYY_MM_DD__safety_critical[__optional_subject].{md,bs}.

Example

# Safety Critical C++
## YYYY-MM-DD [Telecon|Face-to-Face]

**Attendance:**
- BAL: Bryce Adelstein Lelbach (NVIDIA)
- BR:  Bryce Ready (Zenuity, autonomous vehicles)
- SB:  Some Body (organization, domain)
- ...

**Agenda:**

- What will we talk about (N minutes).

### Discussion Topic

BAL: I said this.

BR: And I said this.

[laughter]

???: Someone said this, but we don't know who.

[presentation of some slides/document; provide a link, and just minute questions/discussion, not the presentation]

__POLL: Polls should be statements not questions.__

|Strongly For|Weakly For|Neutral|Weakly Against|Strongly Against|
|-|-|-|-|-|
|6|4|2|0|1|

__Attendance:__ 15

__POLL: What should we name this feature (vote for all the ones you can tolerate, vote as many times as you want).__

|Name|Votes|
|-|-|
|foo  |8|
|bar  |9|
|gozer|0|

__Attendance:__ 15

### Conclusion

**Action Items:**
- Person Responsible: Task.
- ...