19:00:57 <jillr> #startmeeting Ansible Diversity Working Group | Agenda: https://github.com/ansible/community/issues/577
19:00:57 <zodbot> Meeting started Thu Mar 18 19:00:57 2021 UTC.
19:00:57 <zodbot> This meeting is logged and archived in a public location.
19:00:57 <zodbot> The chair is jillr. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:57 <zodbot> The meeting name has been set to 'ansible_diversity_working_group_|_agenda:_https://github.com/ansible/community/issues/577'
19:01:03 <jillr> #chair misc cybette
19:01:03 <zodbot> Current chairs: cybette jillr misc
19:01:13 <jillr> o/
19:02:00 <jillr> #topic update on CoC response training
19:02:12 <tadeboro> I will be in read-only mode today becasue DadOps.
19:02:22 <jillr> #chair tadeboro
19:02:22 <zodbot> Current chairs: cybette jillr misc tadeboro
19:02:25 <jillr> no worries
19:02:48 <jillr> I talked to robyn this week, we can get budget for a future otter tech CoC incident response workshop
19:03:09 <misc> good
19:03:14 <jillr> I need a list of folks who would like to be a part of the CoC response team (and take that training) to get started
19:03:17 <misc> (I forgot to ask my boss)
19:03:23 <cybette> great!
19:03:52 <jillr> gundalow and cybette had previously expressed interest, so I've got you noted
19:04:06 <cybette> thanks, I was just about to volunteer us two :)
19:04:10 <jillr> :)
19:04:29 <misc> are you still aiming for the training next month ?
19:05:08 <jillr> uncertain. robyn will need to do the budget and PO thing, if we have enough people we might try to do a dedicated class but we haven't actually talked to otter tech yet
19:05:50 <jillr> so lacking that info, assuming the April class is probably good?
19:05:58 <jillr> #link https://otter.technology/shop/2021-04-10-apr-10-code-of-conduct-incident-response-workshop/
19:06:28 <cybette> If Otter tech isn't in RH's vendor list it won't be so easy to do PO for dedicated class. However if they accept credit card payments then it shouldn't be a problem.
19:06:57 <cybette> I'm ok with the class on April 10
19:07:01 <misc> riecatnor, from Fedora team, had the teraining last sunday
19:07:08 <jillr> they appear to take credit cards
19:07:18 <misc> so if she was able to pay, I guess others RHer can :)
19:07:36 <misc> (riecatnor aka mnordin)
19:08:04 <cybette> ok good. yeah paying with CC is straightforward. it's when you try to do the PO route with unapproved vendors that's a pain :P
19:08:42 <misc> yeah and when the price is over a limit
19:08:50 <cybette> right
19:09:17 <jillr> so for now it sounds like cybette, gundalow (presumably), and myself will attend the training (and maybe some internal folks who aren't in this meeting, I have to broadcast the option there)
19:10:10 <jillr> anyone else who wants to attend please let me know by end of this week (Friday Marth 19th)
19:10:19 <jillr> *March
19:11:26 <jillr> #topic update on CoC recipient list
19:11:59 <jillr> robyn is opening a ticket with RH IT to get gundalow and I added as recipients to codeofconduct@ emails to start.
19:12:18 <jillr> we can add any additional people who would like to be a part of a CoC Response/Safety team once that list of people is identified and trained
19:12:45 <cybette> I'll feel more comfortable being added to the list after training
19:13:04 <jillr> this will apply to online incidents; response for in-person events like AnsibleFest goes to a different email alias that corresponds to the safety folks that RH sends to events
19:14:14 <jillr> physical security is a whole separate group of risks that we have specially trained people for
19:14:36 <jillr> so the community safety team would not be expected to deal with that
19:14:55 <misc> and in case of a hybrid online/physical event ?
19:15:42 <jillr> that's a really good question that I don't know the answer to
19:16:11 <cybette> right, when things starts happening in person again, I think it will be hybrid initially. Actually Ansible Contributor Summits have always had an online component in addition to F2F
19:16:17 <jillr> I would assume that any event which has that kind of response set-up would handle all reports?
19:16:43 <misc> also, the 2 team would communicate after and before ?
19:17:17 <jillr> seems sensible. I can try to find out!
19:18:13 <misc> in fact, I also wonder if the team in charge of RH summit would be the same as AnsibleFest
19:19:03 <jillr> I believe it's the same team from Events, but I don't know the team/proper name for the folks that do CoC/Safety at events
19:19:36 <misc> I guess that's the same team, but now, knowing RH, I wonder if that's not split by geo :/
19:20:04 * samccann waves really late
19:20:13 <jillr> #chair samccann
19:20:13 <zodbot> Current chairs: cybette jillr misc samccann tadeboro
19:20:17 <jillr> hi!
19:20:22 <cybette> hi samccann !
19:21:21 <samccann> hi all
19:22:49 <jillr> so it sounds like when Fest planning ramps up (or before then) we need to have a conversation with Events to make sure everyone is on the same page about responding to incidents
19:23:09 <cybette> +1
19:23:12 <misc> yeah
19:25:21 <jillr> that covers everything I had about the initial CoC team and training, anything else to discuss on the topic?
19:25:39 <cybette> yes, sorry I didn't put it to github in time, I have a topic
19:26:00 <cybette> #topic sponsoring PyLadies auction
19:27:12 <cybette> #link https://us.pycon.org/2021/events/auction/
19:28:07 <cybette> what do you all think about sponsoring the PyLadies auction? we are discussing our contributions to the PSF and we might have some budget for it, and Robyn and I want to do a diversity type sponsorship
19:28:42 <misc> pyladies is a good choice
19:29:02 <cybette> "This benefit includes: Logo on PyLadies page, Inclusion in blog post highlighting our sponsors, Logo on auction platform, On the schedule it will be listed as “PyLadies Auction, sponsored by XZY”, Anytime we mention the auction, we will say “PyLadies Auction, sponsored by XZY”, Shoutout during the event by the auctioneering team, Social media promotion of sponsorship.
19:29:02 <cybette> This a la carte benefit is $5,000."
19:29:19 <jillr> does Ansible sponsor the PSF independant of RH?
19:30:24 <misc> I am not sure of the status of RH sponsorship for the PSF
19:30:39 <cybette> no, previously the Ansible sponsorship is more about sending people to the event, providing swag etc. so this could be something we do independent of RH
19:30:44 <jillr> I don't see our logo on https://www.python.org/psf/sponsorship/sponsors/ at least; so this is a new contribution?
19:30:50 <jillr> gotcha
19:31:08 <jillr> I like the idea
19:32:06 <cybette> ok great, I will propose that we do it then.
19:32:33 <samccann> +1 on the sponsorship
19:33:08 <cybette> thanks for the input!
19:33:31 <jillr> thanks for the idea!
19:33:41 <cybette> :) I don't have anything else..
19:33:44 <jillr> #topic open floor
19:34:28 <samccann> is there something we could do/attempt like a 'get started in Ansible' session to bring in beginners to the code? Specifically diverse beginners?
19:34:51 <samccann> thinking like partner with blackgirlscode or something to have a mini hackathon/training? dunno
19:34:55 <samccann> just spitballing ideas
19:35:40 <jillr> we usually do a sprint/hackathon at PyCon is my understanding (if we're thinking the previous topic), or do you mean just generally do a hackfest?
19:36:03 <misc> I also do that when pycon.fr is in person, 2 days of sprint on modules
19:36:14 <samccann> my thought is to specifically open it up just to <insert diverse pool>
19:36:28 <misc> but it depend the type of begginers we are aiming for
19:36:33 <samccann> yeah so that same idea, but not open to everyone, open just to that diversity pool.
19:36:34 <jillr> #topic introductory hackfest for new (potential) contributors
19:36:52 <misc> (cause, fixing ansible is maybe not as sexy as creating a website for a total beginner in python)
19:37:27 <samccann> seems we do have stuff for new/potential contributors which is great. But can we do something for a select group that fits our diversity and inclusion goals to extend the kinds of people coding on ansible?
19:37:44 <jillr> I've done mentoring for openstack at that kind of introductory D&I hackfest and that was a lot of setup/explaining OS, I wonder how accessible hacking on Ansible is to a newer programmer
19:37:56 <jillr> (not that we shouldn't do it!)
19:38:01 <samccann> yeah that I dunno
19:38:03 <misc> working on modules is much easier
19:38:17 <misc> usually, just 1 single file to look at, no need to deploy/setup much
19:38:42 <jillr> maybe there are modules in community.general/community.network that need attention that would also be fairly accessible?
19:39:14 <cybette> this might involve working with existing diversity groups and offering to be part of their programs. because I don't see it going well if we say we're opening a course "just for group X, don't sign up if you don't fit this demographic!"
19:39:25 <jillr> +1
19:39:31 <samccann> yeah that makes sense
19:39:42 <misc> community.network would requires the network gear, and some network knowledge, not sure how begginer friendly it is :/
19:40:07 <misc> (like, some specific network knowledge, for the specific switchs)
19:40:25 <samccann> yeah we'd have to define who our target audience is. If it's coding beginners, then something more general would work
19:40:36 <samccann> if it's experienced coders but ansible beginners, then maybe it can be deeper
19:40:49 <misc> yeah
19:41:12 <misc> I think that's the public you get at pycon, folks who already know how to code and navigate a opensource project
19:41:27 <cybette> right..
19:41:34 <misc> now, training on using ansible is different
19:42:09 <misc> but I feel bad as it seems quite selfserving (which shouldn't be bad, cause that's good for the company that pay our paycheck, but still)
19:43:01 <jillr> do we have the necessary skills and resources to run a successful training program/workshop?
19:43:25 <jillr> vs partnering with an existing group to lead a hackfest
19:43:49 <misc> I think partnership is better
19:44:04 <jillr> offering training might be a good long term goal for the communiity
19:44:08 <samccann> partnering for sure. we've a lot to learn in this area it seems
19:44:13 <misc> I never heard people saying "we have too much mentor"
19:44:19 <jillr> +1
19:44:22 <cybette> +1
19:45:15 <jillr> I know the Grace Hopper Celebration conference has an open-source hackfest day, but I don't know if they're doing it for virtual events
19:45:33 <misc> also (speaking of selfserving), we had this ticket: https://github.com/ansible/community/issues/262
19:46:08 <jillr> oh neat
19:47:38 <cybette> I think this will require more thought and planning. but definitely something worth doing!
19:47:55 <samccann> cool
19:48:20 <jillr> agreed
19:48:29 <misc> I am personnaly quite unconvinced by remote hackfests
19:48:53 <samccann> yeah that could be hard
19:49:06 <samccann> wonder if we could do something with katacoda (sp?)
19:49:08 <jillr> indeed, I'm not excited by the idea of trying to troubleshoot a venv on someone's laptop that I can't see in real time
19:49:24 <samccann> where the community team is building up training.
19:49:27 <jillr> or some of the other things noted in this ticket
19:50:06 <cybette> if most of the participants are experienced, it's probably doable remotely. but otherwise yeah... not the best way
19:50:08 <jillr> I know Red Hat has training and things on katacoda, is the community team doing extra things?
19:50:14 <misc> samccann: it would work, minus the part where you have to edit a file in vim on katakoda :)
19:50:28 <misc> but at least, katakoda could help for the dev setup
19:50:39 <misc> like venv + hackingsetup + testing ansible work
19:50:58 <cybette> we tried out Katacoda for last year's contrib summit and it was well received. we are thinking of putting more training up there (also a question of resources to produce said trainings)
19:52:23 <cybette> this is the only scenario we currently have: https://www.katacoda.com/ansible-community/scenarios/fixing-a-bug
19:54:54 <jillr> all good ideas, anything else we should discuss on the topic?
19:56:24 <jillr> #topic open floor
19:56:39 <jillr> last call for today!
19:59:08 <jillr> #endmeeting