diff --git a/src/sessions/2024-12-13.md b/src/sessions/2024-12-13.md
new file mode 100644
index 0000000..4d77211
--- /dev/null
+++ b/src/sessions/2024-12-13.md
@@ -0,0 +1,29 @@
+---
+title: 'A F# Compiler Tour: Reviewing "Scoped Nowarn"'
+preview: 'A F# Compiler Tour: Reviewing "Scoped Nowarn"'
+isDraft: true
+date: 2024-12-13T14:00:00.000Z
+slug: "2024/11/22"
+champion: "Martin"
+zoomLink: "https://us06web.zoom.us/j/86109507433?pwd=qc6GJtAjXynXVBUE7puI4RwcbOQBI4.1"
+zoomPasscode: "review"
+youtubeId: ""
+---
+
+## Topic
+
+The F\# language is driven by language suggestions in .
+Placing a suggestion is easy, the hardship is listed in the implementation.
+As we established in some of our past [sessions](../) contributing to the F\# compiler can be challeging.
+And even we you managed to make it work, in open-source, you still need a signoff from the maintainers.
+
+In this session, we will take [dotnet/fsharp/#18049](https://github.com/dotnet/fsharp/pull/18049) as a case study on how a language suggestion was implemented.
+We will try and have a mob PR review session to provide feedback on this large pull request.
+
+The evolution of the F# language is guided by community suggestions submitted to the [fsharp/fslang-suggestions](https://github.com/fsharp/fslang-suggestions) repository. While proposing a new idea is straightforward, the real challenge often lies in its implementation. As we’ve discussed in previous [sessions](../../), contributing to the F# compiler can be demanding. Even after overcoming the technical hurdles, open-source contributions require approval from maintainers to be accepted.
+
+In this session, we’ll examine [dotnet/fsharp/#18049](https://github.com/dotnet/fsharp/pull/18049) as a case study, exploring how a language suggestion made its way to implementation. Additionally, we’ll conduct a mob PR review to provide collaborative feedback on this substantial pull request.
+
+## Champion
+
+- [Martin](https://github.com/Martin521)