community icon indicating copy to clipboard operation
community copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Request for adding a Slack channel to focus on Velero Data Mover.

Open blackpiglet opened this issue 2 years ago • 9 comments

Request to add a Slack channel, which will focus on Velero Data Mover design, developing and future supporting topics.

Signed-off-by: Xun Jiang [email protected]

Which issue(s) this PR fixes:

Fixes #

blackpiglet avatar Jul 26 '22 06:07 blackpiglet

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: blackpiglet / name: Xun Jiang/Bruce Jiang (11d0cf353c19921d7cf99d9fd86458b3cb7e3cfd)

linux-foundation-easycla[bot] avatar Jul 26 '22 06:07 linux-foundation-easycla[bot]

Welcome @blackpiglet!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

k8s-ci-robot avatar Jul 26 '22 06:07 k8s-ci-robot

Hi @blackpiglet. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

k8s-ci-robot avatar Jul 26 '22 06:07 k8s-ci-robot

/ok-to-test

markjacksonfishing avatar Jul 26 '22 09:07 markjacksonfishing

@markyjackson-taulia Thanks. I removed new channel reference in usergroups.yaml.

blackpiglet avatar Jul 26 '22 11:07 blackpiglet

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: blackpiglet, markyjackson-taulia Once this PR has been reviewed and has the lgtm label, please assign idealhack for approval by writing /assign @idealhack in a comment. For more information see:The Kubernetes Code Review Process.

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 Jul 26 '22 11:07 k8s-ci-robot

@jeefy @jdumars Could you please take a look?

blackpiglet avatar Jul 26 '22 23:07 blackpiglet

@blackpiglet review can take a few days. Kindly be patient

markjacksonfishing avatar Jul 27 '22 00:07 markjacksonfishing

Cc @coderanger for review

markjacksonfishing avatar Jul 28 '22 13:07 markjacksonfishing

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 Oct 26 '22 13:10 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 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 rotten

k8s-triage-robot avatar Nov 25 '22 14:11 k8s-triage-robot

/remove-lifecycle stale

markjacksonfishing avatar Nov 25 '22 15:11 markjacksonfishing

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: blackpiglet, markyjackson-taulia, mrbobbytables

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 25 '22 15:11 k8s-ci-robot

/hold cancel

mrbobbytables avatar Nov 25 '22 15:11 mrbobbytables