20:03:39 <bcotton> #startmeeting FPgM office hours
20:03:40 <zodbot> Meeting started Wed Sep  1 20:03:39 2021 UTC.
20:03:40 <zodbot> This meeting is logged and archived in a public location.
20:03:40 <zodbot> The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:03:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:03:40 <zodbot> The meeting name has been set to 'fpgm_office_hours'
20:03:51 <bcotton> #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc)
20:04:04 <bcotton> #chair bcotton grahamwhiteuk dtometzki glb ramyaparimi pawelzelawski q5sys siddharthvipul x3mboy
20:04:04 <zodbot> Current chairs: bcotton dtometzki glb grahamwhiteuk pawelzelawski q5sys ramyaparimi siddharthvipul x3mboy
20:04:06 <bcotton> #topic Announcements
20:04:13 <bcotton> #info The F35 Beta freeze is underway. All Changes should be 100% code complete (BZ tracker status ON_QA
20:04:18 <bcotton> #info The current Beta release target date is the Early target (Tue 2021-09-14)
20:04:26 <bcotton> #link https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
20:04:28 <bcotton> #help Let me know what tasks need to be changed before I create the next three years worth of release schedule: https://communityblog.fedoraproject.org/time-to-make-new-release-schedules/
20:04:34 <bcotton> #info Project suggestiosn for the next Outreachy round are due 20 September: https://pagure.io/mentored-projects/issues
20:04:41 <bcotton> #info The Fedora Social Hour is tomorrow: https://matrix.to/#/#fedora-social-hour:matrix.org
20:04:47 <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:04:56 <bcotton> #topic Open floor to discuss anything program management related (elections, changes, schedule, etc)
20:08:11 <nirik> bcotton: I got one for you... or your FPgM minions... :) What would you think of pinging in and culling tracker bugs against distribution every say... year? there's some I am sure are no longer used/active.
20:09:34 <bcotton> nirik: that's a good idea for a post-release task. a lot of them probably get swept up in the EOL closure, but i saw you closing a few that don't really make sense to leave open after the release day
20:10:12 <nirik> well, there's some generic ones that are old and very likely dead...
20:10:37 <nirik> like...
20:10:41 <nirik> .bug https://bugzilla.redhat.com/show_bug.cgi?id=272521
20:10:42 <zodbot> nirik: Error: That URL raised <HTTP Error 404: Not Found>
20:11:20 <nirik> "Handle fonts with many styles gracefully"
20:11:28 <bcotton> Heh, F9
20:11:33 <bcotton> Yeah, that's probably stale :-)
20:11:39 <nirik> or " 	better menuing "
20:11:53 <nirik> https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&component=distribution&list_id=12115832&product=Fedora&query_format=advanced
20:12:56 <bcotton> only 135 open bugs, though. that's less than i'd have guessed
20:13:05 <nirik> or " 	ppc64p7 subarch tracker " (we don't even support p7's anymore I don't think?
20:13:31 <nirik> I guess I can cull them, but if you want to, great. :)
20:14:42 <bcotton> i'll add it to the pgm schedule as i do the F37+ updates: https://pagure.io/fedora-pgm/schedule/issue/40
20:15:13 <nirik> the F(n) iso is oversized can definitely be culled after F(n) is released.
20:15:16 <bcotton> while you're here, though, do you have any input on https://pagure.io/fedora-pgm/schedule/issue/17 or https://pagure.io/fedora-pgm/schedule/issue/13
20:15:58 * nirik clicks
20:16:49 <nirik> 17 all seems fine.
20:17:19 <nirik> 13 might cc humaton and mohanboddu they have been doing the daily cycle stuff.
20:18:19 <nirik> oh... I really like the little subtext under early targets/release target #1
20:19:15 <bcotton> that was mattdm's suggestion. hopefully it reduces the number of times we have to explain the distinction :-)
20:20:22 <nirik> on spins... 1 is no longer a thing, we always build all the things now. 5,6,7,8 we no longer do. Although I suppose we could still update it... but we haven't been.
20:22:07 <bcotton> Seems like a good reason to drop it, then :-)
20:22:25 <bcotton> I should also update the "Custom Spins Submission Deadline" to just be the "Self-Contained Change proposal deadline" :-)
20:23:02 <nirik> yep. +1
20:23:24 <bcotton> look at us making progress
20:23:25 <bcotton> nirik++
20:23:40 <nirik> I know right? almost like we are working? naw... :)
20:24:34 <bcotton> don't let people know, they'll expect us to do it all the time
20:26:25 <nirik> indeed.
20:52:26 <bcotton> #endmeeting