 Good morning, so I mean I so I have this session. It is I'm gonna go over kind of the process of how We've updated the Drupal code of conduct over the last year It is I have a Few very dense slides So if I am going too fast if I'm like doing too much info dumping Feel free to like raise your hand and slow me down a little bit You know, I also want to be respectful of folks time and everything here And it makes sure we leave time for some Q&A and discussion afterward So Yeah, so as I'm going through if you're like George slow it down. Just just shoot up a hand and And then we should hopefully have some good time for Q&A at the end So yes, welcome to how we updated the Drupal code of conduct I'm George DeMette. So my day job is founder and CEO of Palantir.net Digital strategy design development consultancy based outside of Chicago, but with people all over the US So I've been active in the Drupal community since 07 the first Drupal event I attended was the Open-source CMS summit at the Yahoo campus in Sunnyvale So that was back when Yahoo had a campus. It gives you a sense of how long ago it was but You know really small amazing kind of opportunity to meet so many people who have been so active in the community for so long and Many of whom are continue to be active today So in terms of how I give back to the community, I'm not a coder but I do Kind of know how to talk to people and listen to people and so I've been so I was one of the founding members of the Drupal community working groups conflict resolution team And I've got a slide that will kind of explain how all these different groups are and how they relate to each other but what essentially means is that between 2013 and 2021 You know when I stepped down I was one of the folks responsible for Code of conduct enforcement Conflict mediation resolution Things of that nature You know as one of the founding members we we learned a lot we built up a lot of processes along the way We made mistakes and learned from them and really tried to document and Bring that knowledge into our you know how we move forward so right now I'm a member of the Drupal community health team which means that I don't I'm not involved in Conflict resolution or code of conduct Issues unless I'm specifically called in either because I have background knowledge of the situation Or some sort of specific Expertise that would be useful And then yeah co-offer the Drupal's code of conduct for events about 10 years ago Gosh 11 years ago at this point After I was one of the co-chairs of Drupal Con Chicago in 2011 We didn't have a code of conduct For our events we didn't have a code of conduct for Drupal con and as someone who is kind of sitting in the like organizer seat and Hearing afterward about some of the things that happened at that event fortunately very few but Still it was like you know what we kind of need a code of conduct for events and so went through that process and Help create the the initial version of the document that exists today And so I'll explain the difference again between the community code of conduct, which is what you see on Drupal.org and The code of conduct for an event like Drupal con an in-person event where you have people interacting with each other in person right or even virtually at events and and sort of the differences between how that gets handled so Let me lay some context here. So This is this is the best way I found to visualize this so In terms of Community governance the community working group the way we're set up. We have kind of a unique structure so Starting at the bottom. I mentioned the community health team and so the community health team is a group of I believe about two to three dozen folks who are Actively engaged in different aspects of the community from all over the project whether they're folks who work on Drupal.org whether they're folks who work on events or Ambassadors people who are involved with communities in different parts of the world making sure that we have a global representation and And again as I said, you know They're in yellow. So that means it's my little color coding means we don't get involved in Conflict resolution, you know between folks somebody files an incident report that doesn't the community health team doesn't see that But but obviously may get involved If there's if there's something going on in an issue queue thread that's public Sometimes one of our community health teams will be one of the folks who post one of those little we call them a little nudge messages That kind of reminds people to be respectful and everything. So that's a community health team Then we have the subject matter experts And so those are people who might be part of the community health team who might get called in on Particular conflict because there's they have again some sort of Specific expertise whether it's a specific language or cultural expertise whether it involves maybe a Particular subset of the community who that person, you know Has a better knowledge of things like that and so that's why That I have in blue so that may that means that somebody who might sometime get pulled in on an incident report And then you have the the community working groups conflict resolution team That's that kind of small core group usually around Four to six people who are really actively involved when they receive the incident reports And they are they're the ones who work through them And you know and basically try to resolve the situation or conflict in one way or the other So so again the blue color coding those are people who who may be involved with with issues the community working group has So they are overseen by the review panel the review panel is three people consists of two community elected board members of the Drupal Association and an independent representative Basically someone who's involved in community management From a different open source project or involved with different open source projects. And so that person is And actually has been since we put this governance structure in place in 2019 John O'Bacon, so folks aren't familiar with him He's kind of a big name and open source community management wrote a couple books on it all around pretty great guy But very very experienced with with with this stuff so the review panel their role would be if there is an issue that The community working group either needs some additional assistance on or if somebody Wants to appeal a decision of the community working group that review panel would get involved in that point the review panel also approves The membership of the community working group of that conflict resolution team And so that's the oversight there and this was a structure. We put in place in beginning of 2019 and previously The conflict resolution team had reported directly to Drees That wasn't something that scaled it didn't work for anyone And and Drees didn't want Want to be responsible for it either But you know at the time the initial governance structures were set in place in 2013 He was kind of the only person who could do it so And because we have those community elected board members who are Part of that make up two-thirds of that panel. It does mean that there is a Level of accountability to the community at large So then above so so I've got all of those folks that I've just talked about are bound by the Community working groups code of ethics. That's a document that we have it's up on Drupal.org you can look at it But it basically says things like If there is an incident report that gets filed And and you are you are part of working on that like you don't Keep it you keep it confidential You you know don't You know share the details of the incident or people's names you protect Particularly the privacy of those who are making reports So that they are feel safe doing so And and it also covers things like a conflict of interest like how you recuse yourself if you Have a connection to one of the involved parties in an incident things like that and again, that's something we put in place in 2017-2018 Just as kind of an added Way of improving our accountability and governance so then above that obviously you have the Drupal Association Board of Directors and So that includes the two community elected board members plus I think there's 12 13 other I'm looking over at Leslie because she Roughly in there And those are obviously the folks who oversee The the running of the Drupal Association. They're they're really more of a strategic board So they they don't get involved in operations. That's that's the CEO Tim Doyle manages that and there is if something Can in theory like get escalated if it has such a huge community-wide impact that You know the review panel feels that the entire board needs to be looped in on it that That can happen It has never happened The kind of incident that that would Necessitate that would be I would think pretty extreme and there's also kind of language In our charter about about how that gets handled again to make sure that we are We are protecting people's Privacy and everything so that's it's a little bit of context kind of laying out our structure because it is a little bit different Than other open-source projects. We are a little bit different than many open-source projects because we are You know an independent project. We don't have we're not corporate sponsored Corporate project and basically has their HR department handle a lot of these things, but we have our own structure so the So I mentioned before there's there's the event code So there's a code of conduct for this event that is enforced and managed by the Drupal Association staff So these folks are generally not involved unless they're looped in on the issue Local Community events Drupal camps etc. Again have their own codes of conduct. They have their own enforcement If there is an incident that happens at a camp we really want to make sure that you know We encourage camp organizers to let the community working group know of that what happened because sometimes what you'll see is you might have somebody who We've seen situations where there's somebody who kind of has a pattern of behavior at different in-person events and And if the CWG knows about it, then they can Take appropriate action to make sure that harm doesn't occur at other events. All right. That's a whole lot of context More context now So here's kind of a brief history and this is how we got to this point So Drupal actually was one of the very like a very early project in terms of adopting a code of conduct and it was back in 2010 Moe Schweitzman who I think is like Number he's in the number three or four. He's in the top ten Drupal dot org numbers Been with the project for an incredibly long time since the start He proposed in 2010 that we essentially adopt the Ubuntu code of conduct Which we which we did there was you know a very short Discussion and and everyone was like yep. That sounds like a great idea But it when it was adopted there was no there was no enforcement mechanism There was no language around what to do if there's conflict. It was really just kind of a well We'll put that in when we get there and so You know what happened during that time and you know again finding out about this Later is that you know, there was obviously still harassment and bad things happening and people Leaving the project and because they didn't know who they could talk to or what could be done about it so in 2012 summer 2012 Dries held a governance sprint and it was really to put together Some governance structures Around both the technical direction of the project and the community So there were there several working groups created the community working group was one of them And as I mentioned before this is around the time as well when the Drupal Association adopted their code of conduct for Drupal con and other events So then CWG was chartered in the spring of 2013 kind of first order of business after kind of sorting through some of the outstanding things we were aware of was To develop incident report and conflict resolution process We added some anti-harassment language the code of conduct, but it was again very general It's like we don't tolerate harassment, but we didn't really kind of go into what that meant But at least if somebody Experienced harassment they had a place to report it. They had a way to report it and that was in the code of conduct and we kind of continued along with that until 2017 There was kind of a major community incident that occurred in 2017 I'm not going to go into the details of that, but the Up the result of that was that there were a series of community conversations that happened starting at Drupal con And then a few others that were held over the summer of 2017 facilitated by Whitney Hess who's kind of this amazing coach and And and then there were also an additional kind of there were some surveys There were some stuff that went out really around community governance because there was a kind of a widespread Recognition that something needed to be done out of that came several series of proposals to improve community governance There a lot of them were focused on number of them were focused on Oversight and governance of the community working group. So again 2018 we've worked on that at the beginning of 2019 adopted a new charter that provided that oversight and accountability And it was like, okay 2019. So now 2020 will we'll work on the other thing which is updating the code of conduct And we sent out a survey and stuff and then there was a global pandemic. So that kind of Kick things a little bit Down the came down the road. But in the meantime, we did create the community health team and it was really fortuitous timing on that because the Community health was in a pretty in a pretty Rough space in 2020 because you know the aforementioned global pandemic. So It was really good to have a group of people who really were passionate about helping the community so 22 about almost exactly a year ago so they the We started the process of Revising and adopting a revised community code of conduct and so that's where I'm going to kind of start Yeah, that was all prelude. I told you I had a lot of stuff So this was a seven person group was assembled out of community health team members and conflict resolution team members and so That was myself Nicky Flores Who was kind of stepped away halfway through the process because she was elected to the Drupal Association Board became part of the review panel Therefore had kind of a little bit of conflict of interest Julian Taylor from the UK Jordanna Fung Who's from Suriname and who leads up the conflict resolution team? Marcusias Donovan guard and Mike and elo who also along with myself been a long time member of the conflict resolution team So first thing we did like every good group should do is charter We used Miro to do this To basically define shared goals measures of success opportunities and constraints. We did this through Miro We did a bunch of stickies and You know organize and greed and voted on them And then once we kind of had that the sort of what are we doing? Why are we doing it? and We then created a timeline and Because we knew we needed to give ourselves that in order to make sure this thing actually happened and So we we had some key milestones. We had two-week sprints We started in June of 22 and we agreed that we were gonna get to a place where we had a draft by mid-December of that year so six-month process And we knew we needed to let folks know what was happening. So we posted public updates the Drupal community blog It basically every two to four weeks to let folks know what was going on. Okay So step one We knew that just that group of us was not going to be enough We were not going to successfully capture all the different perspectives of all the different folks in the community We were coming in a lot of us with a lot of experience and a lot of perspective But not necessarily the broader perspective of our entire community so We created a list of groups and individuals we wanted to make sure we're involved We wanted to consult with during this and so security working group event organizers Drupal diversity and inclusion We talked to some contributors maintainers we involved Drupal Association staff members Yeah, community accessibility And then really this this last part is really important because you know you look at that list before and We are largely folks from North America the UK Jordan is from Suriname which is in South America But we realized we needed a lot more non United States non Western European perspectives and so we reached out to folks in South Asia Africa Latin America other places where We knew there were involved community members who would be willing to kind of review what we were working on and you know check and make sure we were being inclusive including those perspectives and fortunately had already a great community health team Who who could help us with that? So then We we took a look we're like okay, so we have our code of conduct this this you know This point 12 year old a boon to code of conduct that we've been working with It's had a couple updates since we took a look at that The contributor covenant very widely used open source code of conduct. We looked at that bunch of others up there We included not just open source projects We include some kind of open source adjacent communities and spiral is kind of an organization of folks who are involved with Self-organization they have a really amazing handbook and we just split them all up divided them up everyone took some and reviewed them and And then we we basically kind of broke them down into their different components like what does this one have? What does this one have what does this one have and then we we put all those on stickies again? Going back to Miro, and then we did this like really cool exercise where we was we voted on must have should have and nice to have for our code of conduct and You know it's kind of small on the screen But it was like we agreed that we needed to have a statement of shared values, right? There was a must have for example, so it's in that center bullet You know incident report forms things like that and then around the edge you have some of the the nice to have You know things like getting into ideas of transformative justice and things like that Things that we didn't feel were absolutely necessary, but that we We thought were important so that's How we started to organize it and then we we created a Google Doc and for each of those components of All the different codes of conduct We basically pulled the language the from each of those codes Organized them in a Google Doc by the should haves must haves nice to haves and And took that and we shared it out with that that broader group of about two dozen community stakeholders For their review and feedback to see okay, this is kind of where we're thinking this might go What do you think and So we got some really like great feedback You know using language that was easier to read this was particularly important for our folks who were Outside, you know the US and UK and other English speaking countries that a lot of the language that is in these Codes of conduct is really Difficult to read difficult. It's complex English and And if in if English is not your first language It it takes a little bit more work to to to translate it Discussion of a there was so one of the things we we knew we had gotten a lot of feedback During that 2017 process about the code of conduct and how it needed to be more specific more actionable And so there was a lot of discussion around sort of what those kind of examples should be of You know what kind of behaviors? We wanted to promote to encourage to incentivize in the community and which kinds of behaviors You know word were not And then this was also again a really great place I'm so glad we had this kind of this this group of community members because there were You know words and phrases and some of these different Codes of conduct that to someone like me seemed perfectly innocuous But but if you're someone in a community of color They read differently you know, there's words words around things like respectability and stuff like that which It would really appreciate it having those kind of flagged for us So we we knew and suggestions for kind of alternate ways we could get the summit the same point across you know without Inadvertently saying something that that might read differently to someone else So then Let's see. Oh, there. We are this was the the big meat and potatoes part of it This was this was probably about Four months worth of the six month project was revisions revisions we Adapted that outline that we created along with all the feedback into an initial draft and I Really want to thank Donna Bungard here. She did an amazing job of starting to pull that together and Then we basically just continued to meet we would review the draft make additional edits just Keep going on this every every two weeks to just to really kind of hone this down into something that was going to be Clear and readable for everyone Yeah, Hemingway editor and readable. This was for me. I'm a person who likes to write I like to use big words and complex sentences So this was a very humbling experience to try to communicate some pretty nuanced concepts using very simple very direct language and You know because we knew that that was really important and you know again I talked about some of the other open source codes of conduct, you know So the contributor covenants right which is one of the most widely used open source codes of conduct it's actually written at a college graduate reading level and that is Really challenging to understand Even for people for whom English is their native language So we we really were doing a lot of work to try to make things clear short and set short sentences shorter words But that's still communicated the meaning So then then we got to a point where we finally like We're able to share we had a draft that we felt comfortable sharing both with our Stakeholder group and then the full community health team as well for additional review and suggestions So then Again, that was another round another couple rounds of changes. We finally got to a place where it's like, okay I think we got something we can share with the community at large and So we created an issue on triple org as you do And to solicit feed along with the draft text to solicit feedback from the community This was something we did back in November of last year We also invited as part of that people to share feedback privately because we know again from experience that there are Certain things that people may not feel safe saying publicly But but feedback that's very important There there might be people who you know who either are concerned They might be a target of harassment or who might have a piece of feedback They want to live her privately so we enabled people to do that we wrote a blog post outlining why we were doing this what changes we were looking for the process to say the next steps Threw it out on all the community channels slack social media who's in the Drupal newsletter And everything trying to make sure as many folks knew about it as possible And as far as the issue discussion itself like we didn't we didn't want to wait into that We didn't we didn't get involved. We didn't share our opinion We did answer clarifying questions So folks, you know if folks were confused either about the process or what this thing was or that thing was we let Them know and then they got this is a really important thing that we've learned from past is is to Timebox that feedback period right say this is the period in which we are accepting feedback We will lock the issue after that point Just to avoid things from spiraling or bike shedding out of control So I mean in terms of the feedback we received it was really interesting and one of the big surprises for me was that We actually didn't get a Lot of feedback on the new language we were proposing, but we actually got a lot of feedback on on the Language that we didn't change that that had been there for ten years You know and people were like or twelve years and people were like yeah I don't really like the way that's that's worded or that doesn't make sense or that's you know Not not consistent with my experience in the community. So that was That was actually almost kind of a signal that maybe we needed to Maybe even push things a little forward So we we did go into then another couple rounds of revision to incorporate that community feedback And then got that into a finalized draft. We did meet our deadline We did get it finished in December and and then shared that finalized draft With the conflict resolution team they shared it with the review panel as per the CWG's charter the conflict resolution team is responsible for maintaining the code of conduct. So they're the ones You know who were responsible for for reviewing and approving it but they did involve the the review panel and There was you know, there were some minor additional changes We made mostly around clarification around scope You know, that was a particularly tough nugget to crack and Then we created an an unpublished test page on Drupal.org to illustrate because As we'll see I think over on the next slide we the new code of conduct Has a different layout essentially than the current one And so we wanted to make sure it was like clear and people could scan it and everything so Then after all that So May 30th is what just over a week ago We published an announced the code of conduct I'll the URL for that will be on the following page if you want to look at that But there's also blog posts that got published posted out the Drupal planet I just got my weekly drop in my inbox today. I saw that it was promoted there Dries has posted about it on all of his socials He's got a pretty wide reach and so You know, this is something that that folks should hopefully know about or be starting to know about And I've also been speaking with folks at the at the Drupal Association about How we can make sure that it gets a little bit of more promotion on Drupal.org as well What we decided to do was to give folks essentially a month So the new code of conduct where the updated code of conduct will take effect on July 1st And at that point if there will be a like a little if you log on a Drupal.org After July 1st, there'll be a like a little thing Notifying people that the code of conduct has been updated with a link to check it out That will only appear the first time. It'll go way after that And then we also made sure that everyone involved we reached out to everyone to see if they were willing to Receive contribution credit and we made sure that those who did did receive it so How am I doing on time? Few more minutes. Okay. Thank you. So what's new? What did we do? Overall we Preserved the structure and again, that's that's the URL down there if you want to like look at it right now. That's Slash node slash 3 3 3 3 9 5 7 For the recording But we really expanded out the The introduction the big introductory paragraph That really talks more about that lays the context of talks about Drupal's Values and principles how this code of conduct relates to that It it goes into more detail about where the code of conduct applies who it applies to if you're interacting with other community members in different spaces and We really wanted to make sure we emphasize that Maintaining a welcoming community. This is this is everyone's job. This is a shared responsibility And we wanted to make sure that was really clear and we've actually put that in throughout We also put in a statement to pledge welcoming supporting people of All backgrounds and identities and you know, this is this is probably the one Sentence that kind of like that kind of broke our readability editors a little readability software a little bit because We again really we list To make it again very clear and this is a best practice from other codes of conduct to make it really clear that The different forms of discrimination that we We do not tolerate right and and again that was also a really great place where having a Global audience review was important because there were a few things that again because most of these things were written from Western perspective that we missed You know discrimination by caste or tribal affiliation for example, so we made sure those were included Talked about yeah scope enforcement expectations We have the you can see in the screenshot. We've got a little call out Very clear. So if you have an incident you need to report, this is how you do it There's more detailed instructions in the document, but that we want to make sure that was Very easy for people to find and see because very often when someone's reporting incident They don't want to read the whole damn code of conduct. They just need to get Make sure someone knows about their their their problems. So we're the problem. They've seen right? So we we pulled that out the So again, I talked about so shorter sentences shorter paragraphs easier to comprehend We gave it a slightly more conversational less formal tone So that's the readability and then the really the kind of big thing that's different is these examples of a positive and unacceptable behaviors and So we were really kind of struggling with this at first because again This was a piece of feedback from all the different surveys and conversations everything that people and even in some of the incidents that we had talked with people about folks are like Well, I didn't know that that wasn't okay, and it's like, okay Well, you should have but I guess maybe sometimes we do need to spell it out. So we spelled it out And and and but if we included all of those like in the document it'd be like a mile long and again We were looking for readability Scannability so these these are actually presented on the page. They're they're kind of hidden fields and so They're they're collapsed by default, but you can expand them out To to get those examples those examples are not like essential parts of the text But if you are looking for a better understanding of what this means in practice you can collapse those out Yeah, so those are kind of the big the big picture changes You know again, you can look at the document yourself now it is published and You know preview got a question or concern. There's violin issue or reach out directly You know again it this is this is this is not perfect Nothing is but but we think we We think we got it and But we still have a couple weeks if there's like Some typo or language Thing that needs to be changed So, yeah, what do we learn this has been quite a process Um So for anyone who's looking to do something like this So again This for me really helpful important setting goal and milestones early Don't be afraid to make changes. We realized that you know, we had a plan and our first plan did not include enough rounds of revision So we tweaked there, but we were able to do it in a way that preserved to the overall schedule Inviting a diverse group of people Early on to review the draft Can catch many issues. This was a big lesson that I that we learned I learned Going back 11 years when we did the the event code of conduct We did have a group of folks, but it didn't it didn't have any European representation and when we published it You know, I publish it. I think at the end of the day US time and and I woke up the next morning my inbox was flooded with a lot of feedback from folks in Europe and it's like, okay Not gonna make that mistake again. I'm gonna include them from the start And so yeah, so we we did You know and and and these folks Very very grateful to this essential part of the process As I said before a lot of popular codes of conduct are written using really complex language. This is kind of like a bit of feedback for us an open source in general we Often get very technical and that also means we sometimes get very technical in our in our community language and Yeah, and we should really be mindful of that because it it can make our communities feel a little less welcoming And again allowing people to contribute privately and anonymously so we we had a couple pieces of Really great anonymous feedback. We had some less constructive pieces of anonymous feedback, but We we accepted it and you know, you know We we knew it was good to hear and I and going back actually to that community review process You know, there there were a lot of suggestions We incorporated I was really grateful. I saw Ryan's Rama Who tweeted or LinkedIn posted? That you know because he had participated in the in the in the open discussion in the issue queue and he said That he really appreciated that we did incorporate some of his feedback, but we didn't incorporate all of it and that that that that Helped him feel comfortable that this community review was not just paying lip service that we really were listening so even if even if he didn't get all the things he wanted so and then yeah these things take time and You know, there was a big part of me of us for a while. I was like why I Probably just go and bang out this code of conduct over a weekend You know chat GPT wasn't available when we were doing this, but I was like I Actually ran this through chat GPT and was pleasantly surprised at how well it it it accepted it You know, but that's that's not going to capture The the the human feedback and the unique kind of human fingerprint of our community, right? You know, so I think there's there's very often a temptation in open source. It's like okay Well, we'll just adopt whatever, you know code of conduct is out there and And that's fine, but we are such a broad community broad diverse global community and a one-size-fits-all approach does not work for us so and Getting to that place though where we have something that does takes time so I Have any speaking of time if I have any left. Oh Great five minutes for questions. Thank you And yeah, and that's where to find me I'm not on Twitter anymore, but I'm on the the mastodons and the linkedons any questions I Was a lot of talking I just did Yes, you know, we haven't decided on the wording yet The quiz sorry, yes for the recording about the question was when the when the little announcement box shows up on Drupal.org at the beginning of July Will with the you know, we've updated our code of conduct will that include a little TLDR of the changes? And I was just saying we haven't picked the wording yet. I don't know how much space will have to work with So this is a conversation. We'll be having with with Neil drum and the technical team Tim Lennon as well and At the very least I think we'll link to a summary of the changes So folks know but but I don't know how much text will be able to squeeze in there And then you have a question. No someone I thought I saw another hand somewhere Cory so Cory's question is what is the most surprising part of the process for me? So for me personally it was It really was the thing around the complex language and So I actually this this is kind of set me down a little path. I I have I have realized that I Am good at writing words I'm not always good at writing words that are easy for other people to understand and And and that it is it was this was that such a humbling process because I There are some very complex Particularly when it comes to scope and enforcement of a code of conduct, you know like What kind of context would like, you know, for example like We if a community member Starts harassing another community member over social media the social media platform is not itself Something that's owned by the community. It's an interaction between two community members, right and That kind of harassment is absolutely something we can and should be within the scope of our Code of conduct to take action on we can't just be like, oh Well is on Twitter, so it doesn't doesn't apply that that's absurd, right? And and so but figuring out how to communicate that Using simple clear to direct language That that was what we were we were still revising on that one up until the very very end and so Yeah, so I now have a much greater appreciation for What they call plain language or clear language? It's it's a thing and I wrote a little personal blog or post for a company blog about It's like really part of accessibility, right like we we think about accessibility and how it you know, we think about like oh, you know or the Use the font stand out about the background and everything But like if the words themselves are not accessible then like it doesn't matter how good your contrast ratio is Yeah, thank you. Yes Yeah Well, I mean hopefully it won't be me doing it I really want this to be something, you know, and I'm gonna talk with the folks on the on the Both the conflict resolution the community health team Because we have now these examples that are in there I really think this is something we should be at least looking at Once a year You know and we don't necessarily need to make revisions every year, but we should at least be reviewing and You know seeing if there are new kinds of issues that are coming up, so I mean a great example would be An issue we have a lot right now. That's a very hot issue is people gaming the contribution credit system, right and That is something that like didn't exist ten years ago and and you know So we wouldn't have even thought to have included it Actually when we had our original code of conduct like social media wasn't even a thing, right? So and now it is like the number one vector of harassment. So So I think you do have to review You don't want this to be an ossified document. And so I am I'm hoping we can establish at least an annual Sort of cadence for reviewing And making changes if needed. Thank you Yes Yeah, I mean I am I'm happy. I've had actually a few conversations Over the last few days about how we can be Better and clear with our marketing not just in Drupal, but but in open source, right? And again, I think this goes to the fact that so many of us are Highly technical experts, right and when we when we think about things and communicate things we use Very precise very technical language. I get that that makes sense. It's very natural it is But not everyone in our community and not everyone in the world Processes language like that and so we need to make sure that we're being inclusive in terms of how we talk about What we do whether that's for documentation I think the documentation folks have been well down this path already And so I'm very grateful for that But I think you're absolutely correct that in terms of our our marketing and our community Communication there's there's a lot of room for improvement And I think that goes I think that's true for open source in general not just Our our little our little project here. So thank you. Yes Thank you