Remove WeaveWorks URLs from Kubernetes Documentation Website

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.49k stars 14.41k forks source link

Remove WeaveWorks URLs from Kubernetes Documentation Website #45482

Open seifrajhi opened 7 months ago

seifrajhi commented 7 months ago

As per the announcement by Richardson Alexis on LinkedIn (link), WeaveWorks is winding down its operations. Consequently, many URLs from WeaveWorks in the Kubernetes documentation are now obsolete, leading to a "Site Not Found" error message.

For instance here

Proposal:

Identify all WeaveWorks URLs in the documentation.
Remove or replace these URLs with alternative resources to ensure the documentation remains accurate and useful.
Consider updating documentation guidelines to periodically review and update third-party URLs.

This action will ensure users aren't directed to broken or inaccessible resources.

AmarNathChary commented 7 months ago

/language en /sig docs

stmcginnis commented 7 months ago

I don't think we want to remove this just because the company originally behind it is out of business. It is an open source project that at least appears to be living on.

seifrajhi commented 7 months ago

Hello @stmcginnis , Yes, as I proposed in my issue we can Remove or replace these URLs with alternative resources to ensure the documentation remains accurate and useful.

Because their website (https://www.weave.works/) is officially decommissioned and not accessible anymore.

a-mccarthy commented 7 months ago

So this seems to be coming up a bunch of other issues as well, https://github.com/kubernetes/website/issues/45201 and a few other issues/prs. So i think its worth talking about to get on the same page about what to do about the links.

Consider updating documentation guidelines to periodically review and update third-party URLs.

I'm not sure if there was ever a conversation around this when we put together the third party content policy. I think we generally rely on the community to help keep the links updated, as we might not have the depth of knowledge or dedicated resources to always staff doing this research with in the SIG.

k8s-triage-robot commented 4 months ago

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 commented 3 months ago

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: