community icon indicating copy to clipboard operation
community copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

structured logging WG: update meeting time

Open pohly opened this issue 3 years ago • 3 comments

This is the time in the meeting doc and what we currently use in practice.

pohly avatar May 04 '22 14:05 pohly

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pohly To complete the pull request process, please assign tpepper after the PR has been reviewed. You can assign the PR to them by writing /assign @tpepper 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:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar May 04 '22 14:05 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Aug 07 '22 07:08 k8s-triage-robot

/remove-lifecycle stale

pohly avatar Aug 08 '22 07:08 pohly

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Nov 06 '22 07:11 k8s-triage-robot

/remove-lifecycle stale

pohly avatar Nov 07 '22 06:11 pohly

gentle ping @parispittman thanks!

shivanshuraj1333 avatar Nov 10 '22 14:11 shivanshuraj1333

/lgtm /assign @parispittman

shivanshuraj1333 avatar Nov 10 '22 14:11 shivanshuraj1333

/lgtm /approve

parispittman avatar Nov 10 '22 15:11 parispittman

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: parispittman, pohly

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar Nov 10 '22 15:11 k8s-ci-robot