Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.

Found a broken link at /docs/index.md #45

Closed
AdityaC45 opened this issue May 24, 2021 · 12 comments
Closed

Found a broken link at /docs/index.md #45

AdityaC45 opened this issue May 24, 2021 · 12 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@AdityaC45
Copy link

AdityaC45 commented May 24, 2021

The link is present under the

  • Links section:
    - user guide
    - How to write a COSI driver
    - How to make your application COSI-compatible
  • Advanced section:
    - Protocols
    - Architecture
    - Internals
  • Other:
    - Weekly Meetings
@AdityaC45
Copy link
Author

AdityaC45 commented May 24, 2021

These documents are not yet created, I can work on this issue but will need help on the content that needs to be added to these documents

@guymguym
Copy link

guymguym commented Jul 7, 2021

I think the docs moved here - https://container-object-storage-interface.github.io/
Still worth updating the main README.md because it's just bad that those links are broken...
CC @wlan0

@guymguym
Copy link

guymguym commented Jul 7, 2021

@AdityaC45
Copy link
Author

Hi , I went through that link but still there are no contents added to some of the docs so if we are going to update the documentation in the link shared then it will be good otherwise we again have to change the link

@tparikh
Copy link
Contributor

tparikh commented Jul 12, 2021

Thanks for reporting this issue @AdityaC45. I will take a look into this and update the docs and links.

/assign @tparikh

@AdityaC45
Copy link
Author

If you need any help, I will be glad to help you @tparikh

tparikh added a commit to tparikh/container-object-storage-interface-api that referenced this issue Jul 13, 2021
@tparikh
Copy link
Contributor

tparikh commented Jul 13, 2021

@AdityaC45 I have raised PR to fix the broken link to documentation. Team is working on populating the empty pages on the documentation site.

@AdityaC45
Copy link
Author

Ohkk thanks👍

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 11, 2021
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 10, 2021
@k8s-triage-robot
Copy link

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
Copy link
Contributor

@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.

shanduur pushed a commit to shanduur/container-object-storage-interface-api that referenced this issue Jun 6, 2024
BlaineEXE pushed a commit to BlaineEXE/cosi-api that referenced this issue Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants