Enhancement: Unclear description of how to become a triager

Open
#1,594 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start in the triage-team documentation and compare the current wording with the proposed change in PR #1595. The work is done when the text clearly explains who can open a triager request issue without suggesting that contributors can open one themselves.

Written by the indexing model from the issue text.

Description

topic-triage type-bug
Describe the bug

Hi,

In the doc of triage-team. We've got this statment:

Image

AFAIK, only core devs can open the request issue of triager on the core-workflow repository. But this statement could cause confusion that anyone can open it, which lead to some request issue opened by contributers themselves. I think we can make it clearer here.

Thank you!

Edited: PR at #1595 change the statement to:

Image

Screenshots

No response

Additional context

No response

Dominant language
Python
Stars
2.1k
Forks
1k
Avg merge
2d 12h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/devguide

All issues in python/devguide

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.