rmoff commented on code in PR #825:
URL: https://github.com/apache/flink-web/pull/825#discussion_r2792471002


##########
docs/content/posts/2026-02-01-community-update.md:
##########
@@ -0,0 +1,157 @@
+---
+authors:
+- davidrad: null
+  name: David Radley
+date: "2026-02-02T08:00:00Z"
+excerpt: Flink Community update for February 2026
+title: Flink Community Update - February'26
+aliases:
+- /news/2026/02/02/community-update.html
+---
+
+#  Flink Community update for February 2026
+
+<!-- TOC -->
+* [Flink Community update for February 
2026](#flink-community-update-for-february-2026)
+  * [Bringing us up to date - a brief summary of what has happened in Flink 
since 2020 up to end of 
2025.](#bringing-us-up-to-date---a-brief-summary-of-what-has-happened-in-flink-since-2020-up-to-end-of-2025)
+  * [January 2026 overview](#january-2026-overview)
+  * [Flink related Blogs](#flink-related-blogs)
+  * [Summary of Apache Flink Dev List (covering January 
2026)](#summary-of-apache-flink-dev-list-covering-january-2026)
+    * [Key Themes](#key-themes)
+    * [Community Announcements](#community-announcements)
+      * [New Committers](#new-committers)
+      * [New PMC Member](#new-pmc-member)
+    * [FLIP Activity](#flip-activity)
+      * [Accepted - being implemented](#accepted---being-implemented)
+      * [Being discussed](#being-discussed)
+    * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release)
+  * [For more information](#for-more-information)

Review Comment:
   ```suggestion
   * [Bringing us up to date - a brief summary of what has happened in Flink 
since 2020 up to end of 
2025.](#bringing-us-up-to-date---a-brief-summary-of-what-has-happened-in-flink-since-2020-up-to-end-of-2025)
   * [January 2026 overview](#january-2026-overview)
   * [Flink related Blogs](#flink-related-blogs)
   * [Summary of Apache Flink Dev List (covering January 
2026)](#summary-of-apache-flink-dev-list-covering-january-2026)
     * [Key Themes](#key-themes)
     * [Community Announcements](#community-announcements)
       * [New Committers](#new-committers)
       * [New PMC Member](#new-pmc-member)
     * [FLIP Activity](#flip-activity)
       * [Accepted - being implemented](#accepted---being-implemented)
       * [Being discussed](#being-discussed)
     * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release)
   * [For more information](#for-more-information)
   ```



##########
docs/content/posts/2026-02-01-community-update.md:
##########
@@ -0,0 +1,157 @@
+---
+authors:
+- davidrad: null
+  name: David Radley
+date: "2026-02-02T08:00:00Z"
+excerpt: Flink Community update for February 2026
+title: Flink Community Update - February'26
+aliases:
+- /news/2026/02/02/community-update.html
+---
+
+#  Flink Community update for February 2026
+
+<!-- TOC -->
+* [Flink Community update for February 
2026](#flink-community-update-for-february-2026)
+  * [Bringing us up to date - a brief summary of what has happened in Flink 
since 2020 up to end of 
2025.](#bringing-us-up-to-date---a-brief-summary-of-what-has-happened-in-flink-since-2020-up-to-end-of-2025)
+  * [January 2026 overview](#january-2026-overview)
+  * [Flink related Blogs](#flink-related-blogs)
+  * [Summary of Apache Flink Dev List (covering January 
2026)](#summary-of-apache-flink-dev-list-covering-january-2026)
+    * [Key Themes](#key-themes)
+    * [Community Announcements](#community-announcements)
+      * [New Committers](#new-committers)
+      * [New PMC Member](#new-pmc-member)
+    * [FLIP Activity](#flip-activity)
+      * [Accepted - being implemented](#accepted---being-implemented)
+      * [Being discussed](#being-discussed)
+    * [Kubernetes Operator 1.14.0 Release](#kubernetes-operator-1140-release)
+  * [For more information](#for-more-information)

Review Comment:
   no point including the title in the ToC



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to