✨ summaries and small fixes

tc39 · Nov 4, 2024 · 6a98cc0 · 6a98cc0
1 parent 38c1ecd
commit 6a98cc0
Show file tree

Hide file tree

Showing 6 changed files with 69 additions and 25 deletions.
diff --git a/meetings/2024-04/README.md b/meetings/2024-04/README.md
@@ -2,25 +2,25 @@
 
 ## Proposals
 
-| Advanced to     | Proposal                                      |
-|-----------------|-----------------------------------------------|
-| Stage 4         | Set methods                                   |
-| Stage 4         | duplicate named capture groups                |
-| Stage 3         | new Function                                  |
-| Stage 3 | Make eval-introduced global vars redeclarable |
-| Stage 2.7       | Promise.try                                   |
-| Stage 2.7       | Math.sumPrecise                               |
-| Stage 1         | Error.isError                                 |
-| Stage 1         | Strict Enforcement of 'using'                 |
-| Stage 1         | Signals                                       |
-| Withdrawn       | Array.last                                    |
+| Advanced to | Proposal                                      |
+| ----------- | --------------------------------------------- |
+| Stage 4     | Set methods                                   |
+| Stage 4     | Duplicate named capture groups                |
+| Stage 3     | eval/new Function changes for Trusted Types   |
+| Stage 3     | Make eval-introduced global vars redeclarable |
+| Stage 2.7   | Promise.try                                   |
+| Stage 2.7   | Math.sumPrecise                               |
+| Stage 1     | Error.isError                                 |
+| Stage 1     | Strict Enforcement of 'using'                 |
+| Stage 1     | Signals                                       |
+| Withdrawn   | Array.last                                    |
 
 ## Task groups
 
-* KKL has joined the conveners group for TG3; meeting cadence doubled to weekly
-* TG4 has consolidated their code into one repo & is seeking input on organization (especially re tests)
-* TG4 will be meeting in person in Munich June 24-25
+- KKL has joined the conveners group for TG3; meeting cadence doubled to weekly
+- TG4 has consolidated their code into one repo & is seeking input on organization (especially re tests)
+- TG4 will be meeting in person in Munich June 24-25
 
 ## Other
 
-* Committee reached consensus on _non-binding_ guidelines regarding coercion (and not doing it)
+- Committee reached consensus on _non-binding_ guidelines regarding coercion (and not doing it)
diff --git a/meetings/2024-06/README.md b/meetings/2024-06/README.md
@@ -0,0 +1,24 @@
+# 102nd meeting of Ecma TC39 Summary
+
+## Proposals
+
+| Advanced to | Proposal                   |
+| ----------- | -------------------------- |
+| Stage 3     | Promise.try                |
+| Stage 2.7   | RegEx escaping             |
+| Stage 2.7   | Deferred import evaluation |
+| Stage 2.7   | Joint iteration            |
+| Stage 2.7   | Atomics.pause              |
+| Stage 2     | Iterator sequencing        |
+| Stage 2     | Error.isError              |
+| Stage 2     | ESM phase imports          |
+| Stage 2     | Discard bindings           |
+
+## Task groups
+
+- TG5 has planned a user study on MessageFormat 2
+
+## Other
+
+- Big thanks to our meeting hosts Mozilla and Aalto University
+- Temporal scope reduction
diff --git a/meetings/2024-07/README.md b/meetings/2024-07/README.md
@@ -0,0 +1,20 @@
+# 103rd meeting of Ecma TC39 Summary
+
+## Proposals
+
+| Advanced to | Proposal                                                |
+| ----------- | ------------------------------------------------------- |
+| Stage 3     | RegExp.escape                                           |
+| Stage 3     | Intl.Locale                                             |
+| Stage 2.7   | Avoid capturing lexical context in indirect eval        |
+| Stage 2     | Propagate active ScriptOrModule with JobCallback Record |
+| Stage 1     | Concurrency control                                     |
+| Stage 1     | Unordered async iterator helpers                        |
+
+## Task groups
+
+## Other
+
+- Four new members, Replay.io, HeroDevs, Sentry, and JetBrains have been approved to join ECMA and will be participating in TC39
+- consensus on normative convention: pretend primitives aren't iterable
+- consensus to drop `assert` from import attributes
diff --git a/meetings/2024-07/july-29.md b/meetings/2024-07/july-29.md
@@ -745,7 +745,7 @@ WH: I think it’s more than that. I don’t think the stage advancement at the
 
 USA: All right. I believe that has been recorded. MF, you may start.
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 There is confusion about the iteration number argument to the `Atomic.pause` method. This needs to be resolved before the next meeting before stage advancement.
 
