Use the gh-python-team role

core-team/team-log.rst

@@ -18,10 +18,8 @@ Procedure for granting or dropping access
 -----------------------------------------
 
 To be granted the ability to manage who is a committer, you must be a
-team maintainer of the `Python core team`_ on GitHub. Once you have
+team maintainer of the :gh-python-team:`python-core` team on GitHub. Once you have
 that privilege you can add people to the team. They will be asked to
 accept the membership which they can do by visiting
 https://github.com/python and clicking on the appropriate button that
 will be displayed to them in the upper part of the page.
-
-.. _Python core team: https://github.com/orgs/python/teams/python-core

developer-workflow/development-cycle.rst

@@ -310,7 +310,7 @@ Current owners
 
 Certain actions (blocking spam accounts, inviting new users, adjusting
 organization-level settings) can only `be performed`_ by owners of the Python
-organization on GitHub. The ``@python/organization-owners`` team can be
+organization on GitHub. The :gh-python-team:`organization-owners` team can be
 mentioned to request assistance from an organization owner.
 
 .. _be performed: https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permissions-for-organization-roles

documentation/help-documenting.rst

@@ -92,8 +92,8 @@ section containing multiple problems; instead, file several issues so that it
 is easier to break the work up for multiple people and more efficient review.
 
 For help with the finer points of English technical writing, mention the
-`@python/proofreaders <https://github.com/orgs/python/teams/proofreaders>`__
-team in your issue or pull request in any `@python <https://github.com/python/>`__
+:gh-python-team:`proofreaders`
+team in your issue or pull request in any :github:`python`
 repo. If you'd like to join the team,
 `open a core-workflow issue <https://github.com/python/core-workflow/issues/new/choose>`__
 similar to

documentation/translations/coordinating.rst

@@ -15,7 +15,7 @@ Discussions about translations occur on the Python Docs Discord
 `#translations channel <https://discord.gg/h3qDwgyzga>`__ and the
 `translations category <trans_disc_>`_ of the Python Discourse.
 
-For administrative issues, ping ``@python/editorial-board``.
+For administrative issues, ping :gh-python-team:`editorial-board`.
 
 
 Starting a new translation

documentation/translations/translating.rst

@@ -371,7 +371,7 @@ The coordination team for my language is inactive, what do I do?
 
 If you would like to coordinate, open a pull request in the
 `devguide <https://github.com/python/devguide>`__ adding yourself to the table
-at the top of this page, and ping ``@python/editorial-board``.
+at the top of this page, and ping :gh-python-team:`editorial-board`.
 
 
 How do I merge translations back in after docs are moved?

testing/oss-fuzz.rst

@@ -16,15 +16,14 @@ CPython has two OSS-Fuzz projects:
 * `python3-libraries <https://github.com/google/oss-fuzz/tree/master/projects/python3-libraries>`__:
   The fuzz targets, seed corpora, and dictionaries can be found in the
   :github:`python/library-fuzzers` repository. Access to the repository is
-  managed through the `@python/fuzzers
-  <https://github.com/orgs/python/teams/fuzzers>`__ team on GitHub.
+  managed through the :gh-python-team:`fuzzers` team on GitHub.
 
 OSS-Fuzz bug reports are private when filed, so access to crash details and
 reproducer test cases is limited to those listed in the ``auto_ccs`` fields of
 the OSS-Fuzz project configuration files. Those listed can log into
 https://oss-fuzz.com/ with their Google account to view crash details,
 reproducer test cases, and project statistics.
-If you need access, contact the ``@python/fuzzers`` team.
+If you need access, contact the :gh-python-team:`fuzzers` team.
 Completed issues, and issues that remain unresolved after 90 days, are publicly
 visible in the `OSS-Fuzz issue tracker
 <https://issues.oss-fuzz.com/issues?q=(python3-libraries%20%7C%20cpython3)>`__.