diff --git a/src/content/sprints/cpython-documentation.md b/src/content/sprints/cpython-documentation.md new file mode 100644 index 000000000..f279f6735 --- /dev/null +++ b/src/content/sprints/cpython-documentation.md @@ -0,0 +1,32 @@ +--- +title: "Python Documentation" +numberOfPeople: "TBA" +pythonLevel: "Any" +contactPerson: + name: "Adam Turner" + github: AA-Turner +links: + - title: "Start Documenting" + url: "https://devguide.python.org/documentation/start-documenting/" + - title: "Helping with Documentation" + url: "https://devguide.python.org/documentation/help-documenting/" + - title: "Easy Issues" + url: "https://github.com/python/cpython/issues?q=is%3Aissue%20is%3Aopen%20label%3Adocs%20label%3Aeasy" + - title: "Code of Conduct" + url: "https://policies.python.org/python.org/code-of-conduct/" +--- + +Help us improve the Python documentation! + +We'll be working on all parts of the documentation, so all and any changes are +welcome -- from fixing a spelling error to documenting a new feature. + +1. Read + ['what to expect'](https://pycon.blogspot.com/2025/04/pyconus-sprints.html) + for a briefing on what happens at sprints in general. This was written for + the PyCon US sprints, but a lot applies here! +1. Fork and clone the [repository](https://github.com/python/cpython/fork) + **before** arriving at the sprints, to get started faster. +1. Use the + [Python Developer's Guide](https://devguide.python.org/documentation/start-documenting/) + to set up an environment for contributing to the documentation. diff --git a/src/content/sprints/cpython.md b/src/content/sprints/cpython.md index 7f8547322..67fc32a9f 100644 --- a/src/content/sprints/cpython.md +++ b/src/content/sprints/cpython.md @@ -8,6 +8,8 @@ contactPerson: links: - title: "CPython's Developer Guide" url: "https://devguide.python.org/" + - title: "Setup & Building" + url: "https://devguide.python.org/getting-started/setup-building/" - title: "Code of Conduct" url: "https://policies.python.org/python.org/code-of-conduct/" - title: "Easy Issues"