@@ -946,7 +946,7 @@ USA: Could you edit it into the notes?
 
 MF: Sure. Sure I will write it in the notes.
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 - concurrency control advanced to Stage 1
 - there was much concern about the naming of Semaphore

diff --git a/meetings/2024-07/july-30.md b/meetings/2024-07/july-30.md
@@ -79,7 +79,7 @@ MF: Thank you, that was very easy.
 
 Presenter: Frank Yung-Fong Tang (FYT)
 
-- [proposal](https://github.com/tc39/proposal-intl-locale-info)
+- [proposal](https://github.com/tc39/proposal-intl-locale-info)
 - [slides](https://docs.google.com/presentation/d/1wWDYg5BF1wNNAdC6YbBKvRtKS1acyvIP0eLkWCH2c7M)
 
 FYT: So hi everyone I am FYT and working for Google and today I will give you an update and hopefully we could wrap the thing up pretty soon. Um, so basically, I give you an update recently happen on this location, and then try to seek a consensus for a small PR hopefully that is last one we need to touch for this proposal.
@@ -114,7 +114,7 @@ FYT: Thank you.
 
 ### Conclusion
 
-Intl.Locale Update has consensus and advances to Stage 3
+Intl.Locale Update PR has consensus
 
 ## unordered async iterator helpers for Stage 1
 
@@ -167,7 +167,7 @@ MF: I would, but before that, I would like to just make the acknowledgment that
 
 MF: Yes, I would like to ask for Stage 1 now.
 
-USA: Wait. We already hard a lot of support so far. Let’s give it a minute or so to see if anybody has any more to add. Nothing on the queue yet. You have consensus. Congratulations on Stage 1.
+USA: Wait. We already heard a lot of support so far. Let’s give it a minute or so to see if anybody has any more to add. Nothing on the queue yet. You have consensus. Congratulations on Stage 1.
 
 MF: Thank you. As I mentioned, I have a couple more things if anybody wants to give feedback, I would be happy to hear. Again, this proposal, just like the concurrency control, is more worked because they are split from further along proposals. This question is further along. This would be the name of `toAsync` and name of `unordered` don’t really match even though they’re doing kind of the same thing of giving this new prototype. Should they match a little more closely? Should async iterator helpers be updated to say `.async()` or change the name `toUnordered()`? I don’t know.
 
@@ -201,7 +201,7 @@ MF: Thank you for the feedback everyone.
 
 USA: And thank you, MF. Would you like to take a minute to dictate key points and a summary?
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 MF: Yes, I would. So unordered async iterator helpers has been split out of async iterator helpers and async iterator helpers will no longer be considered in that problem space. Unordered async iterator helpers has reached Stage 1. There’s concern that we may be designing too far ahead, so the champion, myself, has committed to not trying to advance unordered async iterator helpers to Stage 2 until async iterator helpers has further advanced and we have more experience with async iterator helpers in the field.
 
@@ -822,6 +822,6 @@ CDA: We are at time. Ben can you please dictate summary for the notes and conclu
 
 BAN: I was going to say it is great that we can open up a conversation and get this work done in 30 minutes because it is opening pandemic Dora’s box. And thank you for your feedback and your assistance.
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 We need to reach out to relevant stakeholders including privacy keys on this language, and on the necessity of this language in the first place. Whether or not this is necessary. Whether this normative text is necessary rather.
diff --git a/meetings/2024-07/july-31.md b/meetings/2024-07/july-31.md
@@ -629,7 +629,7 @@ SYG: Support is a strong word.
 
 CDA: Fair enough. On that note, are there any objections for this for Stage 2? Not seeing anything new in the queue. Not hearing any voices. All right. So we’ll say it is Stage 2. CZW, can you dictate a summary and key points for the notes.
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 CZW: Yeah, the change has consensus to Stage 2 with the first row as defined by current HTML specification defined and we will bring this topic to TG3 for further discussion. And tests will be added to WPT before we advance to Stage 3.
 
@@ -792,7 +792,7 @@ MAH: It was mine. I was just clarifying that EAO’s question is related to mine
 
 CDA: Could you dictate a summary and conclusion for the notes?
 
-### Speaker's Summary of Key Points
+### Speaker's Summary of Key Points, Conclusion
 
 DE: We discussed this proposal and one thing that the committee agreed on was the name `reflect.trusted` types—sorry, Reflect.isTemplateObject. On the cross brand check we didn’t hear any particular concerns. The two things to follow up on are for SES folks is figuring out—talking through what it’s trying to do and with Mozilla folks also understanding how this relates to their goals with trusted types, as well as implementation costs and complexity for users. Are those the two things that I should follow up on or is there anything more that I should follow up on? Is it accurate to say that we’re sticking with cross realm and we agree on the `reflect.isTemplateObject` name?