operate-first / community

GNU General Public License v3.0
11 stars 6 forks source link

Create OWNERS #183

Closed msdisme closed 1 year ago

msdisme commented 2 years ago

Initially added Owners file for making changes to the documentation including Raja Sambasivan and Michael Daitzman. Will discuss reviewers at next SIG meeting

sesheta commented 2 years ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign schwesig after the PR has been reviewed. You can assign the PR to them by writing /assign @schwesig in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/operate-first/community/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
sesheta commented 2 years ago

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as [members]() of the operate-first org. You can then trigger verification by writing /verify-owners in a comment.

msdisme commented 2 years ago

@RS1999ent I would like to add you as a reviewer for the telemetry working group pages in the operate first repositories. Either you can follow the instructions here: https://github.com/operate-first/community/pull/183 or ping @msdisme and I will go ahead and do the PR to add you.

schwesig commented 2 years ago

/kind feature /kind governance /sig operations /kind onboarding

schwesig commented 2 years ago

/area contributor /area user

sesheta commented 2 years ago

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 commented 2 years ago

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 commented 1 year ago

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

/close

sesheta commented 1 year ago

@sesheta: Closed this PR.

In response to [this](https://github.com/operate-first/community/pull/183#issuecomment-1351495852): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.