Update wiki - outdated information across wiki

[wideocean]

I noticed that the wiki is quite outdated on several sub-pages.

Examples:

• Installation: proposed version to use is still version 10
• Code Examples: all links there lead to 404

Suggestion: Check the wiki and replace outdated information.

[H1manshu-Soni]

Hey @wideocean I am a beginner trying to fnid some issues to fix and I think this wil be a good issue to start with, can you point me to the website and the resources required. -Himanshu

[wideocean]

@H1manshu-Soni The wiki can be found here: https://github.com/kubernetes-client/java/wiki

Code examples are already fixed it seems. Installation sub page is still outdated (minor issue): https://github.com/kubernetes-client/java/wiki/1.-Installation

If you think you can fix and update the page, go for it.

[H1manshu-Soni]

Hey @wideocean I am not sure if I understand you correctly but what exactly do you want to me to fix this might be a dumb question but I just dont know what to do there. I am sorry for the trouble.

[wideocean]

@H1manshu-Soni The installation sub page states version 10 while the latest published release is version 14.

[H1manshu-Soni]

Hey @wideocean I have fixed the version problem is there anything else you want me to do?

[harshitasao]

Hi @yue9944882, As indicated in comment I've made the required changes to my forked wiki. If that appears to be correct, please merge it, and if any changes are needed, please let me know. Link to my forked wiki - https://github.com/harshitasao/java/wiki/1.-Installation Thank you.

[yue9944882]

thanks for reporting the outdated content in wiki, i just refreshed them. leaving this thread open for a few days in case i missed anything.

[iamshakkib]

Hi I too want to contribute in open source using Java, Previously have some intern exp. how can I do it ?

[k8s-triage-robot]

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]

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

[brendandburns]

@iamshakkib apologies for the (very) delayed response, but if you are still looking to contribute, there are several issues labelled good-first-issue

https://github.com/kubernetes-client/java/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.