@@ -0,0 +1,46 @@
+# Documentation Community Team Meeting (September 1, 2026)
+
+## Roll call
+
+(Name / `@GitHubUsername` *[/ Discord, if different]*)
+
+* Ryan Duve / `@ryan-duve`
+* Hugo van Kemenade / `@hugovk`
+* Ned Batchelder / `@nedbat`
+* KeithTheEE / `@keithTheEE`
+
+
+## Reports and celebrations
+
+- [Hugo] A page detailing the
+  [time complexity of built-in types](https://docs.python.org/dev/library/time-complexity.html)
+  was added to the documentation!
+- [Hugo] Please test Python 3.15: https://hugovk.dev/blog/2026/help-test-python-315/
+
+
+## Discussion
+
+- [Hugo] Transifex subscription update
+  - Transifex has offered to sponsor in-kind.
+  - We can add a mention to the devguide, since we already describe how to use Transifex.
+
+- [Ned] [python/cpython#156682](https://github.com/python/cpython/pull/156682)
+  split the built-ins from the stdlib documentation.
+  - This will require redirects, which are in `python/psf-salt`
+    - Update patterns in psf-salt, get approved ([python/psf-salt#651](https://github.com/python/psf-salt/pull/651)).
+    - Merge doc changes, including backports, which go live within minutes.
+    - Merge the redirects.
+    - Clear CDN cache, check with Jacob Coffee. It's a `curl` command.
+      - Every docs build does this for every page.
+      - In the [`docsbuild-scripts`](https://github.com/python/docsbuild-scripts/)
+        repository.
+    - `psf-salt` does server-side redirects.
+      - This couldn't handle splitting a large page into many smaller pages.
+
+- Should we use this meeting for triaging docs issues?
+
+
+## Next meeting
+
+- [Ryan] Time permitting, we can have someone screen-share and lead a triage
+  session of open docs GitHub issues in the next meeting.
@@ -26,3 +26,4 @@ Monthly reports in chronological order.
    Jun 2026 <2026-06.md>
    Jul 2026 <2026-07.md>
    Aug 2026 <2026-08.md>
+   Sep 2026 <2026-09.md>