Triage guide
Discussed on the dev call yesterday.

cc @pandas-dev/pandas-core. Any sections I'm missing? Any statements you disagree with?

xref https://github.com/pandas-dev/pandas-governance/issues/11 (writing down a policy for triaging once we have one).
Awesome - great to have this info documented! @TomAugspurger  @alimcmaster1 a couple questions, since you're our only triager so far:

1. Can you close PRs, in additional to issues?
2. Can you push to PRs that aren't your own? I see a "Add more commits by pushing to ..." just above the CI checks. > @alimcmaster1 a couple questions, since you're our only triager so far:
> 
> 1. Can you close PRs, in additional to issues?
> 2. Can you push to PRs that aren't your own? I see a "Add more commits by pushing to ..." just above the CI checks.

1) Yes triage access allows you to close PRs
2) No I cannot push to PRs that aren't my own.

If helpful the full permissions matrix is here:
https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization

Thanks! Thanks. Hopefully addressed everything in 5772227e187ff0403cb432f85884b955a3495ae9
 thanks @TomAugspurger very nice! One thing I have noticed:

The triage team gives me access to cancel/restart build jobs on Travis but not on Azure. 

I can add this info if we think its worth it. (But I know we are hoping to migrate off travis soon)

Anyway just thought I would highlight