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

renaming k8s-infra-team to wg-k8s-infra #166

Closed
spiffxp opened this issue Jan 16, 2019 · 11 comments
Closed

renaming k8s-infra-team to wg-k8s-infra #166

spiffxp opened this issue Jan 16, 2019 · 11 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@spiffxp
Copy link
Member

spiffxp commented Jan 16, 2019

Now that our charter has landed (ref: kubernetes/community#2830), and we're still in early days, let's rename assets from k8s-infra-team to wg-k8s-infra:

slack channel

  • #k8s-infra-team - > wg-k8s-infra

This is a transparent rename, need to ask #slack-admins

public google group

This is a hard break, suggest e-mailing list to let them know of the move, and then doing the move.

k/community docs

update references in here once the slack channel and public google group is renamed

admin groups

@thockin we only have a few references in the extant GCP project. If you create new google groups for k8s-infra-cluster-admins@googlegroups.com and k8s-infra-dns-admins@googlegroups.com I can replicate the config then remove the old groups. We have some docs to update too in DNS

Honestly I'm torn on this, part of me says do it so everything is the same. Part of me says k8s-infra is good enough since there are questions of whether this stays as a wg or may one day become a sig (or a committee, or who knows)

/assign @spiffxp
I'm willing to take on all but admin groups

/assign @dims @thockin
WDYT about the admin groups?

/wg k8s-infra
/kind cleanup

@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jan 16, 2019
@cblecker
Copy link
Member

I'd like to consider if we're moving anyways, to use our gsuite instead of public google groups. The auditing of permissions, the administrator recovery, etc are way stronger there as opposed to the public groups (especially with these really high level trusted permissions).

@dims
Copy link
Member

dims commented Jan 16, 2019

@cblecker i am cool with waiting for/using the gsuite.
@spiffxp looks good other than that!

@cblecker
Copy link
Member

It's my understanding that groups don't cost anything, so we'd just need to request of one of the steering committee admin account holders to set up the groups themselves for us.

@spiffxp
Copy link
Member Author

spiffxp commented Jan 17, 2019

I'm fine with the idea of holding on our groups for ACLs etc, to see if gsuite makes more sense

But I would still like to rename our public discussion group / mailing list

@thockin
Copy link
Member

thockin commented Jan 22, 2019

In general, the feeling was NOT to use the gsuite account very much. Because this will be potentially a lot of small groups, in particular. But I don't hold those keys any more. If steering wants to use gsuite ggroups for this, I am fine.

If we stay with public ggroups, I think we should leave the admin groups (which means the GCP project needs no changes).

If we move to gsuite, I will need new admin groups created and give me owner on them. Then I can set it up in GCP

@cblecker
Copy link
Member

The problem is I don't want to lose access or control over any of the google groups that give infrastructure control. I would like to see those extremely tightly held.

@thockin
Copy link
Member

thockin commented Jan 23, 2019 via email

@cblecker
Copy link
Member

FOR :)

Sure, we'd need to bug one of the admins for new groups being created, but we have way better control/visibility/auditing too.

@bartsmykla
Copy link
Contributor

Hi guys. I've found one more place where where was an old url to the wg google group, and created a PR: kubernetes/community#3334

I'm in the process of adding my email to the list of CNCF's approved CLA, but after that is there anything else I can help here with? :-)

@thockin thockin removed their assignment Apr 4, 2019
@dims
Copy link
Member

dims commented Apr 16, 2019

that should be it.

/close

@k8s-ci-robot
Copy link
Contributor

@dims: Closing this issue.

In response to this:

that should be it.

/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.

@dims dims moved this from Backlog to Done in sig-k8s-infra Apr 29, 2019
@spiffxp spiffxp added this to the proof-of-concept milestone Apr 30, 2019
@spiffxp spiffxp removed this from Done in sig-k8s-infra Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

No branches or pull requests

6 participants