13:02:54 #startmeeting FPgM office hours 13:02:54 Meeting started Wed Sep 28 13:02:54 2022 UTC. 13:02:54 This meeting is logged and archived in a public location. 13:02:54 The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 13:02:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:02:54 The meeting name has been set to 'fpgm_office_hours' 13:02:54 #info This is an open floor meeting to discuss anything program management related (elections, changes, schedule, etc) 13:02:59 #info Inactive packagers will be removed after the F37 release: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/UG3UOKBVJLUWZYEHWL52KPMITPEPEBNF/ 13:02:59 #info Packages in need of a Python 3.11 rebuild will be retired before the Final freeze: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/LMOHU6P4C4G26WTQE7RV2NZSBDTHXKY4/ 13:03:05 #help Submit your ideas for the Fedora Magazine "Feature Spotlight" series: https://communityblog.fedoraproject.org/collecting-ideas-for-feature-spotlight-articles/ 13:03:10 #help Call for projects and mentors for the next Outreachy cohort: https://communityblog.fedoraproject.org/call-projects-mentors-outreachy-dec-2022/ 13:03:15 #help Fedora Week of Diversity proposals are due 1 October: https://communityblog.fedoraproject.org/call-for-proposals-fwd-2022/ 13:03:22 #info F37 Final Freeze begins Tuesday 2022-10-04 13:03:22 #link https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html 13:03:27 #info I propose to disable the comps component in Bugzilla on 29 September: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4TAYYLNIUICCTLUZE7TW6T73FYGFHCCS/#4TAYYLNIUICCTLUZE7TW6T73FYGFHCCS 13:03:31 #info Upcoming and recent summer time changes: https://discussion.fedoraproject.org/t/reminder-summer-time-changes-coming-up/27831/4 13:03:40 #info The Fedora Social Hour is tomorrow: https://matrix.to/#/#social:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org 13:03:43 #topic Open floor to discuss anything program management related (elections, changes, schedule, etc) 13:06:53 Good morning! Is there a badge for being first at the FPgM office hours? ;) 13:14:05 Penguinpee: heh, no badge. sorry :-) 13:16:09 :-\ I put that down on my list regarding badges. Am I in the right place to ask some questions about badges? 13:17:44 you can try. if i can't answer the questions, i might be able to point you in the right direction 13:18:46 Oh wait, I thought I needed you, but I just realized revisiting the topic on discussions, that it's Matthew who wrote that script. Not sure why I keep mixing up the two of you. 13:18:57 we're both from Indiana? :-) 13:19:01 * Penguinpee thinks it's the hat :) 13:20:08 I thought Matthew was from MA. 13:21:00 he lives there now, but he's originally from northern Indiana 13:24:53 I see. My questions regarding badges are all about procedures, getting access an who is and who is no longer actively involved in the project. Marie has already tried getting me in contact with some people she knows might be able to help. But it's been quiet so far. 13:25:43 yeah, i think that's part of the problem. it seems like everyone is in the "no longer actively involved" category 13:25:49 If it stays quiet I need to know whom to poke, what procedures to follow. I plan on talking to infra tomorrow. 13:29:58 talking to infra is probably the best next step anyway. they'd be able to get you the access you need. if no one is around to object to giving you access, that's a good sign that you should get it 13:30:02 Vipul Siddharth: are you around? 13:30:26 well, most issue with badges are on the code side 13:30:34 porting the stack to py3, to newer lib 13:30:44 and fixing recurring issues (who have bugs open) 13:31:04 there isn't much that requires admin access, except restart it when it crash due to open bugs 13:31:13 (and that part could be automated) 13:31:43 well they'd still need repo access if no one who currently has it is responding to requests to add them 13:31:52 repo access, yeah 13:32:58 ah, but it's on github :/ 13:33:23 Thanks for the information, misc. I had a good look in pagure already. Most issues there are regarding badges (requests, fails, etc). Not much regarding issues with the backend. I hooked up with erolkskn, who recently joined infra. 13:33:29 or no...that's the badgr code 13:33:46 well, the badges themself are on pagure 13:34:04 It surely is not deployed directly from GitHub, I hope. 13:34:05 ah, tahrir is on github, too, but at least it's int eh fedora-infra namespace 13:34:07 the code is on multiple repo 13:34:24 and fedbadges 13:34:43 (i guess badgr is in the namespace too, now that i look at it. my coffee is defective) 13:34:55 It's all very mind blowing when you first try to get a hold on it. 13:34:59 https://github.com/fedora-infra/fedbadges/ 13:36:31 Yeah, fedbadges is the backend. But is that directly deployed on the machine? There must be some change review process before it gets into the live environment. 13:37:10 it is more complex 13:37:28 there is fedbadges, and there is release, then once it get release, it get packaged, then deployed 13:37:46 in a ideal world, it should (IMHO) be deploy from git 13:38:38 cause the software is pretty specific to Fedora infra, and I think no one is reusing them (there was attempts in the past), so we can skip the release/rpm part 13:38:48 the same go for tarhir 13:39:08 erolkskn: Are you around? 13:39:55 misc: And packaging is done just like normal community packages in Fedora? 13:40:08 Penguinpee: I think, yes 13:40:12 so in EPEL 13:43:26 Of course. Machines would be running RHEL. Thank you for the information. 13:44:21 misc: Since you are in the fedora-badges group, could you add me to the group? Or do I need to open a ticket for that or ask someone else? 13:44:37 Penguinpee: not sure I have admin access to that group :/ 13:44:40 also, which group 13:44:51 https://pagure.io/group/fedora-badges 13:46:01 seems I can edit, but so, what is the access needed ? 13:46:43 (cause that one is for adding new badges, changing assets, etc) 13:47:04 To start with I would like to work on tickets. Getting order in the chaos. Later on, merge access for PRs. I will talk to infra tomorrow as well. 13:47:41 I think the biggest cleanup is purging the 3D model from the repo 13:48:39 I'm not sure what that is referring to. If it's in git, I'll find it. 13:49:05 so the git repo is 2G 13:49:18 because there is a directory stls, who take a lot of space 13:49:30 that's model for a 3D printer. For physical badges 13:50:10 since the badges are round, the 3D model are huge as they are using bezier curve, just think 1000 small lines turning 0.1 D to draw a circle using a 3D printer.. 13:50:16 and we do not use them 13:50:53 I see. That needs to be stored elsewhere. Maybe in a repo of its on or on plain storage. 13:51:08 yeah, a separate repo 13:51:26 the main issue is not to do it, but find who can do it, as that requires some git push -f around and some coordination 13:52:52 Whatever I do will be in a local clone for now anyway. I don't have push access. But taking things out of git is not trivial, IIRC. 13:53:20 bcotton: Thanks for letting us use your office. :-D 13:53:43 haha, any time :-D 13:54:31 Penguinpee: I might have pasted the command somewhere, I do it quite often 13:54:56 (of course, the question is "where did i pasted that") 13:55:40 https://pagure.io/fedora-badges/issue/727 13:58:08 git filter-repo can be used for that 13:58:21 kinda safe and easy, especially since we can run it on a clone 14:00:23 #endmeeting