08:34 | <rkirsling> | apparently ISO 26262 is on functional safety in the auto industry |
08:35 | <rkirsling> | (factoid from a Toyota presentation @ AsiaLLVM, encouraging making safety qualifications for compilers a thing) |
08:47 | <Aki> | Does someone from Mozilla want to edit down the summary on IDL for ECMAScript for brevity and clarity? |
08:51 | <Aki> | Also, a ton of these are missing links to proposals and slides too 😮💨 |
09:00 | <Aki> | Since I'm seeing a lot of this, I'm just going to mention it. The "Speaker's Summary of Key Points" and "Conclusion" are different things. The former, Speaker's Summary of Key Points, is instructive for what goes into the official minutes of the meeting. It should summarize your presentation and any key points brought up in conversation after. "Conclusion" is the end result of the session—i.e. "this proposal has advanced to stage 2.7; will be reviewed by XYZ & ABC" or "The authors of the proposal will return at a future meeting after working out the details on [major point discussed at plenary] to seek stage 3 advancement." |
09:01 | <arai> | which document is this about? if there's anything missing, I'm happy to fill |
09:05 | <arai> | oh, maybe the notes document? I'll look into it shortly |
09:20 | <Aki> | Right, thank you arai |
09:22 | <Aki> | This meeting wasn't our best work in terms of documentation, but it's not too late! For anyone who presented, even if you know you already wrote a summary and/or conclusion, i strongly urge you to go back and review that 1. your proposal/PR and slide links are provided 2. that there's a clear summary of the topic and discussion, and 3. that the conclusion is recorded |
09:36 | <Michael Ficarra> | I'm still having trouble understanding the difference @akirose:matrix.org |
09:44 | <Aki> | Like, a conclusion of "this propsal is now at stage 2" tells me nothing about the time we spent in the meeting. a summary that says "these were the key points brought up by the presentation. the conversation brought up important concerns regarding the implementation of this one detail. overall the committee was supportive of moving forward." |
09:45 | <Aki> | i should be able to read nothing but the summaries and get a general concept of what we talked about in the meeting. that's where meeting minutes come from. |
11:51 | <Rob Palmer> | We should document this definition in how-we-work because the question keeps getting asked. |
14:02 | <saminahusain> | This may help in the definition of what is needed for the Summary and Conclusion. Overview: • Summary captures the objective or main topic of the discussion. • Conclusion includes the agreements, resolutions and next steps. |
14:03 | <saminahusain> | More specifically: Summary • Main topics or issues discussed. • The objective or main topic of the discussion. • Capture the key salient points and decisions made during the discussion. Conclusion: • Decisions Made: Any conclusions or agreements reached. • Actions Items: Specific tasks or follow-up, who is responsible and any deadlines. • Next Steps: Future meetings or actions planned as a result of the discussion. |
21:45 | <canadahonk> | oh apologies, busy for a bit but will do before end of week |