15:03:41 <spotz[m]> #startmeeting diversity-wg
15:03:41 <opendevmeet> 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 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:41 <opendevmeet> The meeting name has been set to 'diversity_wg'
15:03:57 <spotz[m]> #chair fungi
15:03:57 <opendevmeet> Current chairs: fungi spotz[m]
15:04:11 <spotz[m]> #topic roll call
15:04:56 * fungi reporting in
15:05:30 <spotz[m]> Let’s see if we have anyone else then I’ll tell you my idea
15:05:50 <fungi> the suspense... ;)
15:06:21 <spotz[m]> Hehe
15:06:52 <spotz[m]> #topic CoC teams at OpenInfra Days
15:07:47 <spotz[m]> 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 <spotz[m]> But as you know there’s often lots of people in staff shirts at events
15:09:02 <spotz[m]> 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 <fungi> 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 <fungi> would continuing that at openinfradays be the recommendation?
15:12:06 <fungi> i guess we haven't done that at oidays events in the past?
15:12:27 <fungi> i know part of the new event strategy was to bring more of our standard summit practices to oidays events
15:12:35 <fungi> so including that would make sense
15:15:33 <spotz[m]> I think so, as I know most folks at the events probably dress up more then a staff shirt
15:16:08 <spotz[m]> Maybe beyond the staff badge a lanyard or something on it that can be easily seen from a few feet away
15:18:23 <fungi> 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 <fungi> (as well as reminding attendees of where they can e-mail reports of coc violations or related concerns)
15:19:07 <spotz[m]> It a small location that could be easier or harder. I just like the idea of consistency
15:19:35 <fungi> 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 <fungi> 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 <fungi> 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 <spotz[m]> 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 <fungi> 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 <spotz[m]> Just things I think of when I can’t sleep
15:30:21 <fungi> makes sense
15:31:31 <fungi> i'll also point the meeting log out to aprice and the events folks (helena et al)
15:31:49 <fungi> they may have additional ideas for how to improve this
15:32:58 <spotz[m]> 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 <fungi> yep, something we should definitely be going over with the local event organizers if we don't already
15:35:36 <spotz[m]> So that is what was on my mind this morning.
15:35:55 <spotz[m]> We should also make a push on the survey now that the page is up
15:37:27 <fungi> 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 <spotz[m]> I think that's all I had for today. You have anything?
15:45:06 <fungi> nope, thinking about next steps moving forward on the survey publicity was pretty much all i had at the moment
15:50:06 <spotz[m]> Ok let's end this and you can go continue prepping!
15:50:10 <spotz[m]> #endmeeting