|
| 1 | +--- |
| 2 | +author:["Mariatta"] |
| 3 | +title:"Meeting Minutes: Oct 14, 2024" |
| 4 | +date:"2024-10-14" |
| 5 | +description:"Meeting Minutes from Python Docs Editorial Board: October 14, 2024" |
| 6 | +summary:"Meeting Minutes from Python Docs Editorial Board: October 14, 2024" |
| 7 | +tags:["minutes"] |
| 8 | +categories:["minutes"] |
| 9 | +series:["Meeting Minutes"] |
| 10 | +ShowToc:false |
| 11 | +TocOpen:false |
| 12 | +members:["Carol Willing", "Guido van Rossum", "Mariatta", "Ned Batchelder"] |
| 13 | +--- |
| 14 | + |
| 15 | +###Agenda |
| 16 | + |
| 17 | +* Contribution Guide progress |
| 18 | +* Modernizing Python Docs |
| 19 | + |
| 20 | +###Notes |
| 21 | + |
| 22 | + |
| 23 | +* Contribution Guide progress |
| 24 | +* PR created, approved. |
| 25 | + * PR build:[https://cpython-devguide--1426.org.readthedocs.build/](https://cpython-devguide--1426.org.readthedocs.build/) |
| 26 | + * PR:[https://github.com/python/devguide/pull/1426](https://github.com/python/devguide/pull/1426) |
| 27 | +* Status: |
| 28 | +* There is a new section within the current Devguide: “(draft)” item on the left menu. |
| 29 | +* How do we feel about it landing on main right now? |
| 30 | +* Worried about people ending up in the draft accidentally and thought it’s the real one. |
| 31 | +* There is an info box at the top of each contrib guide saying it’s a WIP. |
| 32 | +* Example:[https://cpython-devguide--1426.org.readthedocs.build/contrib/intro/](https://cpython-devguide--1426.org.readthedocs.build/contrib/intro/)there is a box at the top. |
| 33 | +*[Ned TODO] Add the plan of this new contrib guide under “Introduction” |
| 34 | +*[Ned TODO] embolden the section head in side bar also. |
| 35 | +* How can people discover this? |
| 36 | +*[devguide.python.org/contrib](devguide.python.org/contrib) |
| 37 | +* Or look for the menu item |
| 38 | +* Concerns with merging |
| 39 | +* Linking concerns? |
| 40 | +* Plan: flesh out the pages that don’t exist first. Then move things around later? |
| 41 | +* We use Sphinx include directives. |
| 42 | +* Make sure existing devguide maintainers and docs wg community take one last look |
| 43 | +* Hugo, Jelle, Ezio, Petr |
| 44 | +* DevGuide landing page, has a Quick Reference. It goes straight to code contribution. Feedback from people: it’s not relevant to doc contribution. Need a better pathway. |
| 45 | +* Move the Quick reference to the code contribution. |
| 46 | +* On the landing page there is the table for contribution paths, we can move that up. |
| 47 | +* Instead of table with many rows, it could be a table with two rows and bullet lists. |
| 48 | +* We could use tabs too? |
| 49 | +* What’s the next steps after merging? |
| 50 | +* Ned will write up the plan |
| 51 | +* Talk to people mentioned above |
| 52 | +* Merge the PR |
| 53 | +* More todo items from above |
| 54 | +* Get feedback from people interested in writing sections and see it grow |
| 55 | +* Do people want to be “codeowners” on the new contrib guide? |
| 56 | +* Maybe eventually |
| 57 | + |
| 58 | +* Modernizing Python Docs (Mariatta) |
| 59 | +* Inspiration[https://docs.astro.build](https://docs.astro.build) |
| 60 | +* tutorials.python.org built with new content and new tech |
| 61 | +* What is the vision? |
| 62 | +* Guido would like to see a smaller project using this new/other technology. |
| 63 | +* We can frame it as “PDEB wants to try things out and will solicit feedback from the community.” |
| 64 | +* Maybe take existing tutorials/how to and see how it works on this new tech. |
| 65 | +* See also[https://mystmd.org/](https://mystmd.org/) |
| 66 | +* Alternative tech that has JS interactivity |
| 67 | +* Start with a small prototype of a tutorial |
| 68 | +* Slice tutorial? |
| 69 | + |
| 70 | + |