docs: Add 2024-04-04 meeting notes

notes/2024/2024-04-04.md

@@ -0,0 +1,83 @@
+# 2024-04-04ESLint TSC Meeting Notes
+
+## Transcript
+
+[`2024-03-21-transcript.md`](2024-03-21-transcript.md)
+
+## Attending
+
+- Nicholas C. Zakas (@nzakas) - TSC
+- Milos Djermanovic (@mdjermanovic) - TSC
+- Francesco Trotta (@fasttime) - TSC
+
+@nzakas moderated, and @sam3k took notes.
+
+## Topics
+
+### Status of previous actionable items
+
+- [x] [feat: support the new flat config](https://github.com/eslint/create-config/issues/51) (Completed)
+- [x] [Switch Playground to flat config](https://github.com/eslint/eslint.org/issues/507) (Completed)
+
+### [Change Request: `--inspect-config` CLI option](https://github.com/eslint/eslint/issues/18255)
+
+**TSC Summary:** This issue seeks to add a --inspect-config CLI option that will launch the config inspector (similar to --init does with @eslint/create-config).
+
+**TSC Question:** Shall we accept this proposal?
+
+**Resolution:** We've agreed to accept this proposal
+
+**Action Items:** @nzakas will work on the PR
+
+### [feat: Support different names for code block languages](https://github.com/eslint/eslint-plugin-markdown/issues/245)
+
+**TSC Summary:** This change seeks to use recognizable filename extensions for common code block types like node, javascript, ecmascript to .js, markdown to .md, and typescript to .ts. Currently, the plugin would use the code block type as the filename extension, so javascript becomes 0.javascript, which is a bit confusing.
+
+**TSC Question:** This represents a breaking change, do we want to accept this and publish a new major version?
+
+**Resolution:** We've agreed to accept this proposal but will omit `node` option at this time.
+
+### [Change Request: Provide a way for rules to apply suggestions to other files](https://github.com/eslint/eslint/issues/17881)
+
+**TSC Summary:** This issue requests to formalize the ability of ESLint rules to make changes to files other than the file currently being linted. This can happen when a plugin is managing a separate file, such as eslint-plugin-expect-type, which generates type information and stores it in a snapshot file.
+
+**TSC Question:** Is this something we want to explore?
+
+**Resolution:** We've decided to table the discussion until we have time to review it
+
+**Action Items:** @mdjermanovic will review it
+
+### [Change Request: Consider also moving slightly-more-than-formatting rules out of core](https://github.com/eslint/eslint/issues/17681)
+
+**TSC Summary:** This issue seeks to deprecate two additional rules, multiline-comment-style and line-comment-position, and allow @stylistic to take over maintenance in the plugin.
+
+**TSC Question:** Shall we do so?
+
+**Resolution:** We've decided to deprecate these two rules and coordinate with `eslint-stylistic` to incorporate and maintain them going forward.
+
+### [v9.0.0](https://github.com/orgs/eslint/projects/4/views/2)
+
+All has been completed! We are going to get this one in as well:
+
+* [Change Request: `--inspect-config` CLI option](https://github.com/eslint/eslint/issues/18255)
+
+### Scheduled release for April 5th, 2024
+
+**Action Items:**
+
+- @nzakas will review [docs: version selectors synchronization](https://github.com/eslint/eslint/pull/18265) which is needed before release
+- @mdjermanovic will release the following:
+ - `@eslint/create-config`
+ - `eslint/js`
+ - `eslint`
+- @mdjermanovic will prepare a PR for `eslint.org` to redirect `docs/next/*` to `docs/latest/*`
+- @nzakas will submit the release to [Github Release Radar](https://github.com/github/release-radar)
+- @nzakas will update the blog
+
+### [Contributor Pool for March 2024](https://github.com/issues?q=org%3Aeslint+label%3A%22contributor+pool%22+merged%3A2024-03-01..2024-03-31+)
+
+- @mnkiefer: $1,500 for #17850
+- @webpro: $750 for #18005
+- @ota-meshi: $750 for #18041
+- @kirkwaiblinger: $200 for #18188 
+- @lo1tuma: $200 for #18152