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

[governance] discuss Moby TSC umbrella vs. in-project governance only #15

Closed
estesp opened this issue Feb 19, 2019 · 20 comments
Closed

Comments

@estesp
Copy link
Member

estesp commented Feb 19, 2019

Per the CNCF TOC graduation vote discussion, this issue reflects our commitment to revisit project governance with external connection to the Moby TSC.

@stevvooe
Copy link
Member

Ay!

Current language is here:

containerd defers to the Moby Technical Steering Committee for escalations and resolution on disputes for technical matters.

@crosbymichael
Copy link
Member

I'm in favor of removing the TSC and having decisions left to the maintainers of containerd. The project is mature enough and we have a large, diverse group of maintainers on the project to handle these issues.

ping @containerd/containerd-maintainers @containerd/containerd-reviewers

@lowenna
Copy link

lowenna commented Feb 19, 2019

+1 to what @crosbymichael said

@mlaventure
Copy link
Contributor

Sounds good to me, Containerd has grown enough that active maintainers should be able to take on that responsibilities.

@fuweid
Copy link
Member

fuweid commented Feb 20, 2019

+1 SGTM

@Ace-Tang
Copy link

Ace-Tang commented Feb 20, 2019

removing the TSC and having decisions left to the maintainers of containerd

Really a good news 👍

@AkihiroSuda
Copy link
Member

SGTM

@estesp
Copy link
Member Author

estesp commented Feb 20, 2019

Just to be clear, I'm in favor of this as well.

@jterry75
Copy link
Contributor

+1 SGTM

@hqhq
Copy link

hqhq commented Feb 20, 2019

SGTM

2 similar comments
@ehazlett
Copy link
Member

SGTM

@dqminh
Copy link
Member

dqminh commented Feb 20, 2019

SGTM

@mikebrow
Copy link
Member

I'm in favor of removing the TSC and having decisions left to the maintainers of containerd. The project is mature enough and we have a large, diverse group of maintainers on the project to handle these issues.

+1 SGTM

@yanxuean
Copy link
Member

yanxuean commented Feb 20, 2019

removing the TSC

+1 SGTM

@Random-Liu
Copy link
Member

removing the TSC

+1

@yujuhong
Copy link
Member

+1

1 similar comment
@miaoyq
Copy link
Member

miaoyq commented Feb 22, 2019

+1

@dchen1107
Copy link

+1 on what @crosbymichael said.

@dmcgowan
Copy link
Member

+1
I am glad to see this is unanimous. I think it reflects nicely on the maturity of the project and this group as a whole.

crosbymichael added a commit to crosbymichael/project that referenced this issue Feb 27, 2019
Closes containerd#15

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
@crosbymichael
Copy link
Member

I opened #16 to resolve this since everyone is in favor of the change.

crosbymichael added a commit to crosbymichael/project that referenced this issue Feb 28, 2019
Closes containerd#15

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
crosbymichael added a commit to crosbymichael/project that referenced this issue Mar 6, 2019
Closes containerd#15

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests