diff --git a/core-team/team-log.rst b/core-team/team-log.rst index 77639ebf1..3b438abc4 100644 --- a/core-team/team-log.rst +++ b/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 diff --git a/developer-workflow/development-cycle.rst b/developer-workflow/development-cycle.rst index 5d9073ed3..bcc78d842 100644 --- a/developer-workflow/development-cycle.rst +++ b/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 diff --git a/documentation/help-documenting.rst b/documentation/help-documenting.rst index 23520375c..d9894573c 100644 --- a/documentation/help-documenting.rst +++ b/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 `__ -team in your issue or pull request in any `@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 `__ similar to diff --git a/documentation/translations/coordinating.rst b/documentation/translations/coordinating.rst index 82cfce74f..1936dbb7b 100644 --- a/documentation/translations/coordinating.rst +++ b/documentation/translations/coordinating.rst @@ -15,7 +15,7 @@ Discussions about translations occur on the Python Docs Discord `#translations channel `__ and the `translations category `_ of the Python Discourse. -For administrative issues, ping ``@python/editorial-board``. +For administrative issues, ping :gh-python-team:`editorial-board`. Starting a new translation diff --git a/documentation/translations/translating.rst b/documentation/translations/translating.rst index d954004b9..e75ccb93c 100644 --- a/documentation/translations/translating.rst +++ b/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 `__ 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? diff --git a/testing/oss-fuzz.rst b/testing/oss-fuzz.rst index ec2449a4f..4bf4a5b41 100644 --- a/testing/oss-fuzz.rst +++ b/testing/oss-fuzz.rst @@ -16,15 +16,14 @@ CPython has two OSS-Fuzz 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 - `__ 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 `__.