Add contributing.md for SIG Instrumentation for subprojects

[ehashman]

Describe the issue

Generally the overall contributing.md works for SIG Instrumentation, but it doesn't tell folks how to get involved in our various subprojects.

@kubernetes/sig-instrumentation-members can subproject owners please take this on?

/cc @serathius
for metrics-server
/cc @fpetkovski @dgrisonnet
for KSM
/cc @pohly
for klog/logging

/sig instrumentation

[serathius]

How this should differ than already existing CONTRIBUTING.md within subprojects? (for example https://github.com/kubernetes-sigs/metrics-server/blob/master/CONTRIBUTING.md)

[dashpole]

Should we just make sure we link to the existing contributing docs?

[serathius]

How this is different to just listing subprojects and saying to check their README.md/CONTRIBUTING.md file? In the end this will result in just becoming another list of SIGs project, which is redundant. I think it would make more sense to just encourage users to check out one of the subprojects (list is available in sig-instumentation/README.md).

Another approach to this problem that could be solved on the SIG level would be agreeing on contents of CONTRIBUTING.md in each subproject. We could have a list of required sections to maintain same level of quality. For example, they should all include:

• Up to date Kubernetes contributing guidelines
• List of tools required for development
• How to run tests

[ehashman]

@serathius right now the subprojects list just links to a bunch of OWNERS files. It's not a good starting point for newcomers to get started with contributing to subprojects. Many won't even know what an OWNERS file is.

It would be better for us to list areas seeking help and link directly to their contributor guides, which are not covered by the top-level Kubernetes one.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.