Set labelling strategy

[samccann]

In ansible/ansible, we had some built-in labels and a bot that did helpful things.

Let's use this issue to discuss what we want here in this docs repo that might be similar.
What comes to mind:
needs_info - I added this label but in ansible/ansible, anything with needs_info would auto-send a reminder I think maybe once a month for two or three months? and if there was no response, would auto-close.
triage - new issues automatically got labeled triage so we can see it, determine it's scope, add it to the project board etc.

There's likely more but those two come immediately to mind this morning :-)

[samccann]

@gotmax23 @felixfontein - do we want a 'tooling' label? For things like this and the autoresponder etc? I see we have a docs build label but some of these repo setup things don't apply there, but also aren't documentation issues..

[samccann]

some other issues that aren't documentation:

• Update environment variables page to also include plugins #144 - -relates to autogenerated page (thus needs coding to fix)
• Pdf/Epub/Offline documentation is missing #109 - request for pdf/epub (that may finally be solvable via core docs going to readthedocs)
• Sidebar doesn't have links updated to versions other than latest when selecting another version #94 - problem with the 404 page sphinx extension we use.

etc etc. Just thinking if we can identify issues that require coding skills of some sort, it would make them easier to find by ...coders :-)

[samccann]

Also having a new contributor label on new PRs helpful. We could use it wrt #69 (a potential autoresponder to new contributors). I've also used it in the past to welcome someone to Ansible on their first contribution.