It doesn't work in practice, because the skill baseline of an incoming
"contributor" is so wildly variant that any issue that isn't explicitly
a one-liner is automatically not suitable for *some* non-trivial subset
of "new contributor".
The label is also largely used by incoming contributors whose interests
are not necessarily aligned with the project but instead appear to have
other ulterior motives.
- Includes changes to process discussed in development meeting today.
- Describes issue vs discussion axis which wasn't present at the time
the document was originally created.
- Reduces amount of unnecessary text in hopes that the document will
actually be read in full.