# Proposal: Create "Bug Triage" team on GitHub **URL:** https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992 **Category:** Core Workflow **Created:** [March 6, 2019, 8:27pm UTC](https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992 "2019-03-06T20:27:27Z") **Posts on this page:** 1 **Showing post:** 47
### Author: ![aeros](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/aeros/32/4140_2.png) [@aeros](https://discuss.python.org/u/aeros) #### Post date: [July 18, 2019, 5:36am UTC](https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992/47 "2019-07-18T05:36:57Z")
> [@Mariatta](#): > > I personally think any labels except the automerge lab should be fine for triagers to add. Even the need backports are fine too. Anyone else think differently? Based on my understanding of the [devguide section](https://devguide.python.org/committing/?highlight=backport#backporting-changes-to-an-older-version), the backport labels cause `miss-islington` to attempt to perform the backport automatically after the PR is merged. Unless that functionality is changed, I think those labels should probably be reserved to the core devs. Here’s the list of cpython labels, omitting awaiting, CLA, automerge, and backport: `DO-NOT-MERGE`, `expert-asyncio`, `invalid`, `OS-mac`, `OS-windows`, `skip issue`, `skip news`, `sprint`, `type-bugfix`, `type-documentation`, `type-enhancement`, `type-performance`, `type-security`, `type-tests` From that list, the ones I’m uncertain about for triagers would be `DO-NOT-MERGE`, `invalid`, (due to them coming across strongly) and potentially `type-security`. The distinction between a PR being `type-bugfix` vs `type-security` might not be immediately clear. As an example, I initially had assumed that [this PR](https://github.com/python/cpython/pull/14777) would have been considered a security issue instead of a bugfix due to it being able to crash the interpreter with a segfault. --- _[View the full topic](https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992)._