 Alright, so welcome. We have 20 minutes, half session, so this is gonna be the challenge round for the community working group. Fostering community health and demystifying us, or half of the community working group right here. So Jordana and myself will kind of take you through what we've been up to the past year and kind of where we, the direction we're heading in in the future. We're gonna have the, or you can contact us, sorry, you can contact us via Twitter handles or I think that's your Drupal level username as well. No, my Drupal username is Jordana. So contact us afterwards if you have any additional questions about anything. So for those of you who aren't familiar with the community working group, this is our mission, or part of our mission I should say, our summary of our mission. We're here basically promote community health and uphold the Drupal code of conduct. We often read this as both proactive and reactive, which I don't think I've used those two words more in my life than within the context of the community working group. So upholding the Drupal code of conduct involves a lot of times where there is an issue in the community that comes to our attention that someone is behaving in a way that is in direct conflict with the code of conduct and we need to get involved and have a conversation and see if we can't write that ship. And then the other half we see as proactive where we try to provide resources to help promote community health. So just a couple of bullet points here. I'm not going to go very deep into any of these but we did want to mention a few of the things that we do and that we have been doing lately. We are now committed to publishing an annual report. This kind of came out of the community discussions a couple years ago and these are a lot of this is focused on statistics about the types of reports that we get. Whether they're conflicts and issue queues or something happening in a Slack channel or some other Drupal space. So we're actually just about to start the annual report for this year. This year we also published a code of conduct template and playbook for Drupal events. So if you are Drupal event organizer and you need a resource for having a code of conduct for your own event. We have this information. We have links I'll put up here in a minute. We can get all this stuff. We're also we've organized code of conduct contact training. So we are encouraging all Drupal events to send their code of conduct contacts to this training. It's an online half day training. Jordan had just went through it. I'm actually due to go through it next month. Sorry about that. We are working on updating the Drupal code of conduct which is no small job. The last time the code of conduct was updated was right around five or six years ago. I think it was around the time that the community working group started going. So there was a survey earlier this year. We're looking into code of conducts from other open source communities and we're trying to figure out the best path forward on that. We updated our charter within the past year. The big difference there was we no longer escalate or report to Drees. We now have a review panel consisting of the two community elected board members of the Drupal Association. And then a third person nominated and placed in the position by the Drupal Association. And that is someone who is not part of the Drupal community. So currently that role is filled by John O'Bacon who is, I don't know what's the best way to do that. He's a great open source community health advocate and ambassador. Right, thank you. Yeah, so I'm going to let Jordana take over here for a minute or two. Thank you. We've noticed that a lot of people don't want to file reports with us because they're not sure if they have concerns but if the concern is large enough. So we wanted to call attention to the fact that we have a little checkbox that says we want you to be aware of this but not necessarily take action. So this is great for us to sometimes see patterns of behavior we wouldn't normally see. So something small for you, if it happens consistently over time it has an accumulative effect and it might be a pattern of behavior that is more concerning and of a larger something that is actionable that we can maybe stop before it becomes something bigger. Yeah, a lot of times these are things that are brought to our attention directly by seeing us in person and the conversation usually starts with something along the lines of there's this thing happening and I'm not sure if it's actually a thing or if I'm not sure if it's appropriate or I'm not sure if you know what this what the deal is. So stuff like that is we appreciate because it allows us to often get ahead of things before they actually become a real issue. So speaking of that sometimes when things become real issues we have to sometimes take action and maybe ask certain people to either refrain from coming to events or maybe ask them to step down from leadership decisions. But we are of the opinion like we strongly feel that people can make mistakes everybody makes mistakes but they should have a way back and a way to rectify those mistakes and be able to rejoin the community if they do the work. So this has always been a kind of a balancing activity for us for how do we balance accountability but also have that door open that if they want to change and if they want to make be a better community member that they should have the option to do that. So we have a blog post that we recently submitted it's all it's links over there with our thoughts and the process we do. We've been through this process with more than a few people it's not easy it's not quick and very few people are willing to do the work once they realize once we talk to them about what the expectations are. So we have a very high bar basically what we think and rejoining and getting out back so this is why not everybody chooses to continue. Yeah so we encourage you know we know that this has been something that I know that community members have asked me about and I'm sure Jordana as well and the other two members of I should probably mention the other two members of the CWG. I need to go back and fix the recording. So our chair is George DeMett from Palantir.net and Alex Burrows from the UK is the fourth member of the community working group. So the four of us I'm sure I know I can speak for myself and Jordana can speak for herself here but we've definitely had conversations about this about people re-entering the community and it's there's there's a lot of emotion involved with it and we we greatly value as we do with all issues involving conflict resolution we greatly value confidentiality. We want people to feel comfortable talking to us and not feel that we are going to you know violate their privacy. So a lot of times it's difficult for us to talk about so we wanted a way for us to be able to to to provide something back to the community about what that process looks like. So the result of that is this is this blog post which I think pretty accurately reflects you know what we feel and how difficult the process actually is for people to go through and it's you know it's not easy it's not easy for any of us even the ones who are not going through the process but helping to guide the process. So the other thing that we have going on and this has been going on for a couple of months we've been talking about it for a little bit longer but currently we're four members and we are all part of the conflict resolution team and every other team that the CWG has meaning we do both proactive and reactive and honestly we do proactive as time permits. The proactive stuff is that the code of conduct contact training or the code of conduct playbook and template or these blog posts we have a we have a list of blog posts that we should write that's you know probably six or seven blog posts long and we've been struggling with how can we expand in a healthy way to be you know pretty frank about it. We know that coming into the CWG and you know immediately doing conflict resolution is difficult at best you know Jordana and Alex have been the two most recent members and it's you know it's being thrown to the wolves a little bit. So we've thought about that and we've talked to some community members and what we've decided to do is we've decided to pursue a role based expansion and Tara is actually helping us with this we've been working with Tara for over a month now at least I would say talking about it but number one these you know these roles are separate and not involved with the conflict resolution tasks. We're seeing this as a gentler introduction to the CWG just from a workload and a knowledge standpoint as well as from a privacy standpoint so new members of the CWG who are not in the conflict resolution role will not have access to that information so we're kind of siloing off the conflict resolution aspect of it but we have and we are in the process of defining a bunch of other roles that we are looking going to be looking to fill over the next few months. Some of these already kind of unofficially exist or officially we call we have several geographic slash cultural folks to help us out we call them subject matter experts they're not members of the CWG but they are trusted community members we have interviewed and talked to and when we have an issue that involves a geographic region or a culture that one of us is not familiar with we kind of bring them into that issue and they they have to abide by the same code of ethics that the rest of us do as far as privacy but we kind of want to expand that we want to kind of we want to have a bigger roster for that and make sure we cover the you know the regions and the cultures that that are necessary for our community. We're gonna have a membership role filled by Tara King initially Tara King who's going to help us define and fill these roles. Yes, thank you. It's not like she isn't doing enough but thank you. The one that we probably I think is going to give us the biggest bang for the buck initially is the community health initiatives and these are all the proactive things that we want to be doing that we don't have time for. These are the things like organizing more workshops at Drupal Cons and hopefully some of the other Drupal events around the world. These are things like providing more resources on Drupal.org for for community members you know under the purview of community health. There's some great ideas that came out of Drupal Con Seattle where I can never keep track of the previous Seattle. Thank you. About things we can do in the issue queue and possibly on Slack to help you know when when a conversation starts going sideways a little bit we call them nudges to gently nudge the conversation back and remind folks of the code of conduct. So there's these really great ideas but we don't have the four of us do not have the time to implement them so we're looking for folks to you know who are willing to kind of help with those efforts. Group liaisons. So a lot of times we have to interface with various other parts of Drupal whether it's the Drupal Association whether it's a working group whether it's you know a bunch of camp organizers. So we're looking to kind of fill the pre-fill those roles so that when there is an issue we already know who we can go to talk to and they know how we operate and things like that. One that I know the four of us are crazy excited about is this last one the open source community health ambassador. We have had ad hoc discussions with members from other open source communities about code of conducts and process structure and in this area we are from what we've seen we are far ahead of other open source communities in the way we're in our structure and our process and our documentation. So we are often in the position of giving out advice to other open source communities when it comes to community health and code of conduct and things like that. So we see it we see that there's a huge opportunity to kind of create as George our chair calls it the UN of open source community health. Representatives from different open open source communities coming together exchanging knowledge and basically you know a rising tide will lift all boats. This is something I think any one of the four of us would jump at to do if we could. But we're really excited about this and we think that this could gain traction fast among open source communities with Drupal being the leader. So we are you know we are open to all ideas and if you or someone you know might be interested in working with us on feeling one of these roles or ideas on something that we missed please let us know. We are you know we have a fairly good idea of the direction we're going but it's not too late to you know to give us ideas that will you know causes to stop and think and and answer some new stuff. And we hear the thing like a lot of people tell us we would I would I'm really interested in helping you guys but we don't have I don't have a time. A lot of these roles we're seeing as kind of team roles are and I forget what you call it where it's a time-based so it's going to be like a maybe a one-month period here and so it is it is we're trying to make it so that it's going to be as we work well as well as possible for people where we're not overloading anybody. We're going to try not to do that as much as possible. Right something Tara and I have talked about and we've talked about internally as well is we want to create on ramps and off ramps for all of these roles most selfishly the conflict resolution as well. So we want you know we want people to be able to kind of cycle into these roles get the information they need and not have it being in it not having it be an indefinite time period like saying you're going to be in this role for a year or however long you're comfortable but one of your tasks is going to be identify who's going to fill in behind you and get them ready so we kind of want to learn that process and learn what we need to have in place to facilitate that process but as you know the role that we're in you know sometimes it seems like it's inescapable which you know that's one of the reasons why we feel it's important that we need to kind of bake that type of thing in from the beginning to get that in kind of into the CWG DNA. Alright so here are the links I promise the bitly links are case sensitive so everything is basically under the Drupal community working group on Drupal.org there's a link there to all of our blog posts the code of conduct resources this is for camp organizers is at the second link and then the camp organizer speaker diversity workshop which I should probably just let Tara talk about that Sure, we are helping provide training. We are providing a free three-hour training on November 16th. Thank you on Zoom so anyone in the world can take it it will give you the resources you need to help underrepresented people in your community develop talks and pitch them to your local camp. It's so good I like I'm not the one who made the training so I feel like I can say that it's just sign up here and it's we it's from the WordPress community they had huge results from it so it's like a proven model very exciting. Alright so I know we only have like a minute and a half left so questions everyone. So with the recent change in the charter media at large members does that open up opportunities to have a budget? Do you have any ideas that you would bring to them? So there were a couple driving reasons why we changed the charter. Number one was the report you know our escalation point you know it was clear that Drees didn't want to be in that position anymore the community felt it needed to be more representative of the community so we came up with this idea of well we have two members of the community who are elected to a board so that was our starting point so that was one aspect the other aspect was there are definitely issues where sometimes we need to consult with you know an attorney. So by co-ing under the DA it made it very easy for us to be able to ask the DA if we could have some time with the attorney before we respond to an issue. And very legally protected now so people can't sue us yes personally. And it also does open up for us to request funding from the DA. We actually have we had our introductory call with Heather not too long ago the new executive director of the DA where we had very initial discussions about you know the types of things that we were hoping to be able to request. It's like funding for training but funding for like our slack for example so we can have other people in there without them seeing channels they shouldn't be seeing for example. Yeah. We should probably wrap up if anybody else any questions grab one of us outside tomorrow or Thursday. I find this online as any ideas any suggestions anything. Me too. I'm sparkling robot on the Internet or in the hallways. If you want to talk about membership stuff. If you're interested in getting involved. Yes. I should have put you I'm sorry Tara I didn't even think about. We talked about this two hours ago. We weren't definitely prepared before two hours ago. Sorry. Thank you very much. Thank you.