 Hey everyone, we are part of the Corranities Code of Conduct Committee and we're here today to talk a little bit more about who we are, what we do and kind of our latest project we've been working on which includes a transparency report. And so to start I'm going to have us do intros. Celeste, you want to introduce yourself? Hi, I'm Celeste. I'm a staff technical writer for the CNCF, though I participate in the Code of Conduct Committee as an individual contributor, not a representative of the LF. And yeah, that's more or less me. Tim. I'm Tim Pepper. I'm a senior staff engineer at VMware and similarly, obviously not a VMware Code of Conduct enforcer, but a member of the open source community here. And Karen. Hey, so I'm Karen. I work for Microsoft Azure and I'm a community manager on a few of our different open source projects like Helm and several others. But I am also a member of the Code of Conduct Committee. Well, with that, let's jump into the Code of Conduct concept and what our committee is. Can either of you talk about what we do, why we exist, and kind of what our scope is? All right, I'll take it. So the Code of Conduct Committee is a body we are elected by the steering committee and nominations can either be self nominations or nominations by others. And we are here to effectively enforce community safety. And what community safety really means in this regards is ensuring that any disagreements that people or different groups within the Kubernetes community have are resolved in a helpful way. Trying our best to sort of encourage good behavior and uphold the community code of conduct. And as of yesterday, publishing transparency reports on the work that we do. Tim, is there anything you'd like to add? I think a key thing to understand there is that we're an independent body. We try to be neutral and unbiased. And I think people maybe see a Code of Conduct view it and potentially cynically think, oh, there's no accountability behind these things. It's just a feel good statement. But this body exists to make sure that there can be accountability. And as we approach that, we try to do it with a restorative mindset. It's also really common when you see a body like this to sort of presume it's the police or it's punitive. We're here to kick people out. But we're actually here to try and find positive, mutually positive restorative outcomes where there is conflict. And that's a really critical part of a healthy, sustainable community. All right. So we mentioned the transparency report. Can we talk a little bit more about what this is? What it isn't? And then why did we start doing this? What is the purpose? I'm going to tell you the charge this time. All right. So this is a concept that's out there in multiple forms. Like if you do a Google search for transparency report, you'll come up with a variety of pieces of information on how these things are done. But the basic concept is to demonstrate that there is accountability. We need to give some sort of evidence of that. But it's also really important that it be confidential. If people are being escalated or escalating or being escalated in some way to the Code of Conduct Committee that needs handled in a confidential way, and again, without bias and investigations need to happen. But somehow we have to give a way of indicating that that has happened. And the transparency report gives a form for that. So our goal here is to twice-yearly do a report that gives some statistics and describes the types of areas in which conduct incidents were reported, demonstrate that investigations happened, and also give some statistics on action to show that it's not just sort of looking and shrugging like, I don't know what we could do about that, but that we are actually engaging and we are finding constructive outcomes. Yeah. Absolutely happens basically. Yeah. I think the other thing that I would add to is that I think both A, the concept of a Code of Conduct Committee and B, the concept of a transparency report are a little bit intimidating to other people. Again, as Tim mentioned, people tend to think of Code of Conduct Bodies as being very punitive, being the cops, being like the teacher in the classroom and you go and tattle on your friends too. And similarly, I think transparency reports tend to be really intimidating for a similar reason in terms of like, oh my God, no, they're doing stuff. But the thing to keep in mind is being able to publish a transparency report, I think really means that the Kubernetes community is at a certain level of maturity where we can reflectively look at the work that we're doing, reflectively say that we all are humans and that we do human things like have disagreements, and that as a Code of Conduct Body, we are mature enough to publish that information in a way that doesn't out people who have reported to us. So it's really just a mark of community maturity, and I think we should all be proud of ourselves. So let's get concrete on that. I'm going to screen share and we can drop an url into the chat for folks to see. Hopefully everybody can see that now. Okay, yeah, there is the link there in the Twitch stream I see. So things are coming through. So if you're looking at this document that's now committed and get, you see a little bit of context on the front matter of this page. But then the key thing is some obviously anonymized statistics. These are sort of raw accounts to say that we've had incidents reported also through a variety of forums that these things come in. It's not just the Code of Conduct Committee, there's sort of a federation of moderation on different platforms. And the number of incidents is actually, you might think, wow, 85 incidents, I never heard about these things. Wow, interesting. And then we also, we do thorough investigations and some of the things are clearly a violation of the Code of Conduct. So we go and take action there. And I think one of the key things that we want to highlight in just this first instance is like these numbers are non-zero. There is activity happening, there's accountability happening. And probably that people generally are not seeing this, it's a sign that it's working, it's confidential and restorative outcomes are happening. You're not seeing these big fireballs of flame and conflict. We're going somewhere positive and constructive. Yeah, I think the other thing that I want to call out is the Slack number looks really high. Like 68 incidents seems like a lot, given the contributor community size. It's important to note that Slack is probably the biggest platform or community space that we have actual numbers on. And I think there's over 100,000 people in the Slack instance, which is huge. I think we're actually one of Slack's biggest instances. So given that, and given if Tim scrolls down, there's a bit of analysis. Basically, all of these issues with Slack were people being banned from Slack for spamming others. 68 out of 100,000 is actually not, it's not too bad in the grand scheme of things, though it does seem a little analogous without that piece of context. So definitely give it a read through. You're liable to have a spammer or a troll of some sort on a massive internet platform in any given week. So it's not surprising. I mean, you'd think every day this could be happening. And it's a sign that people are, we have a set of moderators who are watching and constructively handling things. Well, it also means that people are sharing things with these trusted moderators, right? And that same thing goes for us as well. And I just wanted to note, like this is our first transparency report. So it's kind of going to be our baseline for the next few ones. Yeah, we don't have strong, strong statements about whether something is really good or really bad right now. Again, this is our baseline going forward. And we, we hope that within this, like, is if people are seeing this and seeing that it's a constructive way to maybe get ahead of problems instead of dealing with things that are really, really falling apart, that maybe discussion is opened a little earlier on things. And we actually see an increase in potential incident reports because people want to constructively get ahead of something they foresee might be a problem. So we're not, we don't want these numbers to be low. We feel like that would be a bad sign of, of trust in, and this body is a, that restorative function. And I mean, just to, to mention it, because I don't think we've mentioned it before. The code of conduct is published both on kubernetes.io and in the cncf slash foundation repository on github. We actually recently updated the code of conduct to version 1.1. So what's on kubernetes.io has not actually been updated. First off, because that literally went through like earlier today. The second thing is, if you are involved in the kubernetes project or attending kubecon cloud native con, you can report incidents to conduct at kubernetes.io. If you are another cncf project, you want to go to, I believe, conduct at cncf.io. If you're, yeah, I guess the only other thing I would say is, if you're on the fence about whether you should email us or not, email us. It's usually better to, to hear from people and say this actually isn't an issue, then it is to not hear something that is potentially an issue. So I really like that Celeste mentioned that the kubernetes project's code of conduct is coming from the cncf's code of conduct. And within our aspiration to do more transparency reporting going forward, this become a regular thing that this is our first baseline. We also aspire to bring more of the concept of code of conduct committee of transparency reporting of restorative action to the broader cncf community. So whether that's through the contributor strategy body at cncf or just putting the word out like this here doing conference talks where we are a body specific to the kubernetes project. But kubernetes project is kind of unique and having done so many things around contributor experience from the early days and trying to formulate a strong governance system that enables community health and safety and sustainability that we're feeling a need to try and take that to other places as well to kind of level it up make it more generic and maybe make repeatable processes or documents or training and things like that that other projects could leverage as well. Yeah, cool. I think that wraps up our goals and messaging pretty well. Any parting thoughts? Give the give the transparency report a read. I think over time it will end up being a very interesting measure of health for the community. Again, if you have if you have any questions we also have a public channel available I think as of last coupon. So on the community slack instance that's code dash of dash conduct. Please don't report anything in that channel because it is public. But like if you just want to ask us questions, that's the best way to find us. And yeah, again, if there's anything going on at coupon that you see, you can either email conduct at kubernetes.io. You can report it to any Linux foundation staff. Please be safe and please be respectful of each other and have a wonderful convention conference. Hard to add much to that. The one thing I would say also though is as you hear the code of conduct mentioned in meetings or in forums reminding here's your reminder where we adhere to this code of conduct. It doesn't hurt to every now and then glance at it read it over and especially as there's a new updated version coming in just to kind of have a little more concrete awareness of what it means. But then also know as we're here trying to demonstrate that there's a body behind it and we care we care about the project and the project health and safety and what they're for you. I will be at coupon and if anyone anyone wants to ask me questions about the code of conduct committee in person, I'm happy to chat. I'll let you two speak for yourself. Yeah. Hello. Cool. All right. Well, thank you everyone for joining us. Like I said, we'll be around and hopefully you take a look at our transparency report. Thanks. Thanks everyone. Bye everybody.