-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link to developer guide from the contributor guide #1632
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-help /cc @ryanj |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@castrojo I'm trying to understand what this issue better -- does this mean just adding a link to the developer guide from the contributor guide or hashing out some more things? If its the former, we could add back the good-first-issue label. The developer guide has also gone through a major overhaul (thanks to @eduartua!). |
@nikhita - pretty sure it's just a link to the main devrel readme when its ready |
@parispittman Thanks. Do you think we can link it even today? What does ready mean here? :) |
I think this is done? This section links to the root of devel - https://github.com/kubernetes/community/tree/master/contributors/guide#setting-up-your-development-environment We could potentially be more explicit about linking to devel -- like linking to the readme directly the root makes it easier to browse. ¯\(ツ)/¯ |
SGTM. Let's close the issue once this is done. If anything else is needed, let's create follow-up issues with more details. Adding the good first issue label back. /good-first-issue For anyone who takes this up -- the link here should point to https://github.com/kubernetes/community/blob/master/contributors/devel/README.md#setting-up-your-dev-environment-coding-and-debugging instead. |
@nikhita: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
/remove-lifecycle stale |
/kind documentation |
/priority important-longterm |
/milestone May |
And I have signed the CLA, I just didnt setup my email smh |
/resolved :) after a year long sweep into the darkest corner |
/close |
@thecrudge: You can't close an active issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
@thecrudge thank you! /close |
@idealhack: Closing this issue. In response to this:
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. |
We need to sync with RyanJ or someone else working on the developer guide and at least link to whatever they have so far as a starting point
/sig contributor-experience
/area contributor-guide
The text was updated successfully, but these errors were encountered: