14:01:45 <jcapitao> #startmeeting RDO meeting - 2020-07-01
14:01:45 <zodbot> Meeting started Wed Jul  1 14:01:45 2020 UTC.
14:01:45 <zodbot> This meeting is logged and archived in a public location.
14:01:45 <zodbot> The chair is jcapitao. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:45 <zodbot> The meeting name has been set to 'rdo_meeting_-_2020-07-01'
14:01:46 <openstack> Meeting started Wed Jul  1 14:01:45 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:47 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:49 <openstack> The meeting name has been set to 'rdo_meeting___2020_07_01'
14:02:16 <jcapitao> #topic roll call
14:02:35 <spotz> o/
14:02:46 <jcapitao> #chair spotz
14:02:46 <zodbot> Current chairs: jcapitao spotz
14:02:48 <openstack> Current chairs: jcapitao spotz
14:03:30 <amoralej> o/
14:03:33 <ykarel> o/
14:03:53 <jcapitao> #chair amoralej ykarel
14:03:53 <zodbot> Current chairs: amoralej jcapitao spotz ykarel
14:03:54 <openstack> Current chairs: amoralej jcapitao spotz ykarel
14:04:36 <rh-jelabarre> o/
14:05:02 <jcapitao> #chair rh-jelabarre
14:05:03 <zodbot> Current chairs: amoralej jcapitao rh-jelabarre spotz ykarel
14:05:04 <openstack> Current chairs: amoralej jcapitao rh-jelabarre spotz ykarel
14:07:56 <jcapitao> let's start
14:08:05 <jcapitao> #topic reqcheck - override option
14:08:38 <jcapitao> #link https://softwarefactory-project.io/r/#/c/18736/
14:09:05 <jcapitao> i wrote a doc about the override option for reqcheck and how to use it
14:09:33 <jcapitao> would like some reviews to know if it's understable
14:11:02 <spotz> I can take a look
14:11:10 * amoralej reading
14:12:28 <jcapitao> thanks guys
14:13:26 <jcapitao> next step will be to generate the initial YAML file with all the exceptions we want to handle
14:14:02 <jcapitao> https://review.rdoproject.org/r/#/c/26165/
14:14:18 <jcapitao> ^ need to be refresh
14:15:03 <jcapitao> let's continue
14:15:12 <jcapitao> #topic Test Days and Doc Days events
14:15:52 <jcapitao> spotz: do you have some fresh news ?
14:16:01 <spotz> In the last meeting we decided to push the Test Days to Milestone 2 but try to keep the Doc Days the begining of August
14:16:52 <amoralej> spotz, I will be on PTO the first week of august
14:17:00 <spotz> We were going to start organizing those events in this meeting. I have heard back from jbrooks and we should be able to get t-shirts or something for participants
14:17:05 <amoralej> but anyway, no problem as soon as there are RDOers around
14:17:16 <spotz> amoralej: I vote for pushing back a week then:)
14:17:33 <amoralej> nop, i'll be out until august 24th :)
14:17:37 <amoralej> so need to move ahead
14:17:46 <spotz> ha!
14:17:47 <amoralej> or push it back hard
14:17:50 <amoralej> :)
14:18:35 <spotz> Thoughts from folks? There's a bit of information on holding a Doc Days on the site
14:18:52 <spotz> #link http://rdoproject.org/events/docdays/
14:19:10 <amoralej> what i really would like wrt documentation is to use it to gather feedback from community about what's missing
14:19:24 <amoralej> what users and maintainers expect from RDO docs
14:20:03 <amoralej> in fact, we may do something to collect feedback in advance
14:20:11 <spotz> Maybe split into 2 events? A what are we missing day? And then a week or so later working sessions? With the gap in between to try to get the right folks involved
14:20:18 <amoralej> yeap
14:20:21 <amoralej> lgtm
14:20:35 <jcapitao> +1
14:21:03 <spotz> Anyone know the milestone 2 dates off hand?
14:21:05 <amoralej> feedback gathering may be a mtg for the topic specifically or async discussion over ML
14:21:20 <spotz> One thing we don't want to do is release new docs which are out of date too quickly
14:21:52 <ykarel> +1
14:21:53 <ykarel> Jul 27 - Jul 31
14:21:57 <spotz> Yeah we definitely need feedback from more folks that normally attend this meeting
14:22:05 <amoralej> spotz, https://releases.openstack.org/victoria/schedule.html
14:22:11 <amoralej> yep
14:22:45 <amoralej> i'm specially interested in newbiew
14:22:48 <amoralej> newbies
14:22:51 <spotz> amoralej: Ha you're on vacation for milestone 2 as well!
14:22:55 <amoralej> both as maintainers and users
14:23:03 <amoralej> no, i start my vacation on august 1st
14:23:26 <amoralej> from august 1st to 23rd
14:23:27 <spotz> So you want to schedule the test days the week before?
14:25:47 <jcapitao> Jul 27 - Jul 31 as ykarel said ?
14:25:53 <amoralej> ok
14:25:57 <amoralej> let's do 29-30
14:26:09 <amoralej> and doc days?
14:27:19 <spotz> Lets do initial discussions on the ML and push to mid August?
14:27:38 <spotz> Just in case anything comes up in testing days we need to be concerned with
14:27:44 <amoralej> "What is missing in ROD docs" could be on july?
14:27:51 <amoralej> ah, ok
14:27:54 <amoralej> that makes sense
14:28:41 <amoralej> it's just that i'd like to join that, but ok mid august could be fine
14:28:54 <amoralej> btw, wrt test days, i was thinking in replacing it by a different thing :)
14:29:02 <spotz> Then we can push to beginning of September cause I'd like you involved too:)
14:29:15 <spotz> amoralej: Ok shoot:)
14:29:27 <amoralej> still incuvating the ideas
14:29:41 <amoralej> but mainly to replace it by more targeted events
14:30:02 <amoralej> i.e. "RDO maintainers onboarding day"
14:30:38 <amoralej> or "Deploy your first OpenStack PoC" event
14:30:46 <amoralej> where we may do a guided demo
14:30:54 <amoralej> for newcomers
14:31:09 <spotz> I'm definitely good with those:) And we could probably get them livestreamed on twitch too
14:31:16 <amoralej> yep
14:31:19 <amoralej> that was my idea :)
14:31:21 <spotz> But do we still need the testing days?
14:31:35 <amoralej> i think those are not very useful lately
14:31:36 <jcapitao> yeah i like the idea !
14:32:01 <amoralej> also, we may do video-based office hours from time to time
14:32:11 <amoralej> for ask-me-anything style
14:32:18 <amoralej> with zoom or something
14:32:46 <spotz> Remember while I've used RDO and pacjstack just getting involved in this part of the OpenStack community so I don't know what works or doesn't. I do know OUI type things which we're talking about from the dev and ops side are always good things:)
14:33:35 <spotz> My team runs the redhatopenshift twitch we stream Commons so I think we could stream this as well
14:33:47 <amoralej> yep, i saw your video :)
14:34:08 <spotz> Feels weird saying I'm in marketing:)
14:34:22 <amoralej> i took openshift commons as example
14:34:31 <amoralej> i think at a much smaller scale
14:34:42 <amoralej> it would be more interesting for community
14:34:51 <spotz> But we can definitely do a how to set something up and probably a how to get started. What about turning test days into a mini-hackfest?
14:34:59 <amoralej> yep
14:35:04 <amoralej> exactly
14:35:46 <spotz> And because we might need to track attendance, we can have an eventbrite signup and only those folks can get the 'incentive' cause otherwise we don't really have info on them
14:36:19 <spotz> no email can't send a voucher which is how I'm hoping we can do swag aka no snail mail if possible
14:37:24 <spotz> #action spotz talk to cshort about whether RDO can claim twitch time
14:38:13 <spotz> Then why don't we take this new event plan to the mailing list and get buy in, I'll run it past jbrooks first just in case?
14:38:37 <spotz> We'll turn the test days into a hackfest end of July though?
14:39:12 <amoralej> spotz, there are also some discussions around CentOS SIGs
14:39:19 * jbrooks reads the scrollback
14:39:20 <amoralej> we may join forces with SIGs too
14:39:48 <spotz> amoralej: defintitely, I may not be on the right centos list for those?
14:39:57 <spotz> welcome jbrooks
14:40:12 <amoralej> from branding/awareness it may be good to extend these ideas to CentOS SIGs
14:41:03 <spotz> amoralej: Point me to the right lists or people?:) That would give us a larger target and for somethings help their folks get started as well
14:42:29 <amoralej> from CentOS side, rbowen may be interested too
14:42:56 <spotz> Him I know:)
14:43:10 <amoralej> and he may propose how / where to move on
14:43:52 <jbrooks> Another bit on the events front. RH's OSPO recently hooked up a deal w/ conference provider hopin.to, where multiple communities can host events, that may be of interest
14:44:12 <rdogerrit> Merged rdo-jobs master: Set branch for ceph-ansible-integration jobs  https://review.rdoproject.org/r/28321
14:45:19 <amoralej> thanks jbrooks i was not aware of that
14:45:25 <spotz> jbrooks will look into that see how it is on the interactivity side for things like a hackfest and whether we can restream it
14:46:16 <rdogerrit> Sorin Sbarnea (zbr) proposed rdo-infra/ci-config master: WIP: Add mol-promoter job  https://review.rdoproject.org/r/28303
14:46:45 <spotz> We're sitting at 15 minutes left but I think we have a bunch of really good ideas to discuss and share with the community. Will focus a bit more on the hackfest idea to meet the dates
14:47:25 <spotz> #action spotz - Can hopin.to do a hackfest? If not alternatives
14:48:09 <rdogerrit> Sandeep Yadav proposed rdo-jobs master: Add branch_override in ceph-ansible-integration job  https://review.rdoproject.org/r/28322
14:48:24 <jcapitao> #info Test days - August 29th & 30th (TBC)
14:48:28 <spotz> I will say OpenDev has been going really well with the Zoom/Youtube/etherpad combo so if hopin.to doesn't work out BlueJeans or Google meet are a good alternative or OpernStack's Meetpad if the attendance is low enough
14:48:37 <amoralej> jcapitao, august or july?
14:48:45 <jcapitao> oups
14:48:47 <jcapitao> #undo
14:48:47 <zodbot> Removing item from minutes: INFO by jcapitao at 14:48:24 : Test days - August 29th & 30th (TBC)
14:48:48 <openstack> Removing item from minutes: #info Test days - August 29th & 30th (TBC)
14:48:51 <spotz> hehe
14:48:59 <jcapitao> #info Test days - July 29th & 30th (TBC)
14:49:02 <spotz> That's why it kinda needs to be the priority
14:49:51 <amoralej> spotz, so you think we should maintain this test days as-is and work for next ones?
14:50:14 <amoralej> or dismantle it and see what can we do in this timeframe?
14:51:06 <jbrooks> It might be good to keep this one as is, and discuss potential changes/improvements with those who show up for it
14:51:20 <spotz> amoralej: Lets see what it would take, we need to announce it anyways so if we can make it more appealing that might help
14:51:25 <jcapitao> amoralej: were there lot of folks in the last test days ?
14:51:37 <amoralej> actually not
14:51:55 <amoralej> or that's my perception
14:52:09 <spotz> Are we talking less then 10 or less then 50?
14:52:25 <amoralej> less than 10 for sure
14:52:46 <rdogerrit> Sandeep Yadav proposed rdo-jobs master: Add branch_override in ceph-ansible-integration job  https://review.rdoproject.org/r/28322
14:53:35 <spotz> Keeping things the same as jbrooks suggested would buy us more time to make something new and shiny
14:53:36 <jbrooks> Looks like results should have been added to https://etherpad.opendev.org/p/rdo-ussuri-m3-test-matrix
14:55:09 <jbrooks> It's been a while since I've participated in one of these -- sufficient hardware access can be a challenge
14:55:17 <amoralej> yes
14:55:27 <amoralej> in a couple of test days we provided access to hardware
14:55:38 <spotz> Yeah and if less then 10 folks showed up there's no way they could have gotten through all that
14:55:38 <amoralej> are preconfigure systems
14:56:01 <amoralej> but even in those cases participation was < 10
14:57:02 <ykarel> how we used to track participations?
14:57:04 <spotz> So do we want to skip milestone2 and get something totally organized for milestone 3? Big push for collaboration, supplied HW if possible, advertising etc?
14:57:31 <jbrooks> When again is milestone 3?
14:57:46 <ykarel> irc discussions, sighnup etc?
14:57:50 <amoralej> Sep 07 - Sep 11
14:57:59 <amoralej> in fact, RC1 may be better
14:58:07 <amoralej> M3 is close to M3
14:58:59 <spotz> Sep 07 - Sep 11
14:59:02 <amoralej> i meant RC1 is close to M3
14:59:18 <spotz> RC1 would give us more time
14:59:41 <amoralej> and in RC we should have releases for everything so it's a good time to test stuff
15:00:04 <spotz> 1 minute warning FYI
15:00:09 <jbrooks> Sounds good to me. Based on that etherpad, I don't know that any bugs were filed or tests completed last time, so it's not like we're losing that
15:00:17 <jbrooks> +1 to RC
15:01:13 <jcapitao> so do we still want to introduce discussion on ML about doc days now ?
15:01:25 <jcapitao> or should we wait a few days
15:02:02 <spotz> Lets wait a few days maybe point folks to the logs for some upcoming changes
15:02:42 <jcapitao> ok let's do it
15:02:47 <spotz> We may need next meeting to decide on a timeframe as we just pushed the test days back
15:03:14 <jcapitao> #undo
15:03:14 <zodbot> Removing item from minutes: INFO by jcapitao at 14:48:59 : Test days - July 29th & 30th (TBC)
15:03:16 <openstack> Removing item from minutes: #info Test days - July 29th & 30th (TBC)
15:03:36 <spotz> But if anyone has ideas I'm always about on IRC in a bouncer and I think everyone in the OpenStack community has access to my email and RedHatters my work email
15:04:04 <jcapitao> yeah so i removed the info on this meeting
15:04:17 <jcapitao> we'll decide next meeting
15:04:24 <spotz> Sounds like a plan
15:04:47 <jcapitao> let's close quick
15:04:49 <jcapitao> before
15:04:52 <spotz> Great meeting everyone!
15:04:52 <jcapitao> #topic chair for next week
15:05:02 <jcapitao> Any volunteer?
15:05:04 <ykarel> i can take it
15:05:28 <jcapitao> #action ykarel to chair next meeting
15:06:00 <jcapitao> we're gonna skip topic open floor today
15:06:04 <jcapitao> sorry
15:06:11 <jcapitao> we're out of time
15:06:20 <jcapitao> but good discussion yeah
15:06:57 <jcapitao> thank you all
15:07:00 <jcapitao> #endmeeting