cluster-api-provider-ibmcloud icon indicating copy to clipboard operation
cluster-api-provider-ibmcloud copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Docs: identifying scope of improvement

Open Amulyam24 opened this issue 1 year ago • 6 comments

/kind documentation /area provider/ibmcloud

This issue is to collaborate and identify the gaps in the current documentation. https://cluster-api-ibmcloud.sigs.k8s.io/

Amulyam24 avatar Dec 15 '23 05:12 Amulyam24

@Amulyam24 #1402 can we combine both into a single issue. (seems similar)

Prajyot-Parab avatar Dec 15 '23 06:12 Prajyot-Parab

Hi @kishen-v @Niharika0306 @KeerthanaAP @srivastav-abhishek

We are planning to enhance the documentation and make it more understandable and consumable by end users/new comers to the project.

Since you all have recently contributed to or explored this project, I look forward to hearing any feedback on the current documentation. Please share your thoughts accordingly.

Amulyam24 avatar Dec 15 '23 06:12 Amulyam24

cc @Shilpa-Gokul @dharaneeshvrd

Amulyam24 avatar Apr 05 '24 05:04 Amulyam24

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jul 04 '24 05:07 k8s-triage-robot

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Aug 03 '24 05:08 k8s-triage-robot

/remove-lifecycle rotten

mkumatag avatar Aug 06 '24 05:08 mkumatag