15:06:00 <q5sys> #startmeeting Security (2022-08-11)
15:06:00 <zodbot> Meeting started Thu Aug 11 15:06:00 2022 UTC.
15:06:00 <zodbot> This meeting is logged and archived in a public location.
15:06:00 <zodbot> The chair is q5sys. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:06:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:06:00 <zodbot> The meeting name has been set to 'security_(2022-08-11)'
15:06:05 <q5sys> #meetingname security
15:06:05 <zodbot> The meeting name has been set to 'security'
15:06:14 <q5sys> #chair q5sys
15:06:14 <zodbot> Current chairs: q5sys
15:06:17 <q5sys> #link Temporary issues location : https://pagure.io/Fedora-Security-Team/issues
15:06:29 <q5sys> #topic Open floor to discuss anything security related
15:06:34 <q5sys> #info I will be away next week, so the next meeting will be August 25th.
15:16:02 <jforbes> that works. doesn't seem like there has been much to discuss
15:17:41 <kitsu> I could do with some direction as to actively contribute to the spin
15:17:50 <kitsu> any information would be welcome
15:18:46 <q5sys> jforbes: yea, its been mostly quiet... I was thinking of going to every other week anyway... but then I dont want to end up forgetting since its not a weekly thing. haha
15:19:22 <jforbes> I think every other week works. Also useful to send a meeting reminder/agenda to the list
15:19:23 <q5sys> I might do an every other one week for the sec team... one week for the security lab spin since im not doing both #volunteering_for_too_many_things
15:19:25 <q5sys> haha
15:19:45 <jforbes> might get more people involved.  People meaning to attend who forget, etc.
15:19:59 <q5sys> kitsu: i havent had to much time to think about the spin stuff right now.  but I think the first step for the spin would be to review all the ansible scripts and other stuff that's in the pagur repo and make sure its up to date.
15:20:15 <kitsu> I am freeing up a couple of hours a week to contribute and I am putting together a blog post for colleagues who want to help out
15:20:19 <q5sys> jforbes: good point, I'll try to remember to message to the mailing list.
15:20:35 <kitsu> sounds good - I can take a loo this weekend
15:20:43 <kitsu> *look
15:21:00 <q5sys> kitsu: the other thing that probably should get some attention is what we briefly talked about before via email... scripting checking the RH security reports for closed issues and checking the Fedora tickets accordingly
15:21:13 <q5sys> which reminds me... I need to speak with Ben Cotton regarding that as well.
15:21:44 <kitsu> I can help with that too - the rest api I sent you also has the bugzilla ID in the feed which is useful
15:22:28 <kitsu> I could put something together in python to compare the two
15:31:29 <q5sys> Nice.  I've been meaning to look into that... but last month and this month are insane for me. I'm looking forward to Sept when things slow down for  me a bit.
15:31:30 <q5sys> Right now I'm streatched pretty thin between both jobs.
15:31:43 <q5sys> <kitsu> "I could put something together..." <- yea python makes the most sense.
16:03:57 <q5sys> Anywho I'm going to close this meeting out.  But as always, the channel is always open for anyone to talk or throw out ideas.  Whatever comes up during the week will get covered and talked about in more detail with anyone around during the next meeting.
16:04:08 <q5sys> #endmeeting