Improve communication with contributors on the issue tracker and PRs (Language summit follow up)

[brettcannon]

@iritkatriel

@willingc suggested that open issues should ideally have a clear “next action” indicated on them, so that people know where things stand.

I have done this on other repos and found it extremely useful for everyone involved; being able to tell at a glance based on a label why an issue is still open is really powerful (hence the needs labels on PRs ).

@iritkatriel

The first action on an issue is for it to be understood and acknowledged as valid by one of the core devs.

If that includes triagers, then I think this is a good practice. On GitHub - microsoft/vscode-python: Python extension for Visual Studio Code we used to have a classify label added on all new issues, then we said “thanks” and added the appropriate needs label to signify it had been triaged and to say (we dropped the label as we start from triage-needed and getting the issue assigned is the next step).