Skip to content

Commit

Permalink
Linkify links
Browse files Browse the repository at this point in the history
  • Loading branch information
hugovk committed Oct 20, 2024
1 parent ac79a67 commit 48cff14
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/monthly-meeting/2024-10.md
Original file line number Diff line number Diff line change
Expand Up @@ -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”.
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down

0 comments on commit 48cff14

Please sign in to comment.