Updated Guidelines for Help-Wanted Issues

[Benjamin Elder]

Hi all, TLDR: After discussions in SIG Contributor Experience the guidelines for help-wanted issues have been updated to remove the "low barrier to entry" requirement.

This improves the distinction between "good first issue" and "help-wanted" and better aligns with other open source projects.

Help-Wanted issues still require:

• Clear Task The task is agreed upon and does not require further discussions in the community. Call out if that area of code is untested and requires new fixtures. Consensus should exist for the high-level approach.

API and CLI behavior should be decided and included in the OP issue, for example: “The new command syntax is svcat unbind NAME [--orphan] [--timeout 5m]”, with expected validations called out.

• Goldilocks priority The priority should not be so high that a core contributor should do it, but not too low that it isn’t useful enough for a core contributor to spend time reviewing it, answering questions, helping get it into a release, etc.

• Up-To-Date Often these issues become obsolete and have already been completed, are no longer desired, no longer make sense, or have changed priority or difficulty.

If you have a moment, consider sweeping projects you maintain to mark candidate issues, help-wanted issues should be more clearly in scope for growing return contributors versus new contributors (good first issue).

For full details, see:
https://www.kubernetes.dev/docs/guide/help-wanted/ 

https://github.com/kubernetes/community/pull/8447

https://github.com/kubernetes/community/issues/8444

Sig Contributor Experience Meeting Notes: https://docs.google.com/document/d/1CBz8qV_mD6rbDmTsMuosTOQGRXGhN3d8UrcULUI6Vkw/edit?ouid=106034105221670982758&usp=docs_home&ths=true

Thanks,
Ben