|
| 1 | +--- |
| 2 | +author: ["Mariatta"] |
| 3 | +title: "Meeting Minutes: Apr 8, 2025" |
| 4 | +date: "2025-04-08T14:49:46-07:00" |
| 5 | +description: "Meeting Minutes from Python Docs Editorial Board: Apr 8, 2025" |
| 6 | +summary: "Meeting Minutes from Python Docs Editorial Board: Apr 8, 2025" |
| 7 | +tags: ["minutes"] |
| 8 | +categories: ["minutes"] |
| 9 | +series: ["Meeting Minutes"] |
| 10 | +ShowToc: false |
| 11 | +TocOpen: false |
| 12 | +members: ["Carol Willing", "Joanna Jablonski", "Mariatta", "Ned Batchelder"] |
| 13 | +--- |
| 14 | + |
| 15 | +### Agenda |
| 16 | + |
| 17 | +* [Docs audit with Savanna](https://docs.google.com/document/d/10MSDlxmgPex3ZGVr-4OggI2lqSAlv_0OTDchGlrLIkk/edit?usp=sharing) is on hold while she deals with other commitments. She has plans to work on it in the next couple months. |
| 18 | +* Language Summit |
| 19 | + |
| 20 | +### Notes |
| 21 | + |
| 22 | +* Language Summit: we have 30 minutes slot to engage with the core team. What are we gonna do? |
| 23 | + * Mariatta, Carol, and Guido will be there |
| 24 | + * Our updates: |
| 25 | + * Not much has happened, docs community have been active |
| 26 | + * There has been a few big decisions |
| 27 | + * Decrease in “entitlement/ownership” of specific docs areas |
| 28 | + * Having a named body has calmed down those and set a tone |
| 29 | + * Start with the positives we’ve seen with docs, it’s more collaborative now |
| 30 | + * Compare with when we started years ago |
| 31 | + * “How it works” documentation moved into code |
| 32 | + * Renewed emphasis on translations, usability, Irit’s work with moving some docs from devguide to code, Ned’s devguide refactoring |
| 33 | + * Sqllite3 docs in diataxis spirit |
| 34 | + * Docs audit with Joanna and Savannah |
| 35 | + * Posting meeting minutes |
| 36 | + * Seeing engagements with people outside of Core team |
| 37 | + * Separate Docs Discord server works well |
| 38 | + * Looking forward, vision and future |
| 39 | + * We are here to unblock docs decisions |
| 40 | + * Wiki. Is it not a PSF asset? (It is not) |
| 41 | + * Should CPython’s involvement in docs be Reference docs and Devguide docs? |
| 42 | + * To unblock other efforts such as translations of Docs tutorial. Should it be a PSF thing? |
| 43 | + * Why not Core team’s thing? |
| 44 | + * Maybe could free up funding opportunities if it is a PSF thing. |
| 45 | + * Talk about “How PSF can be more involved with Python docs?” |
| 46 | + * Tutorial, onboarding, etc maybe more suited outside core team. |
| 47 | + * Core team docs should just be Reference docs? |
| 48 | + * How to ensure docs discussion is productive at the language summit |
| 49 | + * Not the nitty gritty about the past decisions |
| 50 | + * Focus on role of Core team, PSF, vision |
| 51 | + * Mention the Education & outreach WG |
| 52 | + * Who are we serving, how do we serve them |
| 53 | + * Main audiences: Docs community, Python users, new users |
| 54 | + * What else core team expect from us? |
| 55 | + * What do we want to achieve? |
| 56 | + * Mariatta to start some slides (maybe not until May) |
| 57 | +* Docs audit is still on hold. Might sprint at PyCon US. |
| 58 | +* Review our Changelog: |
| 59 | + * [https://deploy-preview-28--pythoneditorialboard.netlify.app/changelog/](https://deploy-preview-28--pythoneditorialboard.netlify.app/changelog/) |
| 60 | + * [https://github.com/python/editorial-board/pull/28](https://github.com/python/editorial-board/pull/28) |
| 61 | + * Actually, a lot have happened with Editorial board! |
0 commit comments