From 48cff149ed52098b2bdd4cc6796ee5b37f3dc2e5 Mon Sep 17 00:00:00 2001
From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Date: Sun, 20 Oct 2024 20:51:53 +0300
Subject: [PATCH] Linkify links

---
 docs/monthly-meeting/2024-10.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/monthly-meeting/2024-10.md b/docs/monthly-meeting/2024-10.md
index 2d9489c..32c2a21 100644
--- a/docs/monthly-meeting/2024-10.md
+++ b/docs/monthly-meeting/2024-10.md
@@ -47,12 +47,12 @@ to read through it!
 > beginning of the meeting.
 
 - Python Docs Editorial Board has meeting minutes published at
-  https://python.github.io/editorial-board/
+  <https://python.github.io/editorial-board/>
 
 ## Discussion
 
 - [Ned] Reorganization of the devguide --> Contributor's Guide:
-  https://github.com/python/devguide/pull/1426
+  [python/devguide#1426](https://github.com/python/devguide/pull/1426)
 
   - this grew out of a recognition that we want to recognize other types of
     contributions than “dev”.
@@ -105,9 +105,9 @@ to read through it!
       tutorials, so we wanted one official place with up-to-date info. We went with a
       separate repo, so we could use a different tech stack. We went with a plain theme,
       but there are so many themes now, even ones for Sphinx.
-      - For https://numpy.org/numpy-tutorials/ we went with a separate repo, with a
+      - For <https://numpy.org/numpy-tutorials/> we went with a separate repo, with a
         different technical setup (jupytext - text-based notebooks)
-        https://github.com/numpy/numpy-tutorials
+        <https://github.com/numpy/numpy-tutorials>
     - [Mariatta] It's great knowing that NumPy went through this path, now we need to do
       it for Python. I feel that we don't need Sphinx for tutorials.
     - [Trey] Maybe if we don't make it as fancy as astro.build, but get 80% there, it'll
@@ -124,21 +124,21 @@ to read through it!
       see a page that's technical and dense, they get scared. It'll be easier on them if
       we make them transition to information-dense docs. "Pretty and friendly" is more
       important.
-    - [Mariatta] I've also used https://docusaurus.io/ Which is a JavaScript approach.
+    - [Mariatta] I've also used <https://docusaurus.io/> Which is a JavaScript approach.
       But in the end I like astro best.
     - [Carol] in the past, the biggest change would be Markdown vs. ReST. From
       experience with other projects, Markdown lets you have the flexibility to change
       tooling if needed, so the display is separate from the content.
     - [Carol] Were there concerns at the sprint?
     - [Melissa] What Mariatta showed made me thing of learning paths:
-      https://en.wikipedia.org/wiki/Learning_pathway -- people can start where they
+      <https://en.wikipedia.org/wiki/Learning_pathway> -- people can start where they
       need, depending on how much handholding they need etc.
     - [Mariatta] Maybe the first quiz should be “what kind of a learner are you”?
     - [Carol] Moving away from the tooling: I thing there's a subset of users that use
       the current Python tutorial, others use different ones - Carpentries, ones from
       the scientific ecosystem, Dr.Chuck, Chicago[???], etc. The Carpentries have done a
       great job in the past decade coming up with learning-theory-based tutorials:
-      https://carpentries.org/community-lessons/
+      <https://carpentries.org/community-lessons/>
     - [Mariatta] So what do we do next?
     - [Carol] 2 steps: talk about it as EB, but also reach out to Tania & the community
       success project, so there's no duplication of effort. In an ideal world, this