Closed tuminoid closed 5 months ago
/good-first-issue /kind documentation /triage accepted /help
@tuminoid: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
@tuminoid thanks for this! Let's keep this open for our outreachy intern if possible, they should start next week
@elfosardo @tuminoid I would like to take this
/assign @SafeEHA
@elfosardo: GitHub didn't allow me to assign the following users: SafeEHA.
Note that only metal3-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
@tuminoid can we please assign this to @SafeEHA ? thanks!
@tuminoid can we please assign this to @SafeEHA ? thanks!
In GitHub, you can’t assign non-members or non-contributors that have not previously commented in an issue/PR. So please @SafeEHA comment here and we can assign this to you.
Hello @elfosardo @tuminoid I would begin working on this as soon as possible Thanks
Hello @elfosardo @tuminoid I would begin working on this as soon as possible Thanks
Assigned!
I am also willing to work on the issue @tuminoid @elfosardo
cc: https://github.com/metal3-io/metal3-docs/issues/328#issuecomment-1531843191
Hello @dhellmann Please can you give me the correct link for the hyperlink here on this page
It looks like that template is trying to link to itself and I either typoed "design" as "designs" or things were moved later. So I think if you change https://github.com/metal3-io/metal3-docs/blob/main/designs/_template.md
to https://github.com/metal3-io/metal3-docs/blob/main/design/_template.md
it will work.
Hello @dhellmann Please can you give me the correct link for operator-sdk 1.0 migration guide, on this page AccessDetails interface on this page Machine on this page GitHub Search Query under New issue triage on this page And CRs on this page
Hi @kashifest Please can you help provide the correct links to metal3 spec for bare-metal on this page Remediation on this page
https://github.com/metal3-io/baremetal-operator/blob/main/deploy/crds/metal3.io_baremetalhosts_crd.yaml on this page
re-inspection API proposal and CAPI MachineHealthCheck on this page
Hello @fmuyassarov @Hellcatlk @dhellmann @Arvinderpal @kashifest Please I need your help with these broken links
Hello @fmuyassarov @Hellcatlk @dhellmann @Arvinderpal @kashifest Please I need your help with these broken links
I will provide the links soon.
Hello Everyone So far, I have made a partial fix for some of the broken links and created #333
It has been a month since last update. How is this progressing?
Hi @kashifest Please can you help provide the correct links to metal3 spec for bare-metal on this page Remediation on this page
https://github.com/metal3-io/baremetal-operator/blob/main/deploy/crds/metal3.io_baremetalhosts_crd.yaml on this page
re-inspection API proposal and CAPI MachineHealthCheck on this page
the correct link for the CRD is https://github.com/metal3-io/baremetal-operator/blob/main/config/crd/bases/metal3.io_baremetalhosts.yaml , please ping the persons who have written the proposals originally if any more updates are needed
page
CAPI machine healthcheck - https://cluster-api.sigs.k8s.io/developer/architecture/controllers/machine-health-check.html
Hi @kashifest Please can you help provide the correct links to metal3 spec for bare-metal on this page Remediation on this page
https://github.com/metal3-io/baremetal-operator/blob/main/deploy/crds/metal3.io_baremetalhosts_crd.yaml on this page
re-inspection API proposal and CAPI MachineHealthCheck on this page
Remediation proposal- https://github.com/metal3-io/metal3-docs/blob/main/design/cluster-api-provider-metal3/capm3-remediation-controller-proposal.md
Thank you @kashifest I would effect these changes and create a PR
HI @tuminoid I'm making progress on it, once I'm able to get all the correct links PRs would be created respectively
@kashifest I also forgot to add that I need the correct link for https://github.com/metal3-io/baremetal-operator/blob/main/ironic-deployment/ironic/ironic.yaml under Design Details on https://github.com/metal3-io/metal3-docs/blob/main/design/ironic-debuggability-improvement.md page.
HI @tuminoid I'm making progress on it, once I'm able to get all the correct links PRs would be created respectively
I'd like to see a bit more proactive work on it, by trying to identify the correct URL to best of your ability, and creating PR with those, and then address the feedback if the reviewer's say you got the link wrong.
@kashifest I also forgot to add that I need the correct link for https://github.com/metal3-io/baremetal-operator/blob/main/ironic-deployment/ironic/ironic.yaml under Design Details on https://github.com/metal3-io/metal3-docs/blob/main/design/ironic-debuggability-improvement.md page.
here you go, https://github.com/metal3-io/baremetal-operator/blob/dabe5e14bafa00db6ccb37f1169c74ee3dac4425/ironic-deployment/base/ironic.yaml, note that I have given the perma link here. Please obtain the permalink of the links I have provided earlier so that the links dont ront even if the file changes in future.
Hello, please I need to have my access to the repo updated I can't seem to push updates
@tuminoid I apologize for how long this has taken, I am still quite new here and I've been trying to get familiar with everything I corrected the links for the first 2 out of the 3 broken links in the first PR I created, the others have been a bit more complicated to decipher but i assure you I'm doing my best
Hello, please I need to have my access to the repo updated I can't seem to push updates
You need to push the branches to your fork, and then create PR. Directly pushing is not allowed for anyone.
Hello, So far, I have created PRs #336 #333 fixing the broken links that had wrong paths or some other issue with some help and within how much I know currently, I have these left
Please I need help getting the correct links for these as would really like to close out this issue as soon as possible with your help
@huutomerkki if you're interested, you could work with @SafeEHA to get all of the links fixed. It has been pending quite a while.
hello everyone, I'm Nicholas a software developer from Nigeria who is new to open source. I was going through the metal3 user-guide and I came across a broken link, looking at the repo I've seen that this is a good first issue and I'd be more than willing to help, could you kindly bring me up to speed on what to do and how to go about it? thank you and hope to hear from you.
hello everyone, I'm Nicholas a software developer from Nigeria who is new to open source. I was going through the metal3 user-guide and I came across a broken link, looking at the repo I've seen that this is a good first issue and I'd be more than willing to help, could you kindly bring me up to speed on what to do and how to go about it? thank you and hope to hear from you.
Hello @Gutopro. To contribute to Metal3, we follow Github PR workflow described here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request Also see https://github.com/metal3-io/metal3-docs/blob/main/CONTRIBUTING.md
If you encounter a broken link (or fix a broken link identified in this link), you'd need to find a working link and then submit a PR to replace the broken link with a working one. It will then be reviewed by project members and eventually merged, if it fixed the issue.
thanks @tuminoid I'll start working on it immediately.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Adding some suggestions and hints inline
Hello, So far, I have created PRs #336 #333 fixing the broken links that had wrong paths or some other issue with some help and within how much I know currently, I have these left
* [operator-sdk 1.0 migration guide](https://sdk.operatorframework.io/docs/building-operators/golang/project_migration_guide/), on [this](https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/kubebuilder-migration.md) page
I think we should link here
* [Machine](https://kubernetes-sigs.github.io/cluster-api/common_code/machine_controller.html) on [this](https://github.com/metal3-io/metal3-docs/blob/main/design/nodes-machines-and-hosts.md) page
Find some kind of definition or API reference here and link to it.
* [GitHub Search Query](https://github.com/issues?utf8=%E2%9C%93&q=archived%3Afalse+user%3Ametal3-io+no%3Alabel+is%3Aissue+sort%3Acreated-asc+is%3Aopen) under New issue triage on [this](https://github.com/metal3-io/metal3-docs/blob/main/processes/triage.md) page
Looks to me like this link is working.
* [CRs](https://github.com/metal3-io/metal3-dev-env/tree/master/crs) on this [page](https://github.com/metal3-io/metal3-docs/blob/main/crs_reference.md)
Check when this page in the docs was first written and go back in history to the same point in metal3-dev-env. Check what the content was back then and either link to that point in time or find some new material that matches.
* [Link](https://www.ericsson.com/en/portfolio/cloud-software--services/cloud-infrastructure/cloud-container-distribution) on this [page](https://github.com/metal3-io/metal3-docs/blob/main/ADOPTERS.md)
The page no longer exists. No change needed.
* [Addressed](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/0000-20170814-bounding-self-labeling-kubelets.md) on this [page](https://github.com/metal3-io/metal3-docs/blob/main/design/sync-labels-bmh-to-node.md)
It has moved here
/remove-lifecycle stale
@SafeEHA do you want to work on this still? If not, I'm going to bring it to our contrib-fest session at KubeCon 🙂
Yeah with your suggestions I should make some progress, I'll have updates soon
So far I fixed 3 out of the 6 broken links I listed earlier on this PR #387 thanks to pointers from @lentzi90 The other 3 however are still pending... This - GitHub Search Query under New issue triage and this - CRs on this page
Also, for this - Link on this page, would we take it out completely or replace with some other resource since it no longer exists?
This - GitHub Search Query under New issue triage and this - CRs on this page
The GitHub Search Query works as it should but we may have to configure the link checker to understand it. Ignore it for now.
As mentioned, check the history for the page. When was it created? Then go to metal3-dev-env commits and select commits from around the same time. Pick a commit and click "Browse the repository at this time" (< >
). Hopefully you should now see the crs
folder.
Check what the content is. If we have something similar somewhere else, we can link to that. Otherwise just link to the the CRs at this commit.
Also, for this - Link on this page, would we take it out completely or replace with some other resource since it no longer exists?
It is already removed. You don't have to do anything.
This - GitHub Search Query under New issue triage and this - CRs on this page
The GitHub Search Query works as it should but we may have to configure the link checker to understand it. Ignore it for now.
As mentioned, check the history for the page. When was it created? Then go to metal3-dev-env commits and select commits from around the same time. Pick a commit and click "Browse the repository at this time" (
< >
). Hopefully you should now see thecrs
folder.Check what the content is. If we have something similar somewhere else, we can link to that. Otherwise just link to the the CRs at this commit.
Also, for this - Link on this page, would we take it out completely or replace with some other resource since it no longer exists?
It is already removed. You don't have to do anything.
Apologies for responding late, had a busy week
So, i followed your instructions and found this
I remember going through the commits last time but maybe cause I was looking for a file CRs I didn't find anything, but the above link points to a crs
sub-dir that leads to v1apha2
and v1alpha3
with a bunch of yaml files , I looked through metal-docs repo and didn't find anything like it. I am not certain of the specific file from the list, please help point me to the right one
cc: @lentzi90
You can link directly to this: https://github.com/metal3-io/metal3-dev-env/tree/b5a53ecf9576c6deab81f692733782d4c5e8091a/crs That is what they meant to link to originally.
I've made the necessary changes to the PR, kindly review and I'll await your comments and hopefully we can go ahead to merge the broken link checker on #322 like @tuminoid mentioned in the beginning
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
I'm going to split this issue up, with the fresh data, as this is too massive to anyone to work on apparently. /assign
This is the current list of broken links in this repository that need to be fixed.
After these are fixed, we can merge https://github.com/metal3-io/metal3-docs/pull/322 to add broken link checker to keep repository clean from broken links.