20:00:30 <bcotton> #startmeeting FPgM office hours
20:00:30 <zodbot> Meeting started Wed Mar 30 20:00:30 2022 UTC.
20:00:30 <zodbot> This meeting is logged and archived in a public location.
20:00:30 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
20:00:30 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:30 <zodbot> The meeting name has been set to 'fpgm_office_hours'
20:00:31 <bcotton> #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc)
20:00:31 <bcotton> #chair bcotton grahamwhiteuk dtometzki glb pawelzelawski q5sys siddharthvipul x3mboy
20:00:31 <bcotton> #topic Announcements
20:00:31 <zodbot> Current chairs: bcotton dtometzki glb grahamwhiteuk pawelzelawski q5sys siddharthvipul x3mboy
20:00:37 <bcotton> #info It's "unsynchronized summer time changes" season: https://discussion.fedoraproject.org/t/reminder-summer-time-changes-coming-up/27831/3
20:00:55 <bcotton> #info F36 Beta was released yesterday
20:00:55 <bcotton> #info F36 Final freeze begins Tuesday 5 April
20:00:55 <bcotton> #link https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
20:01:01 <bcotton> #help F36 Wallpapers test day is tomorrow: https://fedoraproject.org/wiki/Test_Day:2022_03_31_F36_Wallpapers
20:01:01 <bcotton> #help Kernel 5.17 Test Week is next week: http://fedoraproject.org/wiki/Test_Day:2022-04-03_Kernel_5.17_Test_Week
20:01:01 <bcotton> #help Fedora CoreOS Test Week is next week
20:01:01 <bcotton> #help Fedora IoT Test Day is 6 April
20:01:09 <bcotton> #help Submit your ideas for the Fedora Magazine "Feature Spotlight" series: https://communityblog.fedoraproject.org/collecting-ideas-for-feature-spotlight-articles/
20:01:14 <bcotton> #info The F36 Release Party will be 13–14 May: https://communityblog.fedoraproject.org/youre-invited-to-the-fedora-linux-36-release-party/
20:01:17 <bcotton> #info Registration for the Fedora Mentor Summit is open
20:01:17 <bcotton> #link https://communityblog.fedoraproject.org/fedora-mentor-summit-is-here/
20:01:25 <bcotton> #info the Mentor Summit is Friday and Saturday
20:01:32 <bcotton> #info The Fedora Ambassador Call kickoff will be held at 1500 UTC on Thursday 31 March
20:01:32 <bcotton> #link https://communityblog.fedoraproject.org/fedora-ambassador-call-kick-off/
20:01:39 <bcotton> #info The Fedora Social Hour is tomorrow: https://matrix.to/#/#social:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org
20:01:44 <bcotton> #info If your team wants support from the Fedora Program Management Team, file an isssue: https://pagure.io/fedora-pgm/pgm_team/issues?template=support_request
20:01:44 <bcotton> #topic Open floor to discuss anything program management related (elections, changes, schedule, etc)
20:05:43 <q5sys> Ben Cotton (he/him):  Are we going to moving out PgM repo to gitlab as well?  I ask since you had mentioned using a kanban board for the service security work.
20:06:42 <q5sys> s/out/our/
20:06:44 <bcotton> i don't have any plans to move it at this point, although id suggest tracking the service security stuff in it's own repo
20:07:54 <q5sys> Makes sense
20:11:05 <q5sys> I reached out to the security mailing list about joining... and it's been two weeks.  I know people go on vacations and such, but I've been checking for the security meetings according to when the docs say they are... and they havent been happening.  Which then raises the obvious question.  Do we really even have a sec team anymore?  Obviously OS wise the majority of things will be handled by Red Hat employees upstream.
20:11:55 <q5sys> Im guessing on the Fedora Side of things, mostly any security stuff would be coordination and tracking that things are dealt with when serious matters arise.
20:12:25 <bcotton> i don't think the security team is particularly active (although i'm surprised that it's entirely a ghost town)
20:12:46 <q5sys> the docs page doesn't list any members
20:12:50 <q5sys> so I dont even know who to reach out to.
20:14:37 <bcotton> David Kaufmann (FAS astra) was trying to restart the team last spring according to my email archives
20:14:49 <bcotton> but i haven't heard anything more from him in a while
20:16:00 <q5sys> I wonder if he's Astranox on libera.chat  If so... I'll reach out to him and see what his ideas are.
20:16:10 <bcotton> .fasinfo astra
20:16:11 <zodbot> bcotton: User: astra, Name: David Kaufmann, Email: astra@ionic.at, Creation: 2013-11-27T10:53:26, IRC Nicks: None, Timezone: Europe/Vienna, Locale: en, GPG Key IDs: 5CBED71B23D2450E, Status: None
20:16:14 <zodbot> bcotton: Groups: fedora-contributor, fedorabugs, packager, security-team
20:16:25 <q5sys> If he's trying to restart the team I'm happy to pitch when I have time.
20:16:25 <bcotton> no nick :-(
20:16:43 <q5sys> I'll take the direct route and ask him when I see him active next. :)
20:17:11 <bcotton> I also know that Red Hat Product Security assigned a new security architect for Fedora, but he hasn't gotten settled yet
20:17:45 <bcotton> i'm not sure what his role will be, but if he'll be actively participating, i'll make an introduction
20:17:55 <q5sys> Please do.
20:19:21 <q5sys> I want to make sure I get all the ducks in a row so to speak before moving forward on the issue.  Because it's such a big task, I'd like to have some general agreement on the task and the best way to proceed, before I start submitting PRs with no real focus or direction.
20:19:47 <bcotton> i get the sense that the focus/direction will be whatever you decide it is, for better or worse
20:20:18 <q5sys> true... but sanity checks from people that may be wiser than I is always a good thing. haha.
20:20:32 <q5sys> if Im going to do this... i want to do it right.
20:25:42 <bcotton> yeah, makes sense
20:26:07 <bcotton> even a check from someone less wise than you can be helpful
20:26:15 <q5sys> I dont want to forever be know as the guy that f'd up the service permissions in Fedora. ;)
20:29:01 <bcotton> at least you'd be known!
20:34:49 <q5sys> I'd rather be unknown than be infamous. lol
20:38:46 <bcotton> :-)
21:04:30 <bcotton> #endmeeting