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

Add csi-misc team to tag all developers #390

Merged
merged 1 commit into from
Feb 12, 2019

Conversation

jsafrane
Copy link
Member

For CSI development we need to tag all developers in PRs and issues. IMO, we don't need separate csi-pr-reviews and csi-bugs teams, everybody does everything, @csi-misc in any kubernetes-csi repo should be enough.

Do we need the same team in kubernetes/ repos?

/hold
for discussion in sig-storage first.

@chakri-nelluri @davidz627 @gnufied @lpabon @pohly @rootfs @sbezverk @vladimirvivien @xing-yang @saad-ali @childsb , PTAL. Feel free to suggest other members or remove yourself.

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 21, 2019
@@ -327,3 +327,20 @@ teams:
- lpabon
- saad-ali
privacy: closed
csi-misc:
description: Miscellaneous Discussions for Kubernetes CSI Work Group
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

working group?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

- pohly
- rootfs
- sbezverk
- vladimirvivien
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add me? xing-yang

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried:

    config_test.go:248: The following members of team csi-misc are not Kubernetes CSI org members: xing-yang

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, csi-org, I can fix that easily here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I need to apply for kubernetes-csi org membership first? I should do that anyway.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xing-yang -- You'll need to apply for membership for the kubernetes-csi org before @jsafrane can add you to this GitHub team.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My membership application is approved and I'm added to kubernetes-csi org now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for sorting that! :)

Copy link
Member

@justaugustus justaugustus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason to not just use csi as the team name?

@jsafrane jsafrane force-pushed the csi-wg branch 2 times, most recently from 326b546 to 1d88e26 Compare January 21, 2019 16:09
Copy link
Member

@justaugustus justaugustus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xing-yang needs to file for membership in a separate issue. Please remove her from the PR in the meantime.
/hold

@xing-yang
Copy link
Contributor

@justaugustus Will do. Thanks.

@xing-yang
Copy link
Contributor

@justaugustus I submitted an issue to apply for membership: #392

@mrbobbytables
Copy link
Member

#392 was closed yesterday. I think the only follow-up question from @justaugustus regarding possibly just changing the name to csi?

@jsafrane
Copy link
Member Author

On yesterday's CSI WG meeting we found @kubernetes-csi/csi-misc good enough. IMO, it gives us possibility to add /csi-pr-reviews and /csi-bugs later. @kubernetes-csi/csi looks odd.

/hold cancel
(discussion in sig-storage happened and Xing is a member)

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 24, 2019
@justaugustus
Copy link
Member

SGTM
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 24, 2019
@@ -28,6 +28,7 @@ members:
- saad-ali
- sbezverk
- vladimirvivien
- xing-yang
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase away this line please?

@cblecker
Copy link
Member

/lgtm cancel

Rebase requested.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2019
For CSI development we need to tag all developers in PRs and issues. IMO, we
don't need separate csi-pr-reviews and csi-bugs teams, everybody does
everything.
@jsafrane
Copy link
Member Author

jsafrane commented Feb 4, 2019

rebased

@justaugustus
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 4, 2019
@@ -330,3 +330,21 @@ teams:
- lpabon
- saad-ali
privacy: closed
csi-misc:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can we have this in the alphabetical order? all team names are currently listed alphabetically

(i'll add a test for this later)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 12, 2019
Copy link
Member

@nikhita nikhita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

Thanks @jsafrane!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 12, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, justaugustus, nikhita

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 12, 2019
@k8s-ci-robot k8s-ci-robot merged commit ac24206 into kubernetes:master Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants