Make links clickable in 2023 minutes (#124)

docs/monthly-meeting/2023-02.md

@@ -59,17 +59,17 @@ Please take a second to read through it!
 
 *For and about the Community or Working Group*
 
-- Trouble installing Python: https://mail.python.org/archives/list/docs@python.org/thread/I7JDNUYWIZ3QVY33IDYWFKDTZMIPIVNS/
-  - https://docs.python.org/3/using/mac.html#running-scripts-with-a-gui
+- Trouble installing Python: [mail.python.org/archives/list/docs@python.org/thread/I7JDNUYWIZ3QVY33IDYWFKDTZMIPIVNS/](https://mail.python.org/archives/list/docs@python.org/thread/I7JDNUYWIZ3QVY33IDYWFKDTZMIPIVNS/)
+  - [docs.python.org/3/using/mac.html#running-scripts-with-a-gui](https://docs.python.org/3/using/mac.html#running-scripts-with-a-gui)
 
 - Overhaul Building the Documentation section for clarity
-  - https://github.com/python/devguide/pull/1038
+  - [python/devguide#1038](https://github.com/python/devguide/pull/1038)
 
 - [python/devguide#1020](https://github.com/python/devguide/issues/1020): Function signatures in docs (positional-only markers, defaults, `[]` syntax)
   - How discoverable is the `[]` syntax to today's devs?
 
 - The docs mailing list (docs@python.org)
-    - This is linked from docs.python.org from "report a bug" section https://docs.python.org/3/bugs.html#documentation-bugs
+    - This is linked from docs.python.org from "report a bug" section [docs.python.org/3/bugs.html#documentation-bugs](https://docs.python.org/3/bugs.html#documentation-bugs)
     - [python/devguide#1025](https://github.com/python/devguide/pull/1025)
     - **Mariatta** file an issue or PR for Python docs
       - [Issue](https://github.com/python/cpython/issues/101616), [PR](https://github.com/python/cpython/pull/101617)
@@ -81,31 +81,31 @@ Please take a second to read through it!
     * Put in individual release dates
 
 * draft: Previews in pull requests #105 - need to set up RTD
-https://github.com/python/python-docs-theme/pull/105
+[python/python-docs-theme#105](https://github.com/python/python-docs-theme/pull/105)
   * **Mariatta** to set up an organization account on Read the Docs
 
 
 ### Python Project Documentation
 
 *Relating to `docs.python.org`, `peps.python.org`, `devguide.python.org`, etc.*
 
-* https://packaging.python.org/en/latest/glossary/
+* [packaging.python.org/en/latest/glossary/](https://packaging.python.org/en/latest/glossary/)
   * @CAM-Gerlach to improve the glossary. It can then be linked or copied to CPython docs.
   * improved glossary is part of PEP 639
 
 ### Improve SEO for CPython docs
 
 * (Hugo) OpenGraph metadata PRs:
 
-  * About the extension creating social media cards, asked Ee and Julien about deploying all the images in https://github.com/python/docsbuild-scripts/issues/147
+  * About the extension creating social media cards, asked Ee and Julien about deploying all the images in [python/docsbuild-scripts#147](https://github.com/python/docsbuild-scripts/issues/147)
   * Hugo: I suggest we disable the images when available, then enable after testing the points raised in the issue (only enable for web docs, check translations, don't include in archives)
 
 ### PEPs styling
 
 * (Hugo) I find the Google font, small size and tight spacing hard to read. The Google font loading causes a big initial layout shift. Trying it out with default fonts and spacing feels more readable, faster loads.
   * https://hugovk-peps.readthedocs.io/en/sfs/pep-0703/
-  * https://peps.python.org/pep-0703/
-  * Originally discussed https://discuss.python.org/t/styling-of-peps/13270/34
+  * [peps.python.org/pep-0703/](https://peps.python.org/pep-0703/)
+  * Originally discussed [discuss.python.org/t/styling-of-peps/13270/34](https://discuss.python.org/t/styling-of-peps/13270/34)
 
 * CPython docs styling is waiting for Lutra docs
 

docs/monthly-meeting/2023-08.md

@@ -30,9 +30,10 @@ Please take a second to read through it!
 ## Reports and celebrations
 
 - [PR to keep "translated" attribute on translated nodes](https://github.com/sphinx-doc/sphinx/pull/11502) landed and released! :tada:
-    - https://github.com/python/docsbuild-scripts/issues/148#issuecomment-1648836409 has the details on how it's exposed!
+    - [python/docsbuild-scripts#148 (comment)](https://github.com/python/docsbuild-scripts/issues/148#issuecomment-1648836409) has the details on how it's exposed!
 
-- [Hugo] CPython sprint at EuroPython: we had one room for code and another for documentation, and merged some 140 PRs in total! Thanks to Daniele for helping out and all the excellent docs advice! (Photos: https://mastodon.social/@hugovk/110792652209141428)
+- [Hugo] CPython sprint at EuroPython: we had one room for code and another for documentation, and merged some 140 PRs in total! Thanks to Daniele for helping out and all the excellent docs advice!
+- (Photos: [mastodon.social/@hugovk/110792652209141428](https://mastodon.social/@hugovk/110792652209141428))
 
 
 ## Discussion

docs/monthly-meeting/2023-11.md

@@ -46,7 +46,7 @@ Please take a second to read through it!
 ## Discussion
 
 - [Petr] [Railroad diagrams](https://discuss.python.org/t/36709/20)
-  - Next stream: https://youtube.com/live/vHn4YqzYlPo
+  - Next stream: [youtube.com/live/vHn4YqzYlPo](https://youtube.com/live/vHn4YqzYlPo)
   - [A free REPL for learning](https://tabatkins.github.io/railroad-diagrams/generator.html)
 
 - [Ege] Looking for help on [python-docs-bootstrapper](https://github.com/egeakman/python-docs-bootstrapper/issues/8)

docs/monthly-meeting/2023-12.md

@@ -37,7 +37,7 @@ Please take a second to read through it!
     - e.g. old issue 29428 [*Doctest documentation unclear about multi-line fixtures*](https://bugs.python.org/issue29428)
 
 - [Petr] Use emoji to illustrate good and bad example commit messages
-  - https://devguide.python.org/getting-started/git-boot-camp/#accepting-and-merging-a-pull-request
+  - [devguide.python.org/getting-started/git-boot-camp/#accepting-and-merging-a-pull-request](https://devguide.python.org/getting-started/git-boot-camp/#accepting-and-merging-a-pull-request)
   - [python/devguide#1235](https://github.com/python/devguide/pull/1235)
   - Should we do this for PEPs? See [python/docs-community#22](https://github.com/python/docs-community/issues/22)
   - [Hugo] See also [python/peps#3567](https://github.com/python/peps/pull/3567) for green/red sidebars for good/bad example code in PEPs