Remove old follow-ups

Co-authored-by: Hugo van Kemenade <[email protected]>

Author: encukou

docs/monthly-meeting/2023-08.md

@@ -71,29 +71,6 @@ Please take a second to read through it!
     - Forward plan: Merge Daniele's PR and open an issue for a followup to remove/update more outdated content
 
 
-## Follow-ups from last month(s)
-
-* Thoughts on MDN icons (see e.g. the ToC sidebar for [Document](https://developer.mozilla.org/en-US/docs/Web/API/Document)), as a compact way to flag API status in overviews?
-
-    * :wastebasket: = deprecated
-    * :warning: = non-standard/implementation-specific
-    * 🧪 = experimental/unstable
-
-* Programmatic handling of `deprecated-removed`
-  * Followup from [soft deprecation discussion](https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/73)
-  * MVP should be up by next meeting:
-    * A list of everything that's deprecated
-    * docs on the directive in the devguide
-
-* Thoughts on putting a translation progress notice in docs pages (for each language)? [python/docsbuild-scripts#148](https://github.com/python/docsbuild-scripts/issues/148)
-
-  * Sounds like a good idea
-  * Sphinx issue is open
-    * This should be done in Sphinx first - Manuel will look into it (https://github.com/sphinx-doc/sphinx/issues/11157)
-  * Spanish docs have a [neat progress page](https://python-docs-es.readthedocs.io/es/3.11/progress.html)
-    * Should we add it to all translations?
-
-
 ## Next meeting
 
 The docs team generally meets on the first Tuesday of every month.