15:03:41 #startmeeting diversity-wg 15:03:41 Meeting started Tue Jan 9 15:03:41 2024 UTC and is due to finish in 60 minutes. The chair is spotz[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:41 The meeting name has been set to 'diversity_wg' 15:03:57 #chair fungi 15:03:57 Current chairs: fungi spotz[m] 15:04:11 #topic roll call 15:04:56 * fungi reporting in 15:05:30 Let’s see if we have anyone else then I’ll tell you my idea 15:05:50 the suspense... ;) 15:06:21 Hehe 15:06:52 #topic CoC teams at OpenInfra Days 15:07:47 So while discussing the CoC for Texas Linux Fest it was pointed out that it states you can report things to folks in staff shirts 15:08:11 But as you know there’s often lots of people in staff shirts at events 15:09:02 What about having a consistent color and design for the CoC folks across all events. Or even for those who don’t wear staff shirts a consistent badge 15:11:25 at the summits, we've instructed attendees that they can report violations to anyone wearing a "staff" badge (which were already different colors than regular attendee badges) 15:11:38 would continuing that at openinfradays be the recommendation? 15:12:06 i guess we haven't done that at oidays events in the past? 15:12:27 i know part of the new event strategy was to bring more of our standard summit practices to oidays events 15:12:35 so including that would make sense 15:15:33 I think so, as I know most folks at the events probably dress up more then a staff shirt 15:16:08 Maybe beyond the staff badge a lanyard or something on it that can be easily seen from a few feet away 15:18:23 also we make sure there are fixed locations where reports can be made, so that you don't have to hunt down someone in a particular shirt or with a specific badge color 15:18:57 (as well as reminding attendees of where they can e-mail reports of coc violations or related concerns) 15:19:07 It a small location that could be easier or harder. I just like the idea of consistency 15:19:35 yeah, i do too. just trying to figure out what options we might have, and how much of that we might already be doing in other contexts 15:20:46 the foundation staff members have a lot of varied tasks at events, because we're such a small team, so putting them in uniforms all the time is unlikely to work out 15:21:54 but for example, if the staff badges aren't visible enough, then we should be able to find ways to improve on that 15:22:29 Well I was even thinking while a few staff might get to the events we need to think about the local organizers and making sure they’re good to go. Hence why I was looking for consistency if say Alison wasn’t there and that’s who someone was looking for 15:25:42 yes, well making sure we clearly identify who at an event can receive coc-related concerns is very important (you're right it might not be just foundation staff members, or there may even be no foundation staff members at some events) 15:29:47 Just things I think of when I can’t sleep 15:30:21 makes sense 15:31:31 i'll also point the meeting log out to aprice and the events folks (helena et al) 15:31:49 they may have additional ideas for how to improve this 15:32:58 And while there are professional courses on reporting having a pre-event review of the CoC and how to take reports would be good 15:33:35 yep, something we should definitely be going over with the local event organizers if we don't already 15:35:36 So that is what was on my mind this morning. 15:35:55 We should also make a push on the survey now that the page is up 15:37:27 yep, i agree, we're now set up to be able to easily point project participants there and encourage them to take the survey and get more involved 15:44:31 I think that's all I had for today. You have anything? 15:45:06 nope, thinking about next steps moving forward on the survey publicity was pretty much all i had at the moment 15:50:06 Ok let's end this and you can go continue prepping! 15:50:10 #endmeeting