<commit_before># Triage Process and Github Labels for Angular 2

This document describes how the Angular team uses labels and milestones 
to triage issues on github. The basic idea of the new process is that 
caretaker only assigns a component and type (bug, feature) label. The 
owner of the component than is in full control of how the issues should 
be triaged further.

Once this process is implemented and in use, we will revisit it to see 
if further labeling is needed.

## Components

A caretaker should be able to determine which component the issue 
belongs to. The components have a clear piece of source code associated
with it.

* `comp: animations`: `@matsko`
* `comp: benchpress`: `@tbosch`
* `comp: build & ci`: `@IgorMinar` -- All build and CI scripts 
* `comp: common`: `@mhevery`  -- This includes core components / pipes.
* `comp: core & compiler`: `@tbosch` -- Because core and compiler are very 
  intertwined, we will be treating them as one.
* `comp: forms`: `@kara`
* `comp: http`: `@jeffbcross`
* `comp: i18n`: `@vicb`
* `comp: metadata-extractor`: `@chuckjaz`
* `comp: router`: `@vsavkin`
* `comp: testing`: `@juliemr`
* `comp: upgrade`: `@mhevery`
* `comp: web-worker`: `@vicb`
* `comp: zones`: `@mhevery`

There are few components which are cross-cutting. They don't have
a clear location in the source tree. We will treat them as a component
even thought no specific source tree is associated with them.

* `comp: documentation`: `@naomiblack`
* `comp: packaging`: `@IgorMinar`
* `comp: performance`: `@tbosch`
* `comp: security`: `@IgorMinar`


## Type
What kind of problem is this?

* `type: RFC / discussion / question`
* `type: bug`
* `type: chore`
* `type: feature`
* `type: performance`
* `type: refactor`

## Caretaker Triage Process

It is the caretaker's responsibility to assign `comp:  *` and `type: *`
to each new issue as they come in. The reason why we limit the 
responsibility of the caretaker to these two labels is that it is 
unlikely that without domain knowledge the caretaker could add any 
additional labels of value.<commit_msg>doc(triage): correct existing incorrect info<commit_after># Triage Process and Github Labels for Angular 2

This document describes how the Angular team uses labels and milestones 
to triage issues on github. The basic idea of the process is that
caretaker only assigns a component and type (bug, feature) label. The 
owner of the component than is in full control of how the issues should 
be triaged further.

Once this process is implemented and in use, we will revisit it to see 
if further labeling is needed.

## Components

A caretaker should be able to determine which component the issue 
belongs to. The components have a clear piece of source code associated
with it.

* `comp: animations`: `@matsko`
* `comp: benchpress`: `@tbosch`
* `comp: build & ci`: `@IgorMinar` -- All build and CI scripts 
* `comp: common`: `@mhevery`  -- This includes core components / pipes.
* `comp: core & compiler`: `@tbosch` -- Because core and compiler are very 
  intertwined, we will be treating them as one.
* `comp: forms`: `@kara`
* `comp: http`: `@jeffbcross`
* `comp: i18n`: `@vicb`
* `comp: metadata-extractor`: `@chuckjaz`
* `comp: router`: `@vsavkin`
* `comp: testing`: `@juliemr`
* `comp: upgrade`: `@mhevery`
* `comp: web-worker`: `@vicb`
* `comp: zones`: `@mhevery`

There are few components which are cross-cutting. They don't have
a clear location in the source tree. We will treat them as a component
even thought no specific source tree is associated with them.

* `comp: docs`: `@naomiblack`
* `comp: packaging`: `@IgorMinar`
* `comp: performance`: `@tbosch`
* `comp: security`: `@IgorMinar`


## Type
What kind of problem is this?

* `type: RFC / discussion / question`
* `type: bug`
* `type: chore`
* `type: feature`
* `type: performance`
* `type: refactor`

## Caretaker Triage Process

It is the caretaker's responsibility to assign `comp:  *` to each new
issue as they come in. The reason why we limit the responsibility of the
caretaker to these one label is that it is likely that without domain
knowledge the caretaker could mislabel issues or lack knowledge of
duplicate issues.
{'fraction_non_alphanumeric': 0.10550239234449761, 'fraction_numerical': 0.0014354066985645933, 'mean_word_length': 4.465359477124183, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3785406', 'n_tokens_mistral': 1359, 'n_tokens_neox': 1273, 'n_words': 592}