|
1 | | -# Docs WG Agenda/Minutes -- February 2022 |
| 1 | +# Documentation Community's Team Meeting (February 7, 2022) |
2 | 2 |
|
3 | | -- **Date:** 2022-01-07 |
4 | | -- **Time:** [22:00 UTC](https://arewemeetingyet.com/UTC/2022-02-07/22:00/Docs%20WG) |
5 | | -- **This HackMD:** [https://hackmd.io/@encukou/pydocswg1](https://hackmd.io/@encukou/pydocswg1) |
6 | | -- **GitHub issue:** Agenda Planning Issue |
7 | | -- **Calendar for future meetings:** XXX |
8 | | - |
9 | | -By participating in this meeting, you are agreeing to abide by and uphold the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). |
10 | | -Please take a second to read through it! |
11 | 3 |
|
12 | 4 | ## Quick updates - Introductions |
13 | 5 |
|
@@ -68,7 +60,7 @@ A "guidance document is at the end of the document" |
68 | 60 |
|
69 | 61 | [Julien] Maybe we need guidelines, maybe not. We can definitely review PRs. |
70 | 62 |
|
71 | | -[Petr] We don't need to write the rules before hand, to block our work. We can start by just reviewing stuff. |
| 63 | +[Petr] We don't need to write the rules beforehand, to block our work. We can start by just reviewing stuff. |
72 | 64 |
|
73 | 65 | [Carol] I think that's a good way to start. Because this is both core devs& non-core devs, if there's an issue it should come back to this agenda, instead of a mailing list. |
74 | 66 |
|
@@ -188,7 +180,7 @@ From the issue tracker: |
188 | 180 | - Suggestions and ideas from Typing Summit [python/docs-community#8](https://github.com/python/docs-community/issues/8) |
189 | 181 | - French translation sprint [python/docs-community#9](https://github.com/python/docs-community/issues/9) |
190 | 182 | - Use Sphinx for pep builds and better rendering [python/docs-community#10](https://github.com/python/docs-community/issues/10) |
191 | | - > This seems to be progressing well mostly thanks to Adam's work; we just need to do some tweaks to the styling and appearance; main blocker is just PEP 676's approval and then getting the infra moved over to whatever we decide on (RTD, GHP, Netlify, etc). A huge improvement and going to unlock a lot of possibilities going forward while being far more maintainable than the hacked-together legacy csystem. I'm a little unsure if this is directly within scope here, though. [CAM-Gerlach] |
| 183 | + > This seems to be progressing well mostly thanks to Adam's work; we just need to do some tweaks to the styling and appearance; main blocker is just PEP 676's approval and then getting the infra moved over to whatever we decide on (RTD, GHP, Netlify, etc.). A huge improvement and going to unlock a lot of possibilities going forward while being far more maintainable than the hacked-together legacy csystem. I'm a little unsure if this is directly within scope here, though. [CAM-Gerlach] |
192 | 184 | - Is it in scope? :) |
193 | 185 | - Having a "fast path" for documentation contributions [python/docs-community#13](https://github.com/python/docs-community/issues/13) |
194 | 186 | - Move language selection to a dedicated page? [python/docs-community#14](https://github.com/python/docs-community/issues/14) |
|
0 commit comments