14:32:24 #startmeeting Pulp Triage 2021-03-16 14:32:24 #info daviddavis has joined triage 14:32:24 !start 14:32:24 Meeting started Tue Mar 16 14:32:24 2021 UTC. The chair is daviddavis. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:32:24 The meeting name has been set to 'pulp_triage_2021-03-16' 14:32:24 daviddavis: daviddavis has joined triage 14:32:34 #info x9c4 has joined triage 14:32:34 !here 14:32:35 x9c4: x9c4 has joined triage 14:32:36 #info ttereshc has joined triage 14:32:36 !here 14:32:36 fao89: I got you 14:32:36 ttereshc: ttereshc has joined triage 14:32:37 #info ppicka has joined triage 14:32:37 !here 14:32:37 ppicka: ppicka has joined triage 14:32:46 #info gerrod has joined triage 14:32:46 !here 14:32:46 gerrod: gerrod has joined triage 14:32:54 daviddavis++ 14:32:54 fao89: daviddavis's karma is now 455 14:33:04 ok, open floor 14:33:13 Pulp Python has moved all of its issues over to Github. What should happen to the pulp.plan.io page? 14:33:49 we struggled with this in pulp-cli 14:34:16 the options are basically: 1. archive the project and make it inaccessible 14:34:20 2. the the project as is 14:34:21 The changelog links to the issues there. 14:34:35 and with 2, there may be some way to make the issues readonly? 14:35:05 can you repeat 2.? 14:35:20 basically leave the project accessible to users 14:35:26 but maybe try to make it readonly somehow 14:35:42 That would be ideal. 14:36:00 I agree. I can look into how we can make it readonly 14:36:17 #info ggainey has joined triage 14:36:17 !here 14:36:17 ggainey: ggainey has joined triage 14:37:03 any objections? 14:37:20 +1 to readonly 14:37:42 I have seen projects that archived issues from "old tool" into a .tar.gz, that was then checked into the project. That way, if the old-tool goes away, you can still find the history/discussion contained in the old issues 14:37:55 but I would def start with 'readonly' if we can 14:38:00 Maybe we can shrink the permissions to a minimum as a backup plan 14:38:20 yeah, needs some investigation 14:39:09 cool, I'll look into it 14:39:19 +1 to readonly, I hoped that archiving means making it readonly 14:39:24 #info bmbouter has joined triage 14:39:24 !here 14:39:24 bmbouter: bmbouter has joined triage 14:39:50 all ^ sounds good to me 14:40:30 ttereshc: no it makes it compleltely inaccessible 14:40:40 alas 14:40:48 (does plan.io have a project-export?) 14:40:50 ironically 14:40:58 it does 14:41:07 and we can also request backups in addition to the redmine feature set 14:41:25 ah kk 14:41:30 so we have a number of options 14:42:08 shall we put pulp_python and CLI into 'archive' and see what it does for us? 14:42:25 fwiw... I don't know that the history for the Python plugin on plan.io is especially valuable anymore 14:42:30 bmbouter: cli is already in archive 14:42:48 dalley: consider it a practice run for larger/older projects 14:42:52 :) 14:42:59 it seems like archive vs close is really about including in search results or not https://luisblasco.com/en/redmine-delete-archive-or-close-projects/ 14:43:15 archive I think is probably better (it makes it really hidden but the data is still there) 14:43:58 i can't access issues for cli though 14:44:12 i get 403 14:44:28 yea 14:44:28 yes but we could unarchive it 14:44:40 maybe closed is better? maybe we close pulp_python and compare? 14:44:45 sure 14:44:58 I agree that likely there is not much benefit for cli or python history however it would be good to come up with some readonly option when/if we migrate older projects like pulp_rpm 14:45:18 +1 14:46:03 I just closed pulp_python 14:46:11 I don't see the close option 14:46:12 this seems like the way to go https://pulp.plan.io/projects/pulp_python 14:46:20 bmbouter: it's on the project page in the top right 14:46:25 ty 14:46:31 nice that is looking good 14:46:47 agreed 14:47:13 I think this is what we want 14:47:19 perfect - I was about to ask "can we get a banner", and there it is :) 14:47:22 +1 14:47:27 great job moving pulp_python to GHI 14:47:29 great 14:47:30 +1 14:47:39 at some point we should do pulp_ansible I think fao89 daviddavis gerrod 14:47:46 was this automated or manual? 14:47:47 +1 14:48:20 i manually moved it, there are automated scripts that use the redmine and github apis 14:49:11 it would be good to move something which requires a link to a remote tracker 14:49:11 um 14:49:28 can we reopen it just long enough to remove the "meet girls now!" spam that is the current top entry? :) 14:49:29 this was one of the obstacles to move for some projects 14:49:48 ggainey: ha done 14:49:58 :) 14:50:00 poor girls 14:50:27 they're fine. they're vips 14:51:06 "very inaccurately posted spam"? 14:51:20 hehehe 14:51:23 :D 14:51:58 issue time? 14:52:32 !next 14:52:33 daviddavis: 1 issues left to triage: 8408 14:52:33 #topic https://pulp.plan.io/issues/8408 14:52:34 RM 8408 - alikins - NEW - global_access_conditions.has_obj_perms() triggers a DRF AssertError 'Expected view ContainerNamespaceViewSet to be called with a URL keyword argument named "pk"...' 14:52:35 https://pulp.plan.io/issues/8408 14:53:11 #info ipanova has joined triage 14:53:11 !here 14:53:11 ipanova: ipanova has joined triage 14:53:18 move to pulp_container for now 14:53:32 ok 14:53:44 #idea Proposed for #8408: move to pulp_container 14:53:44 !propose other move to pulp_container 14:53:44 daviddavis: Proposed for #8408: move to pulp_container 14:53:52 +1 14:53:56 +1 14:54:12 #agreed move to pulp_container 14:54:12 !accept 14:54:12 daviddavis: Current proposal accepted: move to pulp_container 14:54:13 I don't think it's a bug. 14:54:14 daviddavis: No issues to triage. 14:54:18 whoa 14:54:24 how did *that* happen?!? 14:54:41 ggainey: ? 14:54:54 ggainey: I'm sure I can think of some thing to put in there :) 14:54:55 daviddavis: only 1 issue - I've never seen that before :) 14:55:00 hehe 14:55:00 wibbit: hush you :) 14:55:21 #endmeeting 14:55:21 !end