kubernetes-sigs/krew-index

Question: Should I re-submit my plugin (pv-migrate)?

utkuozdemir opened this issue · 4 comments

utkuozdemir commented

Hi,

I have submitted the tool I have built about 2y ago: #89

It was rejected as a one-off plugin at that time.

However the tool gained some interest over time, and I am actively maintaining it: https://github.com/utkuozdemir/pv-migrate

There is an open-request to add it to krew: utkuozdemir/pv-migrate#51

I was wondering if I should submit it again, or use a custom index instead?

Thanks.

corneliusweig commented

Hi!

I think we can re-evaluate. When users install this plugin, I think the chances are pretty high that they will uninstall it right after doing the migration. So this plugin really looks one-off. However, I think it's fine to have those plugins in krew, because this is often the first address to look for help.

/cc @ahmetb WDYT?

k8s-triage-robot commented

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 commented

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

ahmetb commented

Sorry for the delay here, yeah feel free to re-submit!

  • 👍1