|
Re: TOC Election Results for GB, End User and Maintainer Seats
Brian Grant
+1. Thank you, Alexis! The CNCF would not be where it is now without your work and your drive.
On Mon, Feb 3, 2020 at 3:23 PM alexis richardson <alexis@...> wrote: thank you chris and liz!
|
|
|
|
回复：[cncf-toc] TOC Election Results for GB, End User and Maintainer Seats
Zhengyu He
Congrats!
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Saad Ali
I'm so grateful for this opportunity to serve the CNCF community. I want to thank the GB for their trust. I am passionate about building open, transparent, and inclusive communities that promote the best ideas. And I look forward to working with all the amazing TOC members to continue championing these ideals and help grow the cloud native ecosystem. I also want to thank Alexis and Joe for all their hard work. They certainly leave big shoes to fill.
Regards, Saad Ali
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Klaus Ma
Congrats to all!
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Joe Beda <jbeda@...>
Just like stepping away from the k8s steering committee -- this is bitter sweet. But I know that the TOC is in good hands and I look forward to see what y'all get up to.
Let me know if I can help at all.
Joe
From: cncf-toc@... <cncf-toc@...> on behalf of alexis richardson <alexis@...>
Sent: Monday, February 3, 2020 3:23:21 PM To: Chris Aniszczyk <caniszczyk@...> Cc: Liz Rice <liz@...>; CNCF TOC <cncf-toc@...>; Frederick Kautz <frederick@...>; Amye Scavarda Perrin <ascavarda@...> Subject: Re: [cncf-toc] TOC Election Results for GB, End User and Maintainer Seats thank you chris and liz!
the essence of community is renewal, so I couldn't be happier than to make way for these new folks a On Mon, Feb 3, 2020 at 10:21 PM Chris Aniszczyk <caniszczyk@...> wrote: > > +1 Alexis is one of the OG CNCF TOC members and I want to thank him personally being there in the early days guiding the organization while we were bootstrapping, thank you Alexis! > > On Mon, Feb 3, 2020 at 2:19 PM Liz Rice <liz@...> wrote: >> >> Thank you! >> >> Can’t say enough how helpful and wise Alexis & Joe have both been on the TOC. Really appreciate everything you have done. >> >> Looking forward to working with this great team going forward! >> >> -- >> Liz Rice - sent from my phone >> >> On 4 Feb 2020, at 00:03, Frederick Kautz <frederick@...> wrote: >> >> Fantastic race, congratulations to everyone selected! We’re all in great hands! >> >> On Feb 3, 2020, at 1:01 PM, Amye Scavarda Perrin <ascavarda@...> wrote: >> >> Many thanks to all who participated in this process, I’m pleased to announce the results of the TOC Election for the GB, End User and Maintainer appointed seats for 2020. >> >> End User appointed seat: >> Katie Gamanji >> >> GB appointed seats: >> Liz Rice >> Saad Ali >> Sheng Liang >> >> Maintainer appointed seat: >> Justin Cormack >> >> Also, a thank you to our outgoing TOC members, Alexis Richardson and Joe Beda, for their work. >> >> -- >> Amye Scavarda Perrin | Program Manager | amye@... >> >> > > > -- > Chris Aniszczyk (@cra) | +1-512-961-6719 >
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
alexis richardson
thank you chris and liz!
the essence of community is renewal, so I couldn't be happier than to make way for these new folks a On Mon, Feb 3, 2020 at 10:21 PM Chris Aniszczyk <caniszczyk@...> wrote:
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Katie Gamanji
I am at loss of words to express how grateful I am for this opportunity. Looking forward to work with this great team in the future!
On Mon, 3 Feb 2020, 22:21 Chris Aniszczyk, <caniszczyk@...> wrote:
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
+1 Alexis is one of the OG CNCF TOC members and I want to thank him personally being there in the early days guiding the organization while we were bootstrapping, thank you Alexis!
On Mon, Feb 3, 2020 at 2:19 PM Liz Rice <liz@...> wrote:
--
Chris Aniszczyk (@cra) | +1-512-961-6719
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Liz Rice
Thank you!
toggle quoted messageShow quoted text
Can’t say enough how helpful and wise Alexis & Joe have both been on the TOC. Really appreciate everything you have done. Looking forward to working with this great team going forward! -- Liz Rice - sent from my phone
On 4 Feb 2020, at 00:03, Frederick Kautz <frederick@...> wrote:
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Fantastic race, congratulations to everyone selected! We’re all in great hands!
toggle quoted messageShow quoted text
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Richard Hartmann
Dear all, thanks for organizing this vote. I know it was stated that the underlying data would not be published, but I would still like to suggest publishing a ranking, ideally with the cumulative votes per person. This is an interesting and useful signal for everyone who ran or voted. Best, Richard Sent by mobile; please excuse my brevity.
On Mon, Feb 3, 2020, 22:02 Amye Scavarda Perrin <ascavarda@...> wrote:
|
|
|
|
Re: TOC Election Results for GB, End User and Maintainer Seats
Ricardo Aravena
Congrats to all!
On Mon, Feb 3, 2020 at 1:02 PM Amye Scavarda Perrin <ascavarda@...> wrote:
|
|
|
|
TOC Election Results for GB, End User and Maintainer Seats
Amye Scavarda Perrin
Many thanks to all who participated in this process, I’m pleased to announce the results of the TOC Election for the GB, End User and Maintainer appointed seats for 2020. End User appointed seat: Katie Gamanji GB appointed seats: Liz Rice Saad Ali Sheng Liang Maintainer appointed seat: Justin Cormack Also, a thank you to our outgoing TOC members, Alexis Richardson and Joe Beda, for their work. Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
|
Apologies
Liz Rice
I’m going to have to miss tomorrow’s TOC call due to a company off-site
-- Liz Rice - sent from my phone
|
|
|
|
Re: CoC Language in the CNCF Graduation Criteria
Carolyn Van Slyck (CHIEF EMOJI OFFICER) <Carolyn.VanSlyck@...>
Yes, having an approved alternative would be great.
Thanks, Dan!
From: Dan Kohn <dan@...>
The requirement for CNCF projects to adopt the CNCF Code of Conduct (CoC) was in the original version of the graduation criteria adopted by the TOC in December 2016: https://github.com/cncf/toc/commit/9037c28e86977fb4c85578859db78c4b3e1628b8#diff-fc153d49a24a66d7f3ba90c3d144ab19R26
In December 2017, Kubernetes switched from the CNCF CoC to its own: https://github.com/kubernetes/kubernetes/commit/5fe3d9dd13d76230ce584ec1f265c6b7b3e76717#diff-d3030a18b089fdb1fbfabf6e75e4aef0
This was implicitly understood by at least some members of TOC since they are also Kubernetes Steering Committee members. But, it seems worthwhile now to 1) have the TOC approve modifying the graduation criteria to *either* be the CNCF
CoC *or* an approved alternative and 2) approve the K8s alternative CoC. --
On Fri, Jan 31, 2020 at 1:28 PM Carolyn Van Slyck (CHIEF EMOJI OFFICER) via Lists.Cncf.Io <Carolyn.VanSlyck=microsoft.com@...> wrote:
|
|
|
|
Re: [cncf-special-issues] Special issues process proposal
Lisbeth McNabb <lmcnabb@...>
Excellent Matt. I will be able to provide input Feb 7 and ahead of our next working call on Feb 20th.
On Fri, Jan 31, 2020 at 8:42 AM Matt Klein <mattklein123@...> wrote:
|
|
|
|
Re: Jepsen result for etcd 3.4.3
Bart Smykla <bartek@...>
It's great to read the report! Good job and thank you for everyone involved!
Bart Smykla On 31/01/2020, 18:17, "kubernetes-dev@... on behalf of Alexis Richardson" <kubernetes-dev@... on behalf of alexis@...> wrote: OK - thanks! If we see anything useful in the user base we'll file a PR. On Fri, Jan 31, 2020 at 4:11 PM Brandon Philips <brandon.philips@...> wrote: > > On Fri, Jan 31, 2020 at 1:35 AM Alexis Richardson <alexis@...> wrote: >> >> On Fri, Jan 31, 2020 at 1:00 AM Brandon Philips >> <brandon.philips@...> wrote: >> > >> > On Thu, Jan 30, 2020 at 7:40 AM Alexis Richardson <alexis@...> wrote: >> >> >> >> One side question from me -- I think it would be good to understand >> >> more about recommended etcd set-ups at different scales of k8s cluster >> >> (10, 50, 150, 500+ nodes) and how to deal with n/w partitions. >> > >> > >> > There are many variables on how much workload an API server puts on etcd but there is a ballpark guess doc here: >> > >> > https://etcd.io/docs/v3.4.0/op-guide/hardware/ >> >> This is great, I don't know how I missed it before. QQ: Are your >> example configs each using only one VM per cluster? That is not >> totally clear from the docs. > > > The example configs are for the etcd nodes needed to support a Kubernetes cluster of X size. Because etcd doesn't scale horizontally the guide, I believe, covers recommended sized clusters up to 5 nodes. Happy to take a PR to clarify something though. > >> >> > What do you mean by dealing with network partitions? Does the failure guide section on network partitions help? https://etcd.io/docs/v3.4.0/op-guide/failures/ >> >> Thank-you. I've seen this --- I guess what I am asking about is >> practical guidance on how often to expect different types of network >> failures, and what to expect, how long etc. I understand this is hard >> to do in a general manner. > > > That all depends on the network not on etcd. All etcd can guarantee is it will tolerate a network partition of arbitrary length of time and will only allow writes on the side of the partition where the majority of members can still talk to each other. Once the partition recovers health checks > > As far as tuning for a particular network see the tuning guide: https://etcd.io/docs/v3.4.0/tuning/ > > Thank You, > > Brandon > > -- You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@.... To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAOSi4U7f-g3FbdrtxhDg9jJdE38uKt_cZfPud%2BPKf_9sxhvSqQ%40mail.gmail.com.
|
|
|
|
Re: CoC Language in the CNCF Graduation Criteria
Dan Kohn <dan@...>
Sorry, I'd forgotten some of the history. I merged the possible schism by adding the divergence in reporting to the CNCF CoC, at the same time that we retained an outside CoC expert to manage inquiries: https://github.com/cncf/foundation/commit/ab6c1296c53d91163022445f568807d904fce6ee#diff-d3030a18b089fdb1fbfabf6e75e4aef0 So, I'm not sure that any changes are currently needed. Any CNCF project could get its own CoC, but doing so would require a vote of the TOC. -- Dan Kohn <dan@...> +1-415-233-1000 Executive Director, Cloud Native Computing Foundation cncf.io dankohn.com or book on my calendar: dankohn.com/c
On Fri, Jan 31, 2020 at 6:46 PM Matt Farina <matt@...> wrote:
|
|
|
|
Re: CoC Language in the CNCF Graduation Criteria
Matt Farina
I don't think Kubernetes currently follows a separate Code of Conduct. If you look in https://github.com/kubernetes/community/blob/master/code-of-conduct.md you'll find a pointer to the CNCF CoC. If Kubernetes has a separate CoC it's not currently documented in either the Kubernetes/Kubernetes repo or the Kubernetes Community repo. I would be curious to know what Kubenetes wants to do differently and why. In open source it can be useful to know this and it provides transparency to the governance of the project. - Matt Farina
On Fri, Jan 31, 2020, at 5:34 PM, Dan Kohn wrote:
|
|
|
|
Re: CoC Language in the CNCF Graduation Criteria
Dan Kohn <dan@...>
The requirement for CNCF projects to adopt the CNCF Code of Conduct (CoC) was in the original version of the graduation criteria adopted by the TOC in December 2016: https://github.com/cncf/toc/commit/9037c28e86977fb4c85578859db78c4b3e1628b8#diff-fc153d49a24a66d7f3ba90c3d144ab19R26 In December 2017, Kubernetes switched from the CNCF CoC to its own: https://github.com/kubernetes/kubernetes/commit/5fe3d9dd13d76230ce584ec1f265c6b7b3e76717#diff-d3030a18b089fdb1fbfabf6e75e4aef0 This was implicitly understood by at least some members of TOC since they are also Kubernetes Steering Committee members. But, it seems worthwhile now to 1) have the TOC approve modifying the graduation criteria to *either* be the CNCF CoC *or* an approved alternative and 2) approve the K8s alternative CoC. -- Dan Kohn <dan@...> +1-415-233-1000 Executive Director, Cloud Native Computing Foundation cncf.io dankohn.com or book on my calendar: dankohn.com/c On Fri, Jan 31, 2020 at 1:28 PM Carolyn Van Slyck (CHIEF EMOJI OFFICER) via Lists.Cncf.Io <Carolyn.VanSlyck=microsoft.com@...> wrote:
|
|
|