15:02:58 #startmeeting horizon 15:02:58 Meeting started Wed Sep 5 15:02:58 2018 UTC and is due to finish in 60 minutes. The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:02 The meeting name has been set to 'horizon' 15:03:07 hi everybody 15:03:17 o/ 15:06:49 amotoki, dklyle, betherly_ : are you around? 15:07:30 o/ 15:07:42 o/ 15:07:48 sorry im late 15:09:36 ok, let's start 15:09:49 #link https://wiki.openstack.org/wiki/Meetings/Horizon 15:09:58 #topic Notices 15:11:15 We'd got Rocky release last week 15:11:27 thanks everybody for contributions! 15:11:54 hi 15:12:31 \o/ 15:12:35 amotoki: hi 15:12:36 #topic OpenStack PTG 15:12:45 we'll have PTG next week! 15:12:55 #link https://etherpad.openstack.org/p/horizon-ptg-planning-denver-2018 15:13:50 after the conversation with amotoki, I would like to move most of proposed topic to Tuesday 15:14:14 since on Monday there'll be operators meetup and few WGs sessions 15:14:35 I'll send a mail with proposed schedule tomorrow 15:14:38 and other cross project sessions 15:14:48 amotoki: +1 15:15:27 please, add your name at the topic you're interested in, so we can adjust a schedule to get more attendees 15:15:54 and you can add your topics to the etherpad too 15:16:12 I think we'll have enough time to discuss anything needed 15:17:14 also, we can get some food and drink on Monday somewhere nearby if people want it 15:18:17 any more comments about the PTG? 15:19:14 sounds like we've done with it 15:19:31 I hope to get good conversations in Denver next week 15:20:11 if nobody argue, I'll drop few topics from the agenda on this meeting 15:20:33 they were added as priorities for Rocky release and it worked good 15:21:01 I would like to do the same for Stein release right after the PTG 15:21:23 #topic Removing Inactive Cores 15:21:45 it's pretty sad, but we need to do it to keep project healthy 15:22:11 I sent a mail to the openstack-dev@ mailing list earlier this week 15:22:13 #http://lists.openstack.org/pipermail/openstack-dev/2018-September/134211.html 15:22:16 #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134211.html 15:23:03 if there are no objections, I'll cleanup horizon-core team in gerrit today and ask stable team to do the same for horizon-stable-maint group 15:23:37 amotoki, dklyle, rdopiera: are you OK with this? 15:24:03 +1 15:24:10 I would like to get some confirmation from the core team 15:25:07 the horizon stable team was not updated for a long time just because it is managed by the stable maint team. 15:25:11 I think, we can discuss how can we attract new reviewers at the PTG 15:25:16 amotoki: +1 15:25:25 +1 15:25:40 +1 15:26:03 e0ne: by the way, I got an e-mail from launchpad telling me my membership is expiring 15:26:13 thanks for the confirmation, guys! it's great to know that we're on the same page 15:26:42 rdopiera: AFAIK, you can re-new your membership in the launchpad group by yourself 15:27:07 e0ne: it told me to contact you or dklyle 15:27:09 e0ne, I think you need admin righst 15:27:13 I need to check if it works for horizon-drivers group 15:27:14 *rights 15:27:58 dklyle: thanks for the information 15:28:45 rdopiera: me or dklyle will update your membership date :) 15:28:56 much appreciated! 15:29:15 rdopiera: np 15:29:24 #topic Bug Triage 15:29:26 other members have no expiration date. I wonder why it is set only to rdopiera... 15:29:49 amotoki, rdopiera: fixed 15:29:53 oh, that's because I'm evil >:) 15:30:08 rdopiera: :) 15:30:09 LOL 15:30:30 amotoki: thanks for bug triage reminder 15:30:35 sometimes I was lazy about that :) 15:30:49 so many mouse clicks 15:30:59 poor mice 15:31:14 they really do have a raw deal 15:31:20 IMO, it's my fail because all mails from launchpad was filtered in my mail client and moved to some non-popular folder 15:31:29 does anyone subscribe launchpad notification for new bugs? 15:31:42 amotoki: I fixed it on Monday :( 15:31:54 I do, but then I filter them all into a separate mailbox that I never look at... 15:32:00 my plan is pretty simple 15:32:03 rdopiera, +1 15:32:09 and I really want to follow it 15:32:43 hehe 15:32:57 I'll check all bugs on weekly basis and send email to openstack-dev@ with a numbers how many bugs were fixed, reported, triaged 15:33:31 I added a weekly task in my calendar each Thursday 15:33:59 I hope, we'll clean up our new non-confirmed bugs queue pretty quick 15:34:08 amotoki: does this sounds good for you? 15:34:47 e0ne: it works but I am a bit afraid you try to do too much :) 15:35:01 amotoki : I'm asking you because your proposed this topic to the agenda 15:35:24 amotoki: let's try to do it and see how is going 15:35:29 sounds good 15:35:39 I usually subscribe two types of bug mails; new and all. 15:36:02 btw, I finished with our product last week, so I'll have more time for upstream work next months 15:36:09 I can know if someone triages a bug by receiving followup bugs mails. 15:36:31 amotoki: I did the same, but filter was broken and all mails were just archived :( 15:37:01 maybe I have to clean up my gmail filters 15:38:02 can we move to the next topic? I've got one more for this meeting 15:38:44 let's move on 15:38:49 ok:) 15:39:00 #topic horizon review inbox 15:39:34 we've got about ~120 open patches in the gerrit 15:39:49 not a big number even for a small team 15:40:18 but there are a log of old patches if -1 from 2017 15:40:53 I know that sometime people just haven't time to address comments 15:40:59 I would be skeptical about them ever merging 15:41:38 there was this "abandoned due to inactivity" thing? 15:41:44 but I think it should be ok to abandon some old patches. e.g.: all patches with no updates for the last 3-4 months 15:41:50 people can always reopen them 15:42:02 rdopiera: that's what I'm talking about 15:42:23 #link https://github.com/openstack/horizon/blob/master/tools/abandon_old_reviews.sh 15:42:28 I think we always did it after a release or something like that? 15:42:41 I just don't want to do it without notification 15:43:05 yeah, I add that script 15:43:20 dklyle: I'll test it soon :) 15:43:47 it's some kind of task which we missed during the last release 15:43:47 it posts info in the review that it was abandoned by script for being stale and gives the criteria 15:44:13 and instructions on how to make it active again 15:44:24 it's very satisfying to run :) 15:44:42 IIRC I clean up several numbers of stale patches which were apparently unnecessary manually at the beginning of Rocky cycle. 15:44:50 There are two types of patches: new features and bug fixes. I tend to open bug fix reviews at that time. 15:45:12 automatic cleanup would be nice 15:45:34 but hopefully someone can take over bug fix patches. 15:45:39 I'll do it today or tomorrow 15:46:22 amotoki: I added some patches to my list to check if that bugs are still actual 15:46:37 e0ne: nice :) 15:47:11 that's everything I've got for the meeting today 15:47:29 we've got a bit more time to discuss anything else 15:48:04 oh.. one more 15:48:20 we'll skip a meeting next week 15:48:52 of course 15:48:55 a lot of people will be at the PTG 15:49:07 I'll send a note to the mailing list 15:49:35 I wonder if we could also update the egenda on the wiki every time the meeting is skipped 15:49:45 to say it's cancelled 15:49:57 rdopiera: good point 15:50:28 anything else to discuss today? 15:51:16 seems that we've done 15:51:31 thanks everybody who joined this meeting today! 15:51:44 I hope to see all of you next week at the PTG 15:51:54 #endmeeting