From ee1c351bc8f078d51f6836816b2a85604a529a16 Mon Sep 17 00:00:00 2001 From: Unique-Usman Date: Wed, 20 Mar 2024 23:48:41 +0530 Subject: [PATCH 01/12] Update the meeting note for March 2024 --- docs/monthly-meeting/2024-03.md | 112 ++++++++++++++++++++++++++++++++ docs/monthly-meeting/index.rst | 1 + 2 files changed, 113 insertions(+) create mode 100644 docs/monthly-meeting/2024-03.md diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md new file mode 100644 index 0000000..a025a39 --- /dev/null +++ b/docs/monthly-meeting/2024-03.md @@ -0,0 +1,112 @@ +# Documentation Community Team Meeting (March 2024) + +- **Date:** 2024-03-05 +- **Time:** [20:00 UTC](https://arewemeetingyet.com/UTC/2024-03-05/20:00/Docs%20Meeting) +- **This HackMD:** https://hackmd.io/@encukou/pydocswg1 +- [**Discourse thread**](https://discuss.python.org/t/47109) (for March) +- [**Meeting reports**](https://docs-community.readthedocs.io/en/latest/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:** + - 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 (e.g. 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! + + +## Roll call + +(Name / `@GitHubUsername` *[/ Discord, if different]*) + +- Ege Akman / `@egeakman` +- Ashley Whetter / `@AWhetter` +- Carol Willing / `@willingc` +- Ned Batchelder / `@nedbat` +- Hugo van Kemenade / `@hugovk` +- Petr Viktorin / `@encukou` +- Pradyun / `@pradyunsg` +- Ezio Melotti / `@ezio-melotti` +- Erlend +- CAM / `@CAM-Gerlach` + +## Reports and celebrations + +## Discussion + + - Carol Willing: [Changelog splitting/reduction](https://github.com/python/docs-community/issues/98). At the February meeting, we had consensus that slimming down the changelog makes good sense. Let's discuss the potential approaches to do so, and try to reach consensus. + - CAM: split by minor release (feature version) would probably make most sense; we could make it more granular. + - Instead of changelog file we could have a changelog directory. Or we could chunk it in the directive. Either way is relatively straightforward. + - Ezio: We have to thing about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster. + - Hugo: On mobile, the page doesn't render well. + - CAM: Are people searching the rendered HTML, or other files. (Petr: i use Ctrl+F quite often) + - Carol: One more use case: When a bug happens, searching for when the feature was introduced. + - There are several issues: the time it takes to build, and the performance on mobile. + - Pradyun: We could make it so that there's still a search across changelogs. We could also add some Javascript to fetch the files and render them in one file. + - CAM: Or we could have one file with everything, and multiple per-version files. It'll still affect build time though. + - Ned: What's the original problem, user experience or build times? Hugo: build time is not the main concern. + - Ashley: What are the use cases of the NEWS file over the What's New pages? Hugo: I only check the What's New. + - Erlend: Do people actually read the changelog, or do they only search it? Does it really have an impact for users if we shorten the changelog? + - CAM: Maybe we should look into the stats at Plausible. + - Carol: For mobile, data can be expensive and slow, so we want this to be responsive and easy to use. + - Hugo: In the Plausible trial, it's the 256th most visited page (4,000 views). What's New was number 98 (18,000 views). There are 10,000+ pages (across 3 versions and several translations). + ``` + rank, page, views + 62 /3/whatsnew/3.11.html 32123 + 98 /3.12/whatsnew/3.12.html 17967 + 129 /3.11/whatsnew/3.11.html 11410 + 140 /3/whatsnew/3.10.html 10199 + 178 /3/whatsnew/3.8.html 7250 + 253 /3/whatsnew/3.9.html 4333 + 256 /3/whatsnew/changelog.html 4226 + 263 /3.13/whatsnew/3.13.html 4042 + 277 /3/whatsnew/index.html 3752 + 435 /zh-cn/3/whatsnew/3.11.html 1993 + 459 /3/whatsnew/3.6.html 1875 + 547 /3/whatsnew/3.7.html 1514 + 553 /3/whatsnew/3.0.html 1488 + 695 /zh-cn/3/whatsnew/index.html 990 + ``` + - Ned: How are we going to use the numbers? + - CAM: The page size for the what's new is about 3KB, changelog is about 4.6MB. That's quite big if you're not on broadband. + - Pradyun: It looks like we have agreement for splitting by directory. Any concerns with that? + - Petr: If you don't use a changelog for searching across Python versions, there isn't much else to use it for. + - [note taker was in discussion] + - Ezio: Using tabs like we use for the devguide? + - Hugo: It would not solve the downloading/page size issue. + - Ezio: (paraphrased) It would help the DOM rendering issue. + - Action item: @encukou to ask on the issue if there's a known usecase for the changelog where you don't want everything on one page. + +- [name=Erlend Aasland]: Evaluate param markup for `eval()` in `Doc/library/functions.rst` (PR [#115212](https://github.com/python/cpython/pull/115212)) + + - Erlend: Last year (https://discuss.python.org/t/16090) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline. + - Hugo: +1, it's easier to scan + - Erlend: the issue had a very long history with lots of discussion about how to communicate the meaning of the parameters, before we agreed on a wording that everyone liked. Structured parameter docs make this easier. + - Ned: I wish we could get away with the Sphinx syntax where colons are brackets somehow. + - (Carol: Way back then we didn't have brackets, remember? :) + - CAM: there's also Myst... + - Erlend: Any reservations after seeing it live? + - Carol: One of the concerns is consistency across the whole file. + - Erlend: That's a valid concern. Will try to find some time to change the markup for some other functions in the page. It's not always straightforward to do for some of the more low-level functions like compile. + - Hugo: I think it's good. + - Erlend: One aspect is that this simplifies writing the description. It's more normalized so there isn't so much space for discussion. + - Petr: Maybe we could get a graphic designer comment on the theme. + - Hugo: Tania Allard has offered to help with an accessibilty audit which could help + - Ned: There are disparate styles: `str` is monospace, *code object* is italic + - CAM: We had a big discussion about how to style ``None``; decision was to use monospace but not link it. There are differences in the markup too. + - Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs canbe over-linked. + - CAM: it's important to distinguish names that exist in Python. + - Carol: Let's ask a UI expert. + - (...) + - We should have a cheatsheet for ReST. The page in the devguide isn't clear for newcomers. + - CAM: Should we expand the current cheatsheet, or have an expanded “getting started” guide? + - Carol: I'm not entirely sure, I'm not making any radical change right now. I was looking into what would be a stumbling point for sprinters and this came up. + - CAM: BTW, in the logging docs, formatter parameter types are auto-linked but not monospaced + - (discussion on tooling) + - Ned: We should start from what we would like to see, and then make the tools do that. + +## Next meeting + +The docs team generally meets on the first Tuesday of every month around 20:00-ish UTC. + +We have a recurring Google Calendar event for the meeting. +Let Mariatta know your email address and she can invite you. diff --git a/docs/monthly-meeting/index.rst b/docs/monthly-meeting/index.rst index 03f8813..b72cdf2 100644 --- a/docs/monthly-meeting/index.rst +++ b/docs/monthly-meeting/index.rst @@ -36,3 +36,4 @@ Monthly reports in chronological order. Dec 2023 <2023-12.md> Jan 2024 <2024-01.md> Feb 2024 <2024-02.md> + Mar 2024 <2024-03.md> From b8b72e418d2d4080e5599d08d066f2c3fc1df849 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Wed, 20 Mar 2024 18:19:58 +0000 Subject: [PATCH 02/12] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index a025a39..361a01e 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -39,7 +39,7 @@ Please take a second to read through it! - Ezio: We have to thing about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster. - Hugo: On mobile, the page doesn't render well. - CAM: Are people searching the rendered HTML, or other files. (Petr: i use Ctrl+F quite often) - - Carol: One more use case: When a bug happens, searching for when the feature was introduced. + - Carol: One more use case: When a bug happens, searching for when the feature was introduced. - There are several issues: the time it takes to build, and the performance on mobile. - Pradyun: We could make it so that there's still a search across changelogs. We could also add some Javascript to fetch the files and render them in one file. - CAM: Or we could have one file with everything, and multiple per-version files. It'll still affect build time though. From fe950ee2efb7ad8b2e463cc9762c8698c3caeeff Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 12:26:38 +0530 Subject: [PATCH 03/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 361a01e..9d5ce04 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -76,7 +76,7 @@ Please take a second to read through it! - Ezio: (paraphrased) It would help the DOM rendering issue. - Action item: @encukou to ask on the issue if there's a known usecase for the changelog where you don't want everything on one page. -- [name=Erlend Aasland]: Evaluate param markup for `eval()` in `Doc/library/functions.rst` (PR [#115212](https://github.com/python/cpython/pull/115212)) +- Erlend: Evaluate param markup for `eval()` in `Doc/library/functions.rst` (PR [#115212](https://github.com/python/cpython/pull/115212)) - Erlend: Last year (https://discuss.python.org/t/16090) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline. - Hugo: +1, it's easier to scan From 63aa6c3daf4e275442b9f3b0f1668b80ba8d273a Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 12:26:45 +0530 Subject: [PATCH 04/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 9d5ce04..4a7c001 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -2,7 +2,7 @@ - **Date:** 2024-03-05 - **Time:** [20:00 UTC](https://arewemeetingyet.com/UTC/2024-03-05/20:00/Docs%20Meeting) -- **This HackMD:** https://hackmd.io/@encukou/pydocswg1 +- **This HackMD:** [https://hackmd.io/@encukou/pydocswg1](https://hackmd.io/@encukou/pydocswg1) - [**Discourse thread**](https://discuss.python.org/t/47109) (for March) - [**Meeting reports**](https://docs-community.readthedocs.io/en/latest/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) From fe48494d1640e99d50530a2f90235b2be4081d17 Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 12:26:50 +0530 Subject: [PATCH 05/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 4a7c001..0b8962b 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -78,7 +78,7 @@ Please take a second to read through it! - Erlend: Evaluate param markup for `eval()` in `Doc/library/functions.rst` (PR [#115212](https://github.com/python/cpython/pull/115212)) - - Erlend: Last year (https://discuss.python.org/t/16090) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline. + - Erlend: Last year ([https://discuss.python.org/t/16090](https://discuss.python.org/t/16090)) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline. - Hugo: +1, it's easier to scan - Erlend: the issue had a very long history with lots of discussion about how to communicate the meaning of the parameters, before we agreed on a wording that everyone liked. Structured parameter docs make this easier. - Ned: I wish we could get away with the Sphinx syntax where colons are brackets somehow. From 8d0e240943fa0ea65ea7034116e7152c66c2444b Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 12:26:56 +0530 Subject: [PATCH 06/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Erlend E. Aasland --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 0b8962b..2f0f406 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -26,7 +26,7 @@ Please take a second to read through it! - Petr Viktorin / `@encukou` - Pradyun / `@pradyunsg` - Ezio Melotti / `@ezio-melotti` -- Erlend +- Erlend Aasland / `@erlend-aasland` - CAM / `@CAM-Gerlach` ## Reports and celebrations From 1588629b16e1c6d1b0fb088b8bb2efcac7cdf4de Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:27 +0530 Subject: [PATCH 07/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 2f0f406..0aaf8f3 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -36,7 +36,7 @@ Please take a second to read through it! - Carol Willing: [Changelog splitting/reduction](https://github.com/python/docs-community/issues/98). At the February meeting, we had consensus that slimming down the changelog makes good sense. Let's discuss the potential approaches to do so, and try to reach consensus. - CAM: split by minor release (feature version) would probably make most sense; we could make it more granular. - Instead of changelog file we could have a changelog directory. Or we could chunk it in the directive. Either way is relatively straightforward. - - Ezio: We have to thing about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster. + - Ezio: We have to think about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster. - Hugo: On mobile, the page doesn't render well. - CAM: Are people searching the rendered HTML, or other files. (Petr: i use Ctrl+F quite often) - Carol: One more use case: When a bug happens, searching for when the feature was introduced. From 4899e10053bc09e00feb636a815ce538bb807bdf Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:35 +0530 Subject: [PATCH 08/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 0aaf8f3..0551997 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -38,7 +38,7 @@ Please take a second to read through it! - Instead of changelog file we could have a changelog directory. Or we could chunk it in the directive. Either way is relatively straightforward. - Ezio: We have to think about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster. - Hugo: On mobile, the page doesn't render well. - - CAM: Are people searching the rendered HTML, or other files. (Petr: i use Ctrl+F quite often) + - CAM: Are people searching the rendered HTML, or other files. (Petr: I use Ctrl+F quite often) - Carol: One more use case: When a bug happens, searching for when the feature was introduced. - There are several issues: the time it takes to build, and the performance on mobile. - Pradyun: We could make it so that there's still a search across changelogs. We could also add some Javascript to fetch the files and render them in one file. From 31487bba5dabeab01ea7d864ed58053e83b24328 Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:41 +0530 Subject: [PATCH 09/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 0551997..7c488a8 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -41,7 +41,7 @@ Please take a second to read through it! - CAM: Are people searching the rendered HTML, or other files. (Petr: I use Ctrl+F quite often) - Carol: One more use case: When a bug happens, searching for when the feature was introduced. - There are several issues: the time it takes to build, and the performance on mobile. - - Pradyun: We could make it so that there's still a search across changelogs. We could also add some Javascript to fetch the files and render them in one file. + - Pradyun: We could make it so that there's still a search across changelogs. We could also add some JavaScript to fetch the files and render them in one file. - CAM: Or we could have one file with everything, and multiple per-version files. It'll still affect build time though. - Ned: What's the original problem, user experience or build times? Hugo: build time is not the main concern. - Ashley: What are the use cases of the NEWS file over the What's New pages? Hugo: I only check the What's New. From 0414e84b57d33f3ad604a4144ebe17ba763ee8b5 Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:46 +0530 Subject: [PATCH 10/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 7c488a8..36b484c 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -67,7 +67,7 @@ Please take a second to read through it! 695 /zh-cn/3/whatsnew/index.html 990 ``` - Ned: How are we going to use the numbers? - - CAM: The page size for the what's new is about 3KB, changelog is about 4.6MB. That's quite big if you're not on broadband. + - CAM: The page size for the What's New is about 3KB, changelog is about 4.6MB. That's quite big if you're not on broadband. - Pradyun: It looks like we have agreement for splitting by directory. Any concerns with that? - Petr: If you don't use a changelog for searching across Python versions, there isn't much else to use it for. - [note taker was in discussion] From f7ccc80e9fccd2b4cfa7c2b69f41d94e515ebe72 Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:52 +0530 Subject: [PATCH 11/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index 36b484c..c518256 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -92,7 +92,7 @@ Please take a second to read through it! - Petr: Maybe we could get a graphic designer comment on the theme. - Hugo: Tania Allard has offered to help with an accessibilty audit which could help - Ned: There are disparate styles: `str` is monospace, *code object* is italic - - CAM: We had a big discussion about how to style ``None``; decision was to use monospace but not link it. There are differences in the markup too. + - CAM: We had a big discussion about how to style `None`; decision was to use monospace but not link it. There are differences in the markup too. - Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs canbe over-linked. - CAM: it's important to distinguish names that exist in Python. - Carol: Let's ask a UI expert. From deafa972a490e56ea3b9468124c9a4431277efc4 Mon Sep 17 00:00:00 2001 From: Unique-Usman <86585626+Unique-Usman@users.noreply.github.com> Date: Thu, 21 Mar 2024 14:45:58 +0530 Subject: [PATCH 12/12] Update docs/monthly-meeting/2024-03.md Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- docs/monthly-meeting/2024-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monthly-meeting/2024-03.md b/docs/monthly-meeting/2024-03.md index c518256..66dd342 100644 --- a/docs/monthly-meeting/2024-03.md +++ b/docs/monthly-meeting/2024-03.md @@ -97,7 +97,7 @@ Please take a second to read through it! - CAM: it's important to distinguish names that exist in Python. - Carol: Let's ask a UI expert. - (...) - - We should have a cheatsheet for ReST. The page in the devguide isn't clear for newcomers. + - We should have a cheatsheet for reST. The page in the devguide isn't clear for newcomers. - CAM: Should we expand the current cheatsheet, or have an expanded “getting started” guide? - Carol: I'm not entirely sure, I'm not making any radical change right now. I was looking into what would be a stumbling point for sprinters and this came up. - CAM: BTW, in the logging docs, formatter parameter types are auto-linked but not monospaced