Update CONTRIBUTING.md based on SIP-13 and add how to use labels

[kristw]

Copy-paste text from SIP-13 with some edits and add this section on how to use labels.

Managing Issues and PRs

To handle issues and PRs that are coming in, committers read issues/PRs and flag them with labels to categorize and help contributors spot where to take actions, as contributors usually have different expertises.

Triaging goals

• For issues: Categorize, screen issues, flag required actions from authors.
• For PRs: Categorize, flag required actions from authors. If PR is ready for review, flag required actions from reviewers.

First, add Category labels (a.k.a. hash labels). Every issue/PR must have one hash label (except spam entry). Labels that begin with # defines issue/PR type:

Label	for Issue	for PR
#bug	Bug report	Bug fix
#code-quality	Describe problem with code, architecture or productivity	Refactor, tests, tooling
#feature	New feature request	New feature implementation
#refine	Propose improvement that does not provide new features and is also not a bug fix nor refactor, such as adjust padding, refine UI style.	Implementation of improvement that does not provide new features and is also not a bug fix nor refactor, such as adjust padding, refine UI style.
#doc	Documentation	Documentation
#question	Troubleshooting: Installation, Running locally, Ask how to do something. Can be changed to #bug later.	N/A
#SIP	Superset Improvement Proposal	N/A
#ASF	Tasks related to Apache Software Foundation policy	Tasks related to Apache Software Foundation policy

Then add other types of labels as appropriate.

• Descriptive labels (a.k.a. dot labels): These labels that begin with . describe the details of the issue/PR, such as .ui, .js, .install, .backend, etc. Each issue/PR can have zero or more dot labels.
• Need labels: These labels have pattern need:xxx, which describe the work required to progress, such as need:rebase, need:update, need:screenshot.
• Risk labels: These labels have pattern risk:xxx, which describe the potential risk on adopting the work, such as risk:db-migration. The intention was to better understand the impact and create awareness for PRs that need more rigorous testing.
• Status labels: These labels describe the status (abandoned, wontfix, cant-reproduce, etc.) Issue/PRs that are rejected or closed without completion should have one or more status labels.
• Version labels: These have the pattern vx.x such as v0.28. Version labels on issues describe the version the bug was reported on. Version labels on PR describe the version that the PR will be released with.

May also update title to reflect the issue/PR content if the author-provided title is not descriptive enough.

If the PR passes CI tests and does not have any need: labels, it is ready for review, add label review and/or design-review.

If an issue/PR has been inactive for >=30 days, it will be closed. If it does not have any status label, add inactive.

@john-bodley @williaster @mistercrunch @graceguo-supercat @michellethomas @betodealmeida @vylc

[codecov-io]

Codecov Report

Merging #6701 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6701   +/-   ##
=======================================
  Coverage   56.19%   56.19%           
=======================================
  Files         520      520           
  Lines       23181    23181           
  Branches     2765     2765           
=======================================
  Hits        13027    13027           
  Misses       9744     9744           
  Partials      410      410

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c65844...6d4e938. Read the comment docs.

[bolkedebruin]

Can you add the asf header to this file (html comment works)

[kristw]

@bolkedebruin Can do, but wonder if the ASF header is also required for documentation (markdown) file?

[bolkedebruin]

Yes. All non Auto generated files part of the artefacts that make up a release need to have those headers.