19:04:49 <smooge> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
19:04:49 <zodbot> Meeting started Fri Jan 10 19:04:49 2020 UTC.
19:04:49 <zodbot> This meeting is logged and archived in a public location.
19:04:49 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:49 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:04:49 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
19:04:50 <smooge> #chair smooge nirik relrod cverna
19:04:50 <smooge> #info meeting is 30 minutes MAX. At the end of 30, its stops
19:04:50 <smooge> #info agenda is at https://board.net/p/fedora-infra-daily
19:04:50 <zodbot> Current chairs: cverna nirik relrod smooge
19:05:14 <smooge> again sorry whatever I did to create this meeting in various calendars turned off any notifications on it
19:05:56 <nirik> yeah, it never notifies me either
19:06:25 <smooge> #topic Tickets needing review
19:06:25 <smooge> #info https://pagure.io/fedora-infrastructure/issues
19:06:34 <nirik> .ticket 8516
19:06:35 <relrod> and my dog just decided she wants to go out, brb
19:06:35 <zodbot> nirik: Issue #8516: fedmsg-gateway on Python3 needs monitoring fixes - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8516
19:06:43 <nirik> that should just go to waiting on assignee?
19:06:47 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8516 https://pagure.io/fedora-infrastructure/issue/8516
19:06:55 <smooge> yep
19:06:57 <nirik> .ticket 8519
19:07:00 <zodbot> nirik: Issue #8519: Wiki edit privileges - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8519
19:07:11 <nirik> I guess we just add em, but they don't really say what they want to edit...
19:07:36 <smooge> I am going to say "what are you going to work on in the ticket. If I hear from them I will add them
19:07:52 <cverna> Wasn't this supposed to be done by the join sig ?
19:08:01 <nirik> yes and no
19:08:13 <cverna> :)
19:08:17 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8519 https://pagure.io/fedora-infrastructure/issue/8519
19:08:18 <fm-admin> pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8519: "Wiki edit privileges" https://pagure.io/fedora-infrastructure/issue/8519#comment-620189
19:08:21 <fm-admin> pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8519 to smooge https://pagure.io/fedora-infrastructure/issue/8519
19:08:30 <nirik> if they just wanted to join we are supposed to point them to fedora-join
19:08:45 <nirik> if they want to edit wiki stuff thats outsside the scope of any group we should add them
19:09:03 <smooge> so basically we are now doing dual sets of work
19:09:26 <nirik> well, we are doing the same work mostly...
19:09:29 <cverna> Ok maybe in the new fas we should have something better to do that
19:09:34 <nirik> asking for what they want to do with it and acting on that
19:09:59 <nirik> we could relax constraints on the wiki (but that could backfire)
19:10:29 <smooge> so if we had the time versus a 3 month deadline.. I would look at building a two tiered auth system like Mozilla and some other groups use.
19:10:36 <cverna> Yes and there aren't many requests like that
19:10:37 <nirik> we do also have a template for this (which people never use)
19:11:08 <nirik> well, lets move any larger discussion to the list or outside the meeting...
19:11:18 <cverna> +1
19:11:34 <nirik> .ticket 8520
19:11:35 <zodbot> nirik: Issue #8520: Extend Pagure API token lifetime - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8520
19:12:32 <smooge> I have nothing to say on this one
19:12:38 <nirik> this seems like a pagure issue that spilled out to us. ;)
19:12:41 * relrod returns
19:12:58 <smooge> i am thinking it is also a policy issue
19:13:08 <nirik> well, I don't think we can adjust the policy...
19:13:29 <smooge> if we want these to be longer it can be done (say in the source code), but we need to say we want it longer.
19:13:57 <smooge> if we are saying our policy is 60 days for XYZ reason and pagure reflects that it is something else
19:14:04 <smooge> ok I guess I have something to say after all
19:14:21 <nirik> well, as far as I know 60 days is what pagure does...
19:14:37 <relrod> I'd say waiting on reporter to see if they have a specific key they want extended. If we get more complaints then we can revisit the policy issue?
19:14:45 <cverna> The idea was to use openidc token that can be renewed more easily. But we need to land that upstream
19:15:32 <pingou> which iirc waits on changes in ipsilon
19:15:56 <pingou> we already provide longer token to like releng for the rcm requests
19:16:05 <nirik> relrod: +1
19:16:13 <pingou> they should just generate a token and work w/ us on extending its lifetime
19:16:15 <nirik> pingou: yes, but only on request...
19:16:23 <pingou> +1
19:16:27 <cverna> Yeah but Patrick said yesterday we might not need it. Anyhow we going down too much details
19:16:29 <nirik> if we have 30 people requesting extensions it becomes... anoying
19:16:48 <pingou> agreed
19:17:07 <relrod> yeah but this is really the first (outside of things like releng) right?
19:17:27 <nirik> sure, but the 3-4 releng people are already somme work.
19:17:28 <pingou> we have a few for ourselves (simple-koji-ci, loopabull)
19:17:37 <nirik> anyhow, lets wait on reporter...
19:17:43 <nirik> and try and move OIDC forward.
19:18:29 <cverna> +1
19:18:49 <nirik> smooge: got the mods to the ticket, or shall I?
19:19:02 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8520 https://pagure.io/fedora-infrastructure/issue/8520
19:19:04 <nirik> any other tickets we want to talk about? any backlog ones?
19:19:16 <fm-admin> pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8519 https://pagure.io/fedora-infrastructure/issue/8519
19:19:33 <smooge> nirik, done
19:20:43 <fm-admin> pagure.issue.comment.added -- pingou commented on ticket fedora-infrastructure#8286: "bugzilla assigning packages to my old email address" https://pagure.io/fedora-infrastructure/issue/8286#comment-620194
19:20:59 <nirik> pingou: can we close some of those bz ones now?
19:21:09 <nirik> did you also see the output erroring on test and flatpaks?
19:21:13 <pingou> nirik: I wish!
19:21:48 <pingou> nirik: yes, both of them do not have component in bz so that makes sense
19:22:03 <pingou> tests won't I guess, for flatpaks no idea
19:22:15 <nirik> yeah, so likely just exclude/ignore those
19:22:33 <pingou> agreed
19:22:37 <pingou> ot
19:22:39 <pingou> it
19:22:45 <pingou> will need a small code change
19:23:13 <pingou> the ticket for the erlang sig pkgdb group has been handled
19:23:26 <pingou> it's waiting on bowlofeggs to confirm it works as desired and then we can close it
19:23:36 <fm-admin> pagure.issue.edit -- pingou edited the priority fields of ticket fedora-infrastructure#7456 https://pagure.io/fedora-infrastructure/issue/7456
19:23:42 <fm-admin> pagure.issue.assigned.added -- pingou assigned ticket fedora-infrastructure#7456 to pingou https://pagure.io/fedora-infrastructure/issue/7456
19:24:13 <nirik> .ticket 7628
19:24:16 <zodbot> nirik: Issue #7628: bugzilla - change default assignee for cockpit - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7628
19:24:39 <nirik> I think we can close that?
19:24:55 <nirik> .ticket 6985
19:24:56 <zodbot> nirik: Issue #6985: pagure-sync-bugzilla.py does not handle pagure.io outtages - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6985
19:24:56 <pingou> Failed to update: `Fedora/cockpit`:
19:24:58 <pingou> <Fault 504: 'The name cockpituous@gmail.com is not a valid username. Either you misspelled it, or the person has not registered for a Red Hat Bugzilla
19:25:01 <pingou> +account.'>
19:25:04 <nirik> ah ha!
19:25:20 <pingou> 6985 is still valid but since the script runs twice a day, meh
19:25:35 <smooge> .... reads that email name
19:25:36 <nirik> fine closing if you like
19:25:50 <smooge> close it . close it . close it
19:25:54 <nirik> .ticket 7639
19:25:55 <zodbot> nirik: Issue #7639: please remove retired packages from bugzilla components list - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/7639
19:25:57 <pingou> and with the changes we're doing to bring bugzilla overrides to dist-git, the time it takes to query src will be much shorter
19:26:12 <pingou> 7639 should be there (to be confirmed but iirc we added that)
19:27:35 <nirik> hum, doesn't seem to be working.
19:27:49 <nirik> It lets me try and open a bug on a old retired package
19:28:19 <nirik> or does it only work on things retired after the script was put in place?
19:28:42 <fm-admin> pagure.issue.comment.added -- pingou commented on ticket fedora-infrastructure#6985: "pagure-sync-bugzilla.py does not handle pagure.io outtages" https://pagure.io/fedora-infrastructure/issue/6985#comment-620198
19:28:54 <pingou> should be relying on pdc iirc
19:29:15 <fm-admin> pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#6985: "pagure-sync-bugzilla.py does not handle pagure.io outtages" https://pagure.io/fedora-infrastructure/issue/6985#comment-620199
19:29:27 <nirik> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=Terminal
19:30:15 <pingou> Terminal doesn't show in the error report
19:30:28 <fm-admin> pagure.issue.edit -- pingou edited the close_status and status fields of ticket fedora-infrastructure#6985 https://pagure.io/fedora-infrastructure/issue/6985
19:30:33 <nirik> It's an old long ago retired package
19:30:56 <nirik> we can investigate in ticket I guess...
19:31:01 <nirik> shall we close out here?
19:31:01 <pingou> let's do that
19:31:17 <pingou> we can also run the script for a single component now to see what it would do
19:31:49 <pingou> so you can run it with --debug and -p rpms/Terminal
19:32:07 <nirik> nice.
19:32:13 <nirik> Thanks for input everyone!
19:32:17 <nirik> #endmeeting