Changes

Author: AA-Turner

docs/monthly-meeting/2025-04.md

@@ -1,42 +1,17 @@
 # Documentation Community Team Meeting (April 2025)
 
-:::info
-- **Date:** 2025-04-01
-- **Time:** [19:00 UTC](https://arewemeetingyet.com/UTC/2025-04-01/19:00/Docs%20Meeting)
-- **This HackMD:** <https://hackmd.io/@encukou/pydocswg1>
-- [**Discourse thread**](https://discuss.python.org/t/documentation-community-meeting-tuesday-1st-april-2025/85787) (for April)
-- [**Meeting reports**](https://docs-community.readthedocs.io/monthly-meeting/) (the latest one might be an [**unmerged PR**](https://github.com/python/docs-community/pulls))
-- **Calendar event:** (send your e-mail to Mariatta for an invitation)
-- **How to participate:**
-  -  We are using Discord: <https://discord.gg/vKTkwJKG?event=1347635566518210613>
-  <!--  Not this month!!: Go to [Google Meet](https://meet.google.com/dii-qrzf-wkw) and ask to be let in. -->
-  -  To edit notes, click the “pencil” or “split view” button on the [HackMD document](https://hackmd.io/@encukou/pydocswg1). You need to log in (for example, with a GitHub account).
-:::
-
-By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/).
-Please take a second to read through it!
-
-
-Example topics for discussion:
-
-* Python project documentation: *relating to `docs.python.org`, `peps.python.org`, `devguide.python.org`, etc.*
-* 'Internal' items: *for and about the Community or Working Group*
-* PEP workflow
-* Follow-ups from previous meetings
-
-
-
 ## Roll call
 
 (Name / `@GitHubUsername` *[/ Discord, if different]*)
 
 - Adam Turner / `@AA-Turner`
 - Blaise Pabon / `@controlpl4n3`
+- Daniele Procida / `@evildmp`
 - Hugo van Kemenade / `@hugovk`
-- Keith / `@KeithTheEE`
 - Jeff Jacobson
+- Keith / `@KeithTheEE`
+- Ned Batchelder / `@nedbat`
 - Ryan Duve / `@ryan-duve`
-- Daniele Procida / `@evildmp`
 - Stan Ulbrych / `@StanFromIreland`
 
 
@@ -126,7 +101,9 @@ Example topics for discussion:
 - Ned notes that a frequent blocker is that a seemingly small change can represent a philosophical decision, which take time to reach consensus on.
   Experienced reviewers can spot these types of change quite quickly. How do we communicate this to new contributors?
 - It is disheartening to have a first PR languish unreviewed, or have 70 comments of back-and-forth debate.
-- Hugo noted the exemplar of the *string examples* PR, seeking to add an example snippet to each `str` method.
+- Hugo noted the exemplar of the *string examples* PR
+  ([python/cpython#119445](https://github.com/python/cpython/pull/119445),
+  seeking to add an example snippet to each `str` method.
   This is unreviewable with everything in one PR, but e.g. splitting to many small PRs might help refine the process.
   Just a single change request blocks an entire PR, whereas smaller PRs are easier to merge quickly.