14:31:15 <fao89> #startmeeting Pulp Triage 2020-06-02
14:31:15 <fao89> #info fao89 has joined triage
14:31:15 <fao89> !start
14:31:16 <pulpbot> Meeting started Tue Jun  2 14:31:15 2020 UTC.  The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:31:16 <pulpbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:31:16 <pulpbot> The meeting name has been set to 'pulp_triage_2020-06-02'
14:31:16 <pulpbot> fao89: fao89 has joined triage
14:31:18 <daviddavis> that was a long triage
14:31:20 <daviddavis> #info daviddavis has joined triage
14:31:20 <daviddavis> !here
14:31:20 <pulpbot> daviddavis: daviddavis has joined triage
14:31:24 <bmbouter> ha yup
14:31:27 <ppicka> #info ppicka has joined triage
14:31:27 <ppicka> !here
14:31:29 <pulpbot> ppicka: ppicka has joined triage
14:31:29 <fao89> !next
14:31:30 <pulpbot> fao89: No issues to triage.
14:31:36 <fao89> Open floor!
14:31:38 <ipanova> #info ipanova has joined triage
14:31:38 <ipanova> !here
14:31:38 <pulpbot> ipanova: ipanova has joined triage
14:31:44 <fao89> https://hackmd.io/SVCMjpwXTfOMqF2OeyyLRw
14:31:54 <fao89> topic: how to deduplicate pulpcore Documentation tag and Documentation category?
14:32:47 <fao89> I believe we don't need a category for that
14:32:51 <ipanova> i think documentation category is not available across all projects
14:33:14 <ipanova> we need to use either one or another
14:33:35 <ggainey> #info ggainey has joined triage
14:33:35 <ggainey> !here
14:33:44 <fao89> on installer for example, it is a category, and we have docs issues, so the tag works for us, the category wouldn't
14:34:03 <bmbouter> fao89: I agree that's a great point in favor of using the tag
14:34:08 <fao89> unless it is possible to set 2 categories on the same issue
14:34:23 <bmbouter> fao89: it is not
14:34:27 <ipanova> why would you need 2 categories?
14:34:37 <fao89> installer + documentation
14:34:38 <bmbouter> Installer is a category
14:34:42 <ipanova> aha
14:34:51 <fao89> tag is the winner
14:34:52 <ipanova> +1 to using tag then
14:35:05 <ipanova> i think in any case lately we have been using the tag
14:35:09 <bmbouter> I agree
14:35:33 <bmbouter> I can make this change and I will replace the categort w/ the tag so nothing will be lost
14:35:40 <fao89> next topic?
14:35:50 <bmbouter> I will make this change today
14:36:04 <bmbouter> ok w/ me
14:36:04 <ipanova> sounds good, thank you
14:36:12 <fao89> topic: announcing https://fixtures.pulpproject.org/fixtures/
14:36:29 <ipanova> awesomee
14:36:48 <bmbouter> yup so this is online! I'm going to send an announcement to pulp-dev also and ask mcorr to add to the website if she thinks that makes sense
14:36:58 <bmbouter> so just an fyi here
14:37:03 <ppicka> great, will it be updated with every merge?
14:37:04 <ipanova> ok
14:37:18 <bmbouter> it will be, there is a 5 min delay though after the container is published
14:37:40 <ipanova> bmbouter: what about tests that use link for the old fixtures
14:38:13 <bmbouter> ipanova: great question. we have an epic tracking each plugin's removal of fedorapeople fixtures and they will not be taken down yet
14:38:21 <ipanova> ack
14:38:23 <bmbouter> https://pulp.plan.io/issues/6638
14:38:43 <dkliban> great!
14:38:45 <bmbouter> file maven python and rpm all have open items in this area ^
14:38:45 <dkliban> #info dkliban has joined triage
14:38:45 <dkliban> !here
14:38:51 <bmbouter> and ansible
14:38:57 <dkliban> !here
14:39:08 <bmbouter> pulpbot is struggling
14:39:08 <pulpbot> bmbouter: Error: "is" is not a valid command.
14:39:25 <fao89> pulpbot does not like pulp-meeting channel
14:39:25 <pulpbot> fao89: Error: "does" is not a valid command.
14:39:26 <dkliban> yeah ... it didn't send a message but it told me privately that i already joined
14:39:42 <fao89> pulpbot--
14:39:42 <pulpbot> fao89: pulpbot's karma is now -1
14:39:45 <dkliban> lol
14:39:54 <ipanova> next topic?
14:39:56 <bmbouter> ppicka: would you be able to look at the rpm tests issue https://pulp.plan.io/issues/6656
14:39:58 <daviddavis> I'm trying to think about how we can start testing https://fixtures.pulpproject.org/fixtures/
14:40:09 * ppicka just checking it
14:40:15 <bmbouter> and gerrod for python?
14:40:23 <bmbouter> https://pulp.plan.io/issues/6656
14:40:52 <ppicka> bmbouter: I will assign it to me for RPM, do we have some time plan how fast do we want to move from fedorapeople to our new?
14:40:53 <bmbouter> daviddavis: so the current plan (up for discussion) is that when running in CI the container is locally hosted
14:41:04 <bmbouter> ppicka: we don't have a timeline
14:41:10 <daviddavis> bmbouter: that's what we do today
14:41:27 <daviddavis> at least in travis
14:41:29 <bmbouter> daviddavis: great, and when running off CI it uses fixtures.fedorapeople.org
14:41:41 <daviddavis> yea
14:41:47 <dkliban> you mean fixtures.pulpproject.org ?
14:41:54 <bmbouter> lol yeah...
14:42:06 <daviddavis> we need to update the docs too
14:42:10 <bmbouter> dkliban: I think the fixtures change you are making may roll that out for all plugins?
14:42:21 <bmbouter> s/fixtures change/pulp smash change/ ?
14:42:34 <dkliban> bmbouter: i am not making a change ... i was just doing it locally on my box to test that it's working
14:42:41 <bmbouter> ack ty
14:43:05 <bmbouter> daviddavis: so I'm thinking that actually all of these plugin issues are really audits to make sure they're using fixtures from the container exclusively
14:43:23 <bmbouter> and that we only need to change pulp-smash itself to switch the default location?
14:43:29 <bmbouter> or maybe I'm confused, wdyt?
14:43:58 <ipanova> pulp-smahs also needs a change
14:45:03 <ipanova> git grep showed me only 1 result ^
14:46:03 <bmbouter> so do I need to make a sub-task for the epic to update pulp-smash?
14:46:10 <ppicka> bmbouter: in case of rpm it is defined in rpm tests
14:46:19 <ipanova> bmbouter: yes
14:46:31 * bmbouter makes it now
14:47:15 <ipanova> ppicka: every plugin will need to make an audit and change docs + tests
14:47:48 <bmbouter> can we put 6638 on the sprint or can someone quick PR it?
14:47:51 <ppicka> ipanova: I agree, it was more 'fyi' when the topic was about pulp-smash too
14:48:14 <fao89> +1 to add to sprint
14:48:16 <bmbouter> I agree this is way more than an fyi
14:48:22 <ipanova> +1
14:48:36 <bmbouter> I'll add to sprint now per this convo
14:49:07 <ipanova> ok
14:49:13 <bmbouter> https://pulp.plan.io/issues/6881 specifically
14:49:38 <fao89> next topic: what is the purpose of the ‘backlog’ Tag?
14:50:00 <bmbouter> this confused me because all things are backlog effectively
14:50:03 <ipanova> this is for this query https://pulp.plan.io/projects/pulp/issues?query_id=152
14:50:21 <bmbouter> mmmm
14:50:22 <ipanova> issues that are good candidates for interns are marked as backlog
14:50:40 <fao89> this query always makes me laugh
14:50:43 <bmbouter> well that answers my question
14:50:48 <bmbouter> the query is veyr useful
14:50:50 <bmbouter> the tag not so much
14:51:03 <ipanova> agree about the tag name
14:51:04 <bmbouter> we could do this differently, we could have the query refer to specific issue numbers
14:51:14 <fao89> s/backlog/love
14:51:15 <ipanova> but at the times we did not come up with a better one
14:51:52 <ipanova> bmbouter: i would prefer to keep a tag
14:52:15 <bmbouter> I'm ok with that, but does this make sense for users to see though?
14:53:48 <dkliban> i can see it being confusing for the uers
14:54:07 <dkliban> i've already heard that we have too many fields that dont' make sense to users filing bugs
14:54:15 <ipanova> i am not sure what to answer, imo this kind of tag should not create any kind of feelings
14:54:22 <bmbouter> yup that's my highlest level goal is to simplify redmine
14:55:18 <bmbouter> our redmine is confusing for users
14:55:25 <dkliban> yep
14:55:45 <ipanova> if that's a concern then we can point query to specific issues number until we come up with a proper tag name
14:56:15 <bmbouter> I was looking at how to do that and I didn't exactly see how
14:56:22 <bmbouter> but that would resolve my concern completely
14:56:33 <ipanova> the goal was to mark issue that would be good being worked on for interns and not create more cinfusion
14:56:41 <ipanova> confusion*
14:57:02 <bmbouter> oic how
14:57:24 <bmbouter> if you want to make a change now or wait I'm ok either way
14:57:31 <bmbouter> I don't want to take folks somewhere they don't want to go
14:57:35 <ipanova> issue 'is'
14:57:41 <bmbouter> yup I agree
14:57:47 <ipanova> bmbouter: https://pulp.plan.io/issues?set_filter=1&status_id=*&issue_id=5707,5894,5896,5941,5955,5955,5833,5867,5870,5873,5706,5941
14:58:06 <bmbouter> so we could remove 'backlog' and have the query use issue is instead
14:58:31 <bmbouter> but only if folks are comfortable w/ this change
14:58:52 <ipanova> yes we can, if that will improve user experience i am in favour
14:59:00 <ipanova> i can do that
14:59:53 <bmbouter> ipanova: ty!
15:00:39 <fao89> last topic: removing the ‘Demo Requested’ tag
15:01:02 <bmbouter> yup same reasoning here, the goal is to simplify redmine and this tag has no life/process/place
15:01:12 <fao89> +1
15:01:19 <ipanova> +1
15:01:36 <bmbouter> I can remove this one
15:02:26 <fao89> #endmeeting
15:02:26 <fao89> !end