15:00:21 <witek> #startmeeting monasca
15:00:26 <openstack> Meeting started Wed Aug 14 15:00:21 2019 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:31 <openstack> The meeting name has been set to 'monasca'
15:00:43 <witek> hello everyone
15:00:49 <Wasaac> o/
15:01:03 <witek> hi Wasaac
15:01:11 <Wasaac> Hey
15:01:26 <dougsz> hey all
15:01:34 <witek> hi Doug
15:01:34 <joadavis> greetings
15:01:38 <witek> and Joseph
15:01:53 <witek> agenda for today:
15:01:58 <witek> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:02:02 <witek> pretty light
15:02:21 <witek> please add if you have anything
15:02:40 <witek> #topic review priority flag
15:02:44 <chaconpiza> Hi!
15:02:50 <witek> hi Martin
15:03:48 <dougsz> So we have two votes on: https://review.opendev.org/#/c/675574 to enable the review priority flag
15:04:47 <dougsz> For those who didn't see the mailing list email, this change enables a vote alongside Workflow and Code-Review in gerrit to set a review-priority.
15:05:23 <dougsz> This then appears in Gerrit dashboards so that you can easily group reviews by priority
15:05:32 <dougsz> It is up to core reviewers to set it.
15:06:06 <witek> #link https://review.opendev.org/#/c/675574 review priority flag
15:06:37 <dougsz> Please vote on the review if you have an opinion
15:06:53 <witek> we
15:07:06 <witek> we've got the third review
15:07:44 <joadavis> looks good. Quick question - will a -1 value prevent it from gating or merging?
15:07:55 <joadavis> this field is just for human use in prioritizing, right?
15:08:15 <dougsz> that's the idea
15:09:01 <dougsz> I would have to check if a -1 prevents gating - I suppose the merge block is also enabled by workflow -2
15:09:08 <witek> `value = -1 Branch Freeze` what does it mean?
15:09:37 <dougsz> I guess this relates to feature freeze
15:10:19 <witek> I think it's a good idea to introduce it
15:11:28 <witek> if we see that it disrupts more than helps, we can still tweak some options
15:11:56 <dougsz> Sounds like a good plan - I have removed my -1
15:12:13 <witek> thanks Doug for proposing this
15:12:13 <dougsz> That's it from me on this one.
15:12:44 <dougsz> np - was inspired by your monasca-common change, thinking about how to get that merged quickly
15:13:13 <witek> :) small advert
15:13:26 <witek> #topic monasca.is is down
15:13:31 <witek> #topic monasca.io is down
15:14:30 <chaconpiza> it is only accessible by https://monasca.github.io/
15:14:46 <witek> I got notified about it yesterday by someone from T-Mobile
15:15:06 <joadavis> I suppose HPE owned that domain registration and lost track of it
15:15:47 <chaconpiza> martinus@natrium:~$ whois monasca.io
15:15:47 <chaconpiza> Domain Name: MONASCA.IO
15:15:47 <chaconpiza> Registry Domain ID: D503300000040570321-LRMS
15:15:47 <chaconpiza> Registrar WHOIS Server: whois.namecheap.com
15:15:47 <chaconpiza> Registrar URL: www.namecheap.com
15:15:48 <chaconpiza> Updated Date: 2019-08-07T22:31:31Z
15:15:52 <chaconpiza> Creation Date: 2015-08-07T15:18:29Z
15:15:54 <chaconpiza> Registry Expiry Date: 2020-08-07T15:18:29Z
15:15:56 <chaconpiza> Registrar Registration Expiration Date:
15:15:58 <chaconpiza> Registrar: NameCheap, Inc
15:16:00 <chaconpiza> Registrar IANA ID: 1068
15:16:02 <chaconpiza> Registrar Abuse Contact Email: abuse@namecheap.com
15:16:04 <chaconpiza> Registrar Abuse Contact Phone: +1.6613102107
15:16:06 <chaconpiza> Reseller:
15:16:08 <chaconpiza> Domain Status: ok https://icann.org/epp#ok
15:16:10 <chaconpiza> Domain Status: autoRenewPeriod https://icann.org/epp#autoRenewPeriod
15:16:12 <chaconpiza> Registrant Organization: WhoisGuard, Inc.
15:16:14 <chaconpiza> Registrant State/Province: Panama
15:16:16 <chaconpiza> Registrant Country: PA
15:16:18 <chaconpiza> Name Server: DNS101.REGISTRAR-SERVERS.COM
15:16:22 <chaconpiza> Name Server: DNS102.REGISTRAR-SERVERS.COM
15:16:24 <chaconpiza> DNSSEC: unsigned
15:17:19 <witek> that supports joadavis assumption
15:17:32 <dougsz> argh
15:18:21 <witek> I think it's worth keeping that domain
15:19:24 <witek> I'll check with Tim, if he can help
15:19:36 <witek> any other ideas?
15:20:02 <sc> I think is just misconfigured as the domain is taken
15:20:37 <dougsz> On the other hand, should we try and put all documentation in one place (OpenStack docs)?
15:21:01 <joadavis> from the output above, you can see the updated date was august 7, so they may have just registered and paid for 4 years which expired
15:21:21 <witek> Domain Status: autoRenewPeriod
15:21:54 <joadavis> yes, OpenStack docs is our source of truth.  monasca.io is just a nice pretty site, but should be directing users to the official documentation for technical details
15:23:54 <witek> dougsz: agree, we should have all technical info in d.o.o, but monasca.io could still act as project `marketing page`
15:24:48 <dougsz> agreed
15:27:29 <witek> I'll also ask Timothy about ownership, it would be nice if we could use this page for the community and update accordingly
15:28:15 <joadavis> Starting with Tim seems like the right answer.  The cost should be low.
15:28:42 <witek> OK, I'll follow up on this
15:29:09 <witek> #topic Confluent Kafka client [monasca-api]
15:29:22 <witek> thanks again for your reviews
15:29:50 <witek> the refactoring to monasca-common has landed and the new tag has been created
15:30:21 <witek> now, I'm waiting for upper-constraints to get updated
15:30:53 <witek> I've also pushed the change for producer in monasca-api
15:31:02 <witek> https://review.opendev.org/676405
15:31:33 <witek> the change is quite simple, but I've tested it with Python 3 only
15:31:50 <witek> and apparently Python 2 CI jobs fail
15:32:07 <witek> so they prove to be useful :)
15:34:05 <witek> after fixing this, together with changes in persister and notification, we'll have all core Python components updated with the new client
15:34:47 <witek> that's all for now to this topic from me
15:35:33 <witek> #topic AOB
15:36:05 <witek> I'll be out of office for the next two weeks
15:36:30 <sc> enjoy your holidays
15:36:38 <witek> thanks :)
15:36:47 <witek> could someone please lead the meetings in that time?
15:37:59 <chaconpiza> I can
15:38:03 <sc> next week I'll OOO, too, I'll be back 26
15:38:15 <witek> Martin: thanks a lot!
15:38:46 <dougsz> I'll be around too, thanks chaconpiza
15:39:05 <chaconpiza> np, have a nice vacation.
15:39:14 <witek> any other topics to cover?
15:39:19 <witek> thanks
15:40:13 <witek> if not, thank you for joining
15:40:41 <witek> bye bye, see you in September
15:41:02 <chaconpiza> thanks
15:41:06 <witek> #endmeeting