17:00:23 <fungi> #startmeeting diversity-wg
17:00:23 <opendevmeet> Meeting started Mon Oct  4 17:00:23 2021 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:23 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:23 <opendevmeet> The meeting name has been set to 'diversity_wg'
17:00:30 <fungi> #link Meeting Agenda: https://etherpad.openstack.org/p/diversity-wg-agenda
17:00:37 <fungi> #chair spotz
17:00:37 <opendevmeet> Current chairs: fungi spotz
17:00:56 <fungi> #topic PTG
17:02:08 <fungi> the ptg is coming up in a couple weeks, i know spotz reserved us some time, i don't see any indication on the agenda that we've got a ptg planning document anywhere yet to collect ideas for what we want to discuss
17:02:58 <fungi> i recall a meeting or two back it was suggested that we take the opportunity to review the various codes of conduct (foundation coc, community coc, event cocs)
17:05:04 <fungi> we also talked about maybe taking some time together to look through example uses of terms identified through the earlier inclusive terminology effort, and try to identify some low hanging fruit or other opportunities for contributors to tackle those
17:06:31 <fungi> i did a bit of that a while ago, just basic queries in the opendev codesearch, to try and get some idea of what's likely to be involved
17:07:07 <fungi> but it might be good to work through some specific examples in our projects to get a clearer picture
17:08:08 <fungi> since i'm not sure whether i'm the only one around at the moment, i'll give others in the channel a chance to catch up and comment
17:13:46 <fungi> seeming like maybe it's just me at the moment, so i'll confer quietly with myself on this topic until spotz is back
17:17:47 <fungi> from the looks of the agenda etherpad, lisa is trying to join but maybe going to the wrong place. i tried to provide some guidance there
17:20:29 <spotz_> Hey, I’m running a little late but logged in from phone
17:20:42 <SWDevAngel> Me too.
17:20:54 <fungi> oh hi there
17:21:04 <SWDevAngel> Having trouble logging in from computer so just on phone today.
17:21:10 <spotz_> Hey fungi
17:21:16 <SWDevAngel> Hi Fungi
17:22:08 <fungi> spotz_: SWDevAngel: this is what i've covered so far: https://meetings.opendev.org/meetings/diversity_wg/2021/diversity_wg.2021-10-04-17.00.log.txt
17:25:13 <spotz_> So PTG we’re probably meeting too early for you swdrvangel but TC is having an open leadership in the slots after ours
17:25:51 <spotz_> I was hoping we’d get some early logins
17:27:37 <spotz_> I’m hoping we can make some progress on naming but we still don’t have the stance online yet
17:29:26 <spotz_> Grr
17:29:36 <SWDevAngel> ;)
17:31:46 <spotz_> Missed any responses
17:32:42 <fungi> nope
17:34:50 <spotz_> Ok I’ll try to email out an invite to our time slot with a copy of the stance in it this week. I’ll be in LA next week and still need to come up with a social for the PTG
17:37:28 <spotz> Anything else we want to try to do for the PTG?
17:37:30 <fungi> #chair spotz_
17:37:30 <opendevmeet> Current chairs: fungi spotz spotz_
17:37:43 <fungi> (didn't add your _ nick earlier)
17:38:30 <fungi> so far we talked about reviewing the various codes of conduct, and working through some specific examples of updates to projects for inclusive terminology
17:38:58 <fungi> i don't remember any other ptg topic ideas floated yet
17:40:11 <spotz> I was hoping we'd get some of the projects to stop by and work through their naming issues. Maybe just concentrating on the CoC stuff would be a better use of our time though
17:41:09 <fungi> well, if nobody stops by with specific examples, we can find examples to discuss via codesearch and one of us can push up some patches
17:42:14 <fungi> i think it's a good opportunity to at least raise those examples to the broader community via mailing lists or whatever in order to demonstrate that they're in many cases simple introductory fixes for new contributors to cut their teeth on
17:43:05 <fungi> that will hopefully spur on some progress
17:43:40 <spotz> Ok soo we'll invite folks, and if not we'll do the codesearch and patches, and the CoC
17:43:55 <spotz> Once finalized we can make an etherpad
17:44:12 <fungi> the coc situation is evolving too, we've got a new url and have been pushing changes to project sites and docs to update that
17:44:47 <fungi> the foundation executive management team has been coordinating with legal counsel to update a lot of the existing legal documents in the wake of the name change
17:45:10 <fungi> so this is probably a great time to bring up other changes which might be warranted
17:45:20 <SWDevAngel> Cool
17:45:38 <SWDevAngel> Spotz I’ll be in LA next week also. :)
17:45:54 <spotz> SWDevAngel: Sweet we'll need to meet up
17:46:17 <fungi> i love louisiana, jealous!
17:46:39 <spotz> fungi: yeah that's one of the reasons the stance has no home yet
17:46:42 <spotz> fungi: hehe
17:46:48 <fungi> (well, really mostly new orleans)
17:47:53 <SWDevAngel> Ha ha. WISH I was going to the state LA not the city!!! ;)
17:47:58 <spotz> I want to go to NOLA and break my diet:)
17:48:15 <fungi> spotz: the reshuffling of legal docs and moving of the codes of conduct is part of it, but also that the statement of support for inclusive language isn't a legal document the board ratified, so it's not actually tied to the foundation bylaws like the coc and other things in the legal document set
17:48:28 <SWDevAngel> Instead we’ll be in CALA… funny. Never called it that before.
17:49:40 <fungi> i was trying to push for a board vote on that statement of support, but nobody seemed to think it was worth voting on
17:50:23 <spotz> Yeah the answer I got was that it was approved no vote needed.
17:51:36 <spotz> #link - https://etherpad.opendev.org/p/yogaptg-d%26i
17:52:06 <fungi> but not ratified as a motion, so not published as an actual statement from the board
17:52:26 <fungi> there is basically still no official record of it, as a result
17:53:11 <fungi> if it were a resolution, it would have at least appeared in board meeting minutes
17:55:19 <spotz> IIt should have at least been in the minutes
17:57:05 <fungi> as far as i know the text of the statement was not included in the minutes (the text of a resolution would have been)
17:59:34 <spotz> Ok I can see that. It was brought up in a meeting, I gave updates to it, and we all agreed to it in email with maybe only a brief final message but nothing was ever read or included in the minutes with the actual contents
18:00:57 <fungi> yeah, hard to see it as an actual statement made by the board if there was no resolution, but also it would have had the side effect of the text actually being published as part of the proceedings
18:02:17 <spotz> I think for now we just push forward with atleast getting it on a secured wiki page no one can just edit and we'll focus on stuff we can get done like straightening up the CoC issue
18:02:59 <fungi> i can do that at any time. setting the protected flag on a wiki page is just a click for me as a wiki moderator
18:03:45 <spotz> fungi: Let's go ahead and get that done and links to the word suggestions we'd done and maybe the CoC?
18:07:55 <fungi> sure, happy to
18:09:31 <spotz> Thanks, it'll at least give us a little closure to this
18:09:40 <fungi> oh, also before we close the meeting, a link to the new community coc location...
18:09:42 <fungi> #link Open Infrastructure Foundation Community Code of Conduct: https://openinfra.dev/legal/code-of-conduct/
18:10:02 <spotz> And are all projects using that one?
18:10:32 <fungi> they either already link to it or have changes proposed for their web sites to switch the url. but also the old url now redirects to that
18:10:53 <spotz> It's definitely a more indepth CoC
18:11:36 <spotz> OOk let me close the meeting out
18:11:40 <spotz> #endmeeting