Skip to content

Update devguide regarding the new Python Triagers team #339

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.

Sign up for GitHub

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

Jump to bottom
Closed
Mariatta opened this issue Jul 8, 2019 · 10 comments
Closed

Update devguide regarding the new Python Triagers team #339

Mariatta opened this issue Jul 8, 2019 · 10 comments
Labels
help wanted project: triagers Adding triagers project

Comments

@Mariatta
Copy link
Member

Mariatta commented Jul 8, 2019

Document the role and expectations
@Mariatta
Copy link
Member Author

Mariatta commented Jul 8, 2019

Related discussion:. https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992

Also document that exsiting triagers in bpo are welcome to request themselves be added to the GitHub triagers team.

@Mariatta Mariatta added help wanted project: triagers Adding triagers project labels Jul 8, 2019
@aeros
Copy link

aeros commented Jul 9, 2019 •
edited
Loading

I wouldn't mind helping with this. Do you think that it should be an expansion upon the already existing section over at https://devguide.python.org/triaging/ ?

@Mariatta
Copy link
Member Author

Mariatta commented Jul 9, 2019

Thanks. Sounds good to me to expand that section, or adding a new section of just "triaging pull request on GitHub".

@aeros
Copy link

aeros commented Jul 9, 2019

Alright, I'll create a new section towards the end of the triaging page for now (with a link at the top for easy reference) and create a PR over on python/devguide (linking to this issue) after typing up a draft, based on the proposal and discussion over at https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992.

aeros added a commit to aeros/devguide that referenced this issue Jul 9, 2019
@aeros
Added a "Bug Triager" section to "triaging.rst"
ac6e6f5 
Component of issue python/core-workflow/issues/339 and based on the proposal from https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992/19.
@aeros aeros mentioned this issue Jul 9, 2019
Merged
@aeros
Copy link

aeros commented Jul 9, 2019 •
edited
Loading

Instead of explaining it in the context of triaging on GitHub, this PR focused around explaining the role of the Bug Triager (with the expectations on GitHub for the role in bullet points). The details of the each responsibility could definitely be expanded upon further if needed, or there could be a separate section which describes the GitHub triage process. This initial draft just provided an overview based on the information in the proposal rather than an in-depth GitHub triaging guide.

@aeros
Copy link

aeros commented Jul 11, 2019

@Mariatta As far as naming for the role itself goes, is the preference towards Python Triager , Bug Triager, or something else? I mostly just used Bug Triager since the name of the team on the proposal on the discussion boards was the Bug Triage team. I can edit the PR accordingly.

@Mariatta
Copy link
Member Author

I'm not sure what the name should be :) I asked in #334

@Mariatta
Copy link
Member Author

another issue related to this is python/devguide#296
It would be great to explain the purpose of each GitHub labels. The triage section explains each components of the issue tracker clearly, but nothing has been written about our GitHub labels yet.

@aeros
Copy link

aeros commented Jul 11, 2019

It would be great to explain the purpose of each GitHub labels.

Agreed, this would be a good idea for the next component to start working on, once the role summary section is finished.

Mariatta added a commit to python/devguide that referenced this issue Jul 22, 2019
@aeros @willingc @Mariatta
python/core-workflow#339: Add "Python triage team" section to "triagi…
c2d7cfa 
…ng.rst" (#506)

* Added a "Bug Triager" section to "triaging.rst"

* Moved "Bug Triager" section to the top

* Expand role summary

* Adjust name of triage role on bpo

* Update Python triage team name

Co-Authored-By: Carol Willing <[email protected]>
Co-Authored-By: Mariatta <[email protected]>
@Mariatta
Copy link
Member Author

Mariatta commented Jul 22, 2019 •
edited
Loading

Closed via python/devguide#506

AA-Turner pushed a commit to AA-Turner/devguide that referenced this issue Jun 17, 2022
@aeros @willingc @Mariatta
python/core-workflow#339: Add "Python triage team" section to "triagi…
d0683f1 
…ng.rst" (python#506)

* Added a "Bug Triager" section to "triaging.rst"

* Moved "Bug Triager" section to the top

* Expand role summary

* Adjust name of triage role on bpo

* Update Python triage team name

Co-Authored-By: Carol Willing <[email protected]>
Co-Authored-By: Mariatta <[email protected]>
kitarefake added a commit to kitarefake/devguide that referenced this issue Jul 15, 2024
@kitarefake @willingc @Mariatta
python/core-workflow#339: Add "Python triage team" section to "triagi…
dd24db0 
…ng.rst" (#506)

* Added a "Bug Triager" section to "triaging.rst"

* Moved "Bug Triager" section to the top

* Expand role summary

* Adjust name of triage role on bpo

* Update Python triage team name

Co-Authored-By: Carol Willing <[email protected]>
Co-Authored-By: Mariatta <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted project: triagers Adding triagers project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mariatta @aeros