Skip to content
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

Closed
stefwrite opened this issue Mar 15, 2022 · 6 comments
Closed
Labels
area/contributor Indicates an issue/PR is related to a project platform contributor. kind/handbook Indicates an issue/PR is related to a handbook. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@stefwrite
Copy link

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.

@stefwrite stefwrite added area/contributor Indicates an issue/PR is related to a project platform contributor. kind/handbook Indicates an issue/PR is related to a handbook. labels Mar 15, 2022
@quaid quaid added this to Content in progress in Community Handbook Mar 15, 2022
@sesheta
Copy link
Member

sesheta commented Jun 13, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2022
@sesheta
Copy link
Member

sesheta commented Jul 13, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 13, 2022
@quaid quaid removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 21, 2022
@sesheta
Copy link
Member

sesheta commented Oct 19, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2022
@sesheta
Copy link
Member

sesheta commented Nov 18, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 18, 2022
@sesheta
Copy link
Member

sesheta commented Dec 18, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Dec 18, 2022
Community Handbook automation moved this from Content in progress to Done Dec 18, 2022
@sesheta
Copy link
Member

sesheta commented Dec 18, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/contributor Indicates an issue/PR is related to a project platform contributor. kind/handbook Indicates an issue/PR is related to a handbook. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
Development

No branches or pull requests

3 participants