14:01:37 <jcapitao> #startmeeting RDO meeting - 2020-12-16
14:01:37 <zodbot> Meeting started Wed Dec 16 14:01:37 2020 UTC.
14:01:37 <zodbot> This meeting is logged and archived in a public location.
14:01:37 <zodbot> The chair is jcapitao. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:37 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:37 <zodbot> The meeting name has been set to 'rdo_meeting_-_2020-12-16'
14:01:38 <openstack> Meeting started Wed Dec 16 14:01:37 2020 UTC and is due to finish in 60 minutes.  The chair is jcapitao. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:42 <openstack> The meeting name has been set to 'rdo_meeting___2020_12_16'
14:02:33 <jcapitao> #topic roll call
14:02:44 <jpena> o/
14:02:55 <chandankumar> \o
14:02:57 <spotz> o/
14:03:40 <jcapitao> mjturek: do you want to discuss the topics you put last week ?
14:03:49 <jcapitao> #chair jpena chandankumar spotz
14:03:49 <zodbot> Current chairs: chandankumar jcapitao jpena spotz
14:03:50 <openstack> Current chairs: chandankumar jcapitao jpena spotz
14:06:04 <amoralej> o/
14:06:04 <spotz> mjturek: Do you want to present your items from last week?
14:06:08 <ykarel> o/
14:06:28 <jcapitao> #chair amoralej ykarel
14:06:28 <zodbot> Current chairs: amoralej chandankumar jcapitao jpena spotz ykarel
14:06:29 <openstack> Current chairs: amoralej chandankumar jcapitao jpena spotz ykarel
14:08:14 <jcapitao> ok, let's start with first topic
14:08:22 <jcapitao> #topic On boarding process, where to send new contributors
14:08:46 <spotz> Being that chandankumar joined us and I ran into a few questions looking at our doc:)
14:09:45 <chandankumar> yes please
14:10:02 <spotz> So Bugzilla seems to be the official way to find tasks but it does not appear to have a search for easy tasks and what is in there is either older or already assigned
14:10:41 <amoralej> what kind of tasks?
14:11:06 <chandankumar> spotz: for easy tasks earlier, we used github issues under easyfixes, we never used bugzilla for finding easy tasks
14:11:08 <spotz> The Github repo we currently send folks to has really old issues. And while it's purpose I believe was to allow you to get a mentor it's really old and out of date
14:11:09 <amoralej> i mean, we use bz for some stuff but not for everything
14:11:17 <chandankumar> but that initiative got dead long time ago
14:11:47 <spotz> hehe the point of my topic! We should only have one place that has things people can work on
14:13:05 <spotz> I think we all tend to just do stuff and not use BZ which is fine I do it upstream and in RDO too. But some first timers might not be comfortable with that. Now we can definitely word the page to say if you find something small and want to just put up a patch please do
14:13:06 <amoralej> yes, that's a good point
14:13:32 <amoralej> so, we have a trello board https://trello.com/b/HhXlqdiu/rdo
14:13:50 <spotz> But having only one place for them to look and one place for us to maintain I think would be less confusing
14:13:56 <amoralej> i'd say that's the most generic way to report we use
14:14:02 <spotz> amoralej: Is that public?
14:14:05 <amoralej> but we need bz for specific things
14:14:11 <amoralej> yes spotz it's public
14:14:24 <mjturek> sorry spotz im good, asked about them throughout the eek instead
14:14:27 <jcapitao> maybe we should communicate the trello board on our website ?
14:14:45 <jcapitao> i mean a dedicated page
14:15:07 <spotz> jcapitao: If that's the best place then yes and maybe a point to BZ in X,y, and z conditions?
14:15:08 <apevec> sorry I saw ping earlier, what is the question about rdo cloud??
14:15:28 <apevec> (spoiler: it's going away, best to assume it's gone)
14:15:51 <ykarel> ^ makes that question go away
14:16:11 <ykarel> so can ignore that
14:16:16 <amoralej> spotz, bz is mainly just to specific things as add new packages
14:16:22 <apevec> excellent :)
14:16:42 <amoralej> trello board is more generic
14:16:51 <amoralej> and in fact we may create a trello card and point to the bz
14:17:22 <spotz> amoralej: Ok which makes sense as currntly the page is worded in that direction as it talks about installing rdopkg(?)
14:18:29 <spotz> Ok so sounds like easyfix should be retired as unmaintained, point to the trello board and change the BZ and maybe the rdopkg into a package contributor only thing
14:18:45 <spotz> Do we on;y really get web/doc and package contributions?
14:18:49 <jcapitao> we can take advantage of trello labels (e.g easy_fix label)
14:19:05 <amoralej> if we want to revive easyfixes we could move to trello, yes
14:19:05 <spotz> jcapitao: perfect!
14:19:10 <amoralej> i think it'd be better
14:19:20 <amoralej> yes, lables would be good
14:19:31 <amoralej> labels
14:19:47 <spotz> It'll definitely stop people from looking at really old things that maybe are long fixed
14:21:31 <rdogerrit> Amol Kahat proposed rdo-infra/ci-config master: Add tripleo component standalone upgrade criteria master+V+U  https://review.rdoproject.org/r/31358
14:21:34 <spotz> Ok I'll work on a patch for that page as a WIP so we can make sure the process is correct
14:21:48 <jcapitao> do we have complaints on old things ?
14:21:50 <spotz> Anyone else on this topic?
14:22:21 <spotz> jcapitao: Complaints no but when you see things that are old you tend to think a project isn't active
14:23:04 <jcapitao> right
14:24:07 <spotz> I'm still working on getting access to our twitter, but we've gotten some likes lately on facebook:)
14:24:33 <spotz> So people are finding us, we just want them to join in:)
14:26:31 <jcapitao> wow we have FB page, was not aware of that
14:27:21 <spotz> jcapitao: I think it mainly get reposts but I did make a post about the release
14:27:49 <spotz> Anyways thatt's all I had on that for now
14:28:32 <openstackgerrit> yatin proposed x/packstack stable/train: Rely on ID/VERSION_ID to detect distro  https://review.opendev.org/c/x/packstack/+/767137
14:28:50 <rdogerrit> Alfredo Moralejo created rdo-infra/weirdo master: Update ansible version to 2.9.16  https://review.rdoproject.org/r/31384
14:29:24 <jcapitao> ok thank you spotz
14:29:32 <spotz> My pleasure
14:30:11 <jcapitao> let's move to next topic
14:30:43 <jcapitao> #topic Next time's chair
14:30:57 <ykarel> i can take it
14:31:16 <spotz> Are we going to keeo going or break for the holidays?
14:31:48 <amoralej> i'll be on pto next three meetings
14:32:15 <amoralej> my xmas pto goes from wednesday to thursday :)
14:32:23 <spotz> Me too:)
14:32:58 <jcapitao> I'll be on PTO next two meetings
14:32:59 <rdogerrit> Riccardo Pittau created openstack/sushy-tools-distgit rpm-master: Initial import of spec file  https://review.rdoproject.org/r/31385
14:33:26 <spotz> Well Mon-Wen, holiday, recharge, holiday:)
14:33:44 <spotz> Maybe it's only 2 weeks
14:34:02 <amoralej> so, i'd say ykarel can run it next week, then skip following one and retake on jan 6th
14:34:15 <ykarel> +1
14:34:16 <amoralej> i have two weeks, three meetings :)
14:34:49 <spotz> Ok I'll email the lists we're meeting next week then skipping until 1/6
14:34:58 <jcapitao> #action ykarel to chair next week
14:36:17 <jcapitao> #topic Open Floor
14:37:03 <jcapitao> feel free
14:39:06 <spotz> Anything else I'd come up with is too long:)
14:39:40 <amoralej> :)
14:40:14 <amoralej> i think it's fair to mention that we'll need to think what to do with centos8-> stream
14:40:25 <spotz> That was one of them:)
14:40:28 <amoralej> first thing next year :)
14:40:44 <spotz> Moving target repos is another:(
14:40:59 <openstackgerrit> yatin proposed x/packstack stable/ussuri: Rely on ID/VERSION_ID to detect distro  https://review.opendev.org/c/x/packstack/+/767136
14:41:01 <amoralej> target repos?
14:41:09 <jcapitao> repoids ?
14:41:40 <spotz> On an easier note, do we have a way to pull contact info for all the contributors so if we get in the Cool Stuff Store over break I can just mail out codes and info?
14:42:05 <spotz> So we CI/CD the packages. So an install that works yesterday may not today
14:42:11 <spotz> Hence moving targett
14:42:19 <amoralej> ah, got it now
14:42:21 <amoralej> yep
14:42:47 <amoralej> now we have two fast moving targets
14:42:53 <amoralej> sorry, we have one now
14:42:58 <amoralej> we'll have two soon
14:44:04 <ykarel> what script was used to fetch contributors in https://review.rdoproject.org/etherpad/p/victoria-release-announcement
14:44:23 <ykarel> may be same can be used to fetch email contacts for those
14:44:35 <spotz> ykarel: That was my thought
14:44:38 <amoralej> ykarel, just curl calls to repoexplorer
14:44:52 <amoralej> i think we only have user name
14:45:01 <amoralej> you want mails, right?
14:45:03 <spotz> amoralej: From an ops perspectiive an install might work one day and not the next due to changes
14:46:05 <amoralej> yep
14:46:33 <spotz> Which is bad:(
14:48:29 <ykarel> yes mail should be enough i think
14:49:06 <spotz> amoralej: Just email, they'll have a code and put their info in the store
14:49:50 <spotz> I can search for thte red hatters in rover and will just reach out on the lists if need be to the others I guess
14:50:45 <amoralej> so, i.e. https://redhat-oss-git-stats.softwarefactory-project.io/contributor.html?cid=BQgJExQAEQ4lFAQRBBUQSwUOGA--
14:50:54 <amoralej> i don't see the mail address there
14:51:31 <amoralej> gerrit account in review.r.o is linked to github
14:51:44 <amoralej> not sure if we can fetch it from there
14:51:46 <amoralej> mm
14:51:49 <spotz> Yeah, ok I'll work around it
14:51:52 <amoralej> better from review.r.o
14:55:07 <spotz> Ok that's enough trouble from me for today:)
14:56:02 <jcapitao> ok let's close the meeting then
14:56:28 <jcapitao> #endmeeting