14:30:11 #startmeeting Pulp Triage 2020-09-11 14:30:11 #info fao89 has joined triage 14:30:11 !start 14:30:11 Meeting started Fri Sep 11 14:30:11 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:11 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:11 The meeting name has been set to 'pulp_triage_2020-09-11' 14:30:11 fao89: fao89 has joined triage 14:30:57 #info daviddavis has joined triage 14:30:57 !here 14:30:57 daviddavis: daviddavis has joined triage 14:31:15 #info dkliban has joined triage 14:31:15 !here 14:31:15 dkliban: dkliban has joined triage 14:31:57 #info bmbouter has joined triage 14:31:57 !here 14:31:57 bmbouter: bmbouter has joined triage 14:32:01 * bmbouter does the dance of friday 14:32:02 !next 14:32:03 #topic https://pulp.plan.io/issues/7495 14:32:03 fao89: 4 issues left to triage: 7495, 7486, 7485, 7476 14:32:04 RM 7495 - awcrosby - NEW - duplicate key violation, Repository.next_version already exists 14:32:05 https://pulp.plan.io/issues/7495 14:32:47 we had a similar bug filed before 14:33:01 but it was for the pulp_rpm plugin 14:33:20 #idea Proposed for #7495: Leave the issue as-is, accepting its current state. 14:33:20 !propose accept 14:33:20 fao89: Proposed for #7495: Leave the issue as-is, accepting its current state. 14:33:27 +1 14:33:53 #agreed Leave the issue as-is, accepting its current state. 14:33:53 !accept 14:33:53 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:33:54 #topic https://pulp.plan.io/issues/7486 14:33:54 fao89: 3 issues left to triage: 7486, 7485, 7476 14:33:55 RM 7486 - daviddavis - NEW - 1.3.0 release 14:33:56 https://pulp.plan.io/issues/7486 14:34:01 convert to task 14:34:03 +1 14:34:04 +1 14:34:12 I'll do that 14:34:25 #idea Proposed for #7486: convert to task 14:34:25 !propose other convert to task 14:34:25 fao89: Proposed for #7486: convert to task 14:34:29 #agreed convert to task 14:34:29 !accept 14:34:29 fao89: Current proposal accepted: convert to task 14:34:30 #topic https://pulp.plan.io/issues/7485 14:34:30 fao89: 2 issues left to triage: 7485, 7476 14:34:32 RM 7485 - thm - NEW - Documentation: Pulp all-in-one container with CentOS7's docker 14:34:33 https://pulp.plan.io/issues/7485 14:34:52 #idea Proposed for #7485: Leave the issue as-is, accepting its current state. 14:34:52 !propose accept 14:34:52 dkliban: Proposed for #7485: Leave the issue as-is, accepting its current state. 14:35:06 we need to update our pulpproject.org page to include a note about this 14:35:12 #agreed Leave the issue as-is, accepting its current state. 14:35:12 !accept 14:35:12 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:35:12 #topic https://pulp.plan.io/issues/7476 14:35:13 fao89: 1 issues left to triage: 7476 14:35:14 RM 7476 - dalley - NEW - [Docs] Improve plugin API reference section of the guide 14:35:15 https://pulp.plan.io/issues/7476 14:36:15 #info ggainey has joined triage 14:36:15 !here 14:36:15 ggainey: ggainey has joined triage 14:36:22 the next 3 I would suggest accept + low prio 14:36:26 #idea Proposed for #7476: accept and add to current quarter 14:36:26 !propose other accept and add to current quarter 14:36:26 fao89: Proposed for #7476: accept and add to current quarter 14:37:57 #agreed accept and add to current quarter 14:37:57 !accept 14:37:57 fao89: Current proposal accepted: accept and add to current quarter 14:37:58 fao89: No issues to triage. 14:37:58 + convert to task 14:38:34 Open floor! 14:38:47 https://hackmd.io/@pulp/triage/edit 14:38:59 !friday 14:38:59 ♪ It's Friday, Friday, gotta get down on Friday ♪ 14:39:03 topic: why redmine queries are so easy to delete? 14:39:42 is there a way to improve it? 14:40:23 i don't think so 14:40:30 but i have not looked into it 14:40:46 I also believe there is not, we are not able to configure permissions more finely than we have already and we can't customize our redmine (it's hosted not by us) 14:40:57 the good news is though, if we switch to github it won't be an issue 14:41:00 =/ 14:41:21 next topic: Add a tag or new tracker to track release tasks 14:41:26 #info x9c4 has joined triage 14:41:26 !here 14:41:26 x9c4: x9c4 has joined triage 14:42:09 my concern with this is that the more we add the more choice users have when filing tasks 14:42:32 these fields do already exist though 14:42:33 this was the motivation for my big push to super-simplify our redmine actually 14:42:43 choice when selecting them 14:42:47 is still increased 14:42:52 that's true 14:43:06 my problem is there's no way to search on release issues reliably 14:43:51 for any of these issues there would be a corresponding version field already created 14:43:52 Can we prevent users from creating issues in the release tracker? 14:44:11 So only admins can? 14:44:24 that might be an option 14:44:30 bmbouter: not sure I follow 14:44:44 I feel this discussion would be good after pulpcon, since we will be discussing moving to github issues 14:45:02 daviddavis: what I'm getting at is that the release tracker isn't the real thing, it's just a bookkeeping helper 14:45:27 I think the roadmap page is the real thing, e.g. https://pulp.plan.io/versions/126 versus https://pulp.plan.io/issues/7463 14:45:34 yea, that's kind of why I am leaning towards a tag 14:45:58 we cannot restrict some users to set some tags in redmine at least 14:46:13 this is true 14:46:22 if you want to still do this I can disagree and say ok 14:46:42 I think I'm worn out mostly on redmine customization having done it for soooo longgggg 14:47:09 release task could be the first task to be added to the milestone, so we can look at the milestone 14:47:14 yea, I agree. but as someone who primarily manages these release issues, it would help me to be organized. 14:47:38 fao89: the only problem is I can't see release issues across milestones 14:47:40 can we add a boolean just for tasks? 14:47:56 most users dont' file tasks 14:48:00 we can but is this really that special 14:48:45 eh 14:49:20 i don't think so 14:49:42 daviddavis: if this is helpful to you and you want to configure it somehow having stated my concerns I would say feel free to do it 14:49:42 I don't have a strong preference as long as I can search for release issues. I'm happy to raise this again after pulpcon if we want more time to think about it. 14:50:16 it doesn't sound like there's overwhelming support for any solution here so let's revisit later 14:50:29 let's revisit later 14:50:59 next topic: hacktoberfest 14:51:28 do we have issues that we can add the hacktoberfest label? 14:52:05 hacktoberfest awards people who make 4 contributions to open source during October 14:52:33 maybe something cli related? 14:52:59 that would be good 14:53:05 or auto-distribution ? 14:53:41 assuming we design that out in advance 14:54:47 this might make a better mailing list discussion so peopel can think of ideas 14:55:07 +1 14:55:08 I just wanted to point out, we can benefit from contributors during October 14:55:25 next topic: pulpcon video links 14:55:28 yes indeed - I signed up for updates, had not seen this before, thanks fao89 14:56:16 ggainey, for us it is free t-shirt and stickers every year, since we are always contributing to open source 14:56:30 zacly :) 14:56:53 so this is what I learned about our video links 14:57:08 and I was I think the main proponent of per-session links because I wasn't sure this would work 14:57:13 but it does work, so let's keep it simple 14:57:18 +1 14:57:20 +1 14:57:26 KISS 14:57:42 keep it simple smarty 14:57:46 heh 14:58:39 I'm adding the links to the schedule now 14:59:45 #endmeeting 14:59:45 !end