Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate text on 11.2. Becoming a member of the Python triage team #702

Closed
Bonifacio2 opened this issue May 18, 2021 · 1 comment
Closed

Comments

@Bonifacio2
Copy link
Contributor

Bonifacio2 commented May 18, 2021

Part of the section is as follows:

Any existing developers on b.p.o can transition into becoming a Python triager. They can request this to any core developer, and the core developer can pass the request to the Python organization admin on GitHub. The request can be made confidentially via a DM in Zulip or Discourse, or publicly by opening an issue in the core-workflow repository.

Any contributor who is not already a developer on b.p.o can also self-nominate to be a member of Python triage team. They can request this to any core developer, confidentially via DM in Zulip or Discourse, or publicly by opening an issue in core-workflow. If a core developer agrees and is willing to vouch for them, the core developer can pass the request to the GitHub administrator. They should also be added as developer on bpo.

Most of the text on the paragraphs is the same, so I guess there's a leaner way to write it.

Source: https://devguide.python.org/triaging/#becoming-a-member-of-the-python-triage-team

@slateny
Copy link
Contributor

slateny commented May 22, 2022

Looks like it was resolved per #814

@slateny slateny closed this as completed May 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants