-
Notifications
You must be signed in to change notification settings - Fork 5
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
Gap analysis for first two rungs of the contributor ladder documentation #30
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@sesheta: 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. |
From the Contrib_X Docs WG:
We need to identify what docs are needed in the Operate First community.
We'll track progress on this here on the Community Handbook board https://github.com/orgs/operate-first/projects/20
ACTION: We need to determine how we're going to do this gap analysis and write that down.
OUTCOME NEEDED: List of doc needs that can be set up as individual issues to be worked on.
All community members are invited to add to the list of known doc needs by commenting here on this issue.
The text was updated successfully, but these errors were encountered: