search

kubernetes-sigs / kustomize

Customization of kubernetes YAML configurations
Apache License 2.0
10.93k stars 2.24k forks source link

Telemetry to guide investment decisions #3941

Open KnVerey opened 3 years ago

KnVerey commented 3 years ago

As maintainers, we do not currently have a way to gauge feature popularity in the community. This makes it more difficult to identify the most impactful work areas and conversely what we should deprecate. The crawler that previously existed to help with this was removed because it was unmaintained: https://github.com/kubernetes-sigs/kustomize/pull/3841. Let's resurrect this in some form.

We could also consider an opt-in mechanism to report feature usage at build time. This has serious privacy implications to consider.

k8s-triage-robot commented 3 years ago

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:

You can:

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

/lifecycle stale

KnVerey commented 3 years ago

Related to #4148

natasha41575 commented 3 years ago

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/kustomize/issues/3941#issuecomment-1024791049): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
natasha41575 commented 2 years ago

/reopen /lifecycle frozen

k8s-triage-robot commented 1 year ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

annasong20 commented 1 year ago

/triage accepted

natasha41575 commented 1 year ago

For whoever is going to pick up this issue, I think there are a few steps here:

  1. Write up a proposal for what metrics we are interested in. For example, how many kustomization files there are on Github, the popularity of different fields, what kinds of custom plugins are people writing etc
  2. Take a look at the existing Github crawler and understand how it works and what kinds of metrics does it provide, are these useful and can the crawler be enhanced to support other metrics we might be interested in
  3. (Optional) Research other possible ways that we might be able to collect metrics and weigh pros and cons of each.
natasha41575 commented 1 year ago

@valaparthvi I am hoping you can work on this! I can't assign you the issue but please assign it to yourself if you can.

valaparthvi commented 1 year ago

/assign valaparthvi

valaparthvi commented 1 year ago

In my previous experience with Telemetry collection, I used Segment to collect the telemetry data, and then pass the data to Woopra to analyze the collected data.

Segment provides a Go library, even though the library is not actively maintained, I have seen that it is functional as is.

Ref:

antoooks commented 1 year ago

@valaparthvi Found an interesting paper about correlation between potential project metrics and project impact. It shows that category of metrics classified under activity metrics shows positive correlation to project impact. With impact measured using number of other projects that uses the project as an upstream or downstream dependency, this is where the crawler is needed.

Image

Image

Image

Source: https://digitalcommons.unomaha.edu/cgi/viewcontent.cgi?article=1061&context=isqafacpub

k8s-triage-robot commented 4 days ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted