20:04:03 #startmeeting horizon 20:04:03 Meeting started Wed Apr 26 20:04:03 2017 UTC and is due to finish in 60 minutes. The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:04:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:04:07 o/ 20:04:08 The meeting name has been set to 'horizon' 20:04:08 hey 20:04:09 o/ 20:04:11 o/ 20:04:16 \o/ 20:04:18 o/ 20:04:21 So, the meeting bot might get muddled; I just started it in openstack-meeting by accident 20:04:34 was wondering where everyone was :) 20:04:36 o/ 20:04:40 Hey everyone 20:04:57 o/ 20:05:16 #topic Notices 20:05:29 There's a couple of things I wanted to raise 20:06:25 Firstly, I'll be away the next 2 weeks, so there'll be no meeting; I'll send out an email as well 20:06:38 One of those weeks is the summit, so I would expect a lot of disruption anyway 20:07:12 The second item is really an appeal for longer term contributors 20:07:42 Despite Horizons activity levels seeming sort of high at a surface level, we're really struggling for people with long term commitments to maintain the codebase 20:07:59 & who understand large portions of the code 20:08:44 If you're interested in becoming core and have the time to commit from your employer etc, please get in touch 20:09:12 I know a couple have messaged recently and I'll be following up with them too 20:09:13 do you have any suggestions for how to build that expertise other than just spending more time on it for now? 20:09:56 Things that I found really useful in terms of building relevant knowledge was reviewing the bug list itself, and then picking out items I knew almost nothing about and fixing them 20:10:37 Reading the bugs gives you a much better grasp of what Horizon is really missing; there is tons of feedback and discussion in there. 20:10:47 reviews help too, same idea pick an area you don't know much about and try to dig deep enough to feel comfortable with the review 20:11:13 I find the comments of other people in the reviews very helpful 20:11:13 very slow at first, admittedly 20:11:27 ask questions 20:11:35 Yeah. And please don't hesitate to give a +1 We totally understand that its a learning process and don't expect reviews to always be perfect/correct 20:11:53 but if you do nothing, we have no way of gauging how to teach 20:12:27 sound like good suggestions, thanks! 20:12:27 So just review to the best of your knowledge, and then give that +/-1. Check the comments from other reviewers and you'll see what you missed :) 20:13:14 Thats all from me anyway in terms of announcements; did anyone have anything else? Otherwise we can just have open discussion. 20:14:46 #topic Open Discussion 20:14:52 are people coming to the forum? 20:15:03 you mean summit? 20:15:03 do we have meeting times and rooms allocated? 20:15:11 it's the forum now 20:15:17 but yes 20:15:29 because name changes = progress :)_ 20:15:36 "summit" was such a vulgar name 20:15:50 I will be there ...do you have any events list for horizon? 20:15:52 someone should update the url https://www.openstack.org/summit/boston-2017/ ;-) 20:16:11 The only sessions we have are project/ops feedback and the project update 20:16:50 I will be there too :) 20:16:57 \o/ 20:16:59 we should at least have a F2F 20:17:21 cool 20:17:24 F2F? 20:17:28 face to face? 20:17:36 yes 20:17:56 ah 20:18:05 something casual? bar? 20:18:21 Or were you looking for a more formal event at the summit to chat Horizon 20:18:27 both 20:19:19 Not sure we'll be able to find official space at the summit at this point 20:19:37 I'm sure there's place to meet 20:19:38 but we could definitely all get together for dinner or something 20:19:51 I'll get in touch with the foundation and see 20:20:01 \o/ 20:20:23 and send out an email about arranging an evening to get together 20:21:20 thanks robcresswell 20:22:28 sounds good! 20:23:18 :) 20:23:45 If anyone wants any further advice on reviewing, bug fixing, learning, other contribution, please just ask. I'm usually on IRC if I'm awake. 20:24:27 ok...will bug ya 20:24:33 I was thinking about proposing some kind of a mentoring program, but then I realized we will do that on IRC anyways 20:24:53 Oh, and one thing I found reeeeally handy when I joined Horizon was just jumping in on IRC to dig into people's bugs. There were a number of things I found, or bugs confirmed just by quick discussions 20:24:54 you just have to ask 20:25:07 rdopiera: Yeah, we're generally one of the more responsive channels with helping people 20:25:33 rdopiera and david-lyle are both cores too, if people didn't know 20:25:40 although david is more like a grand-core... 20:25:50 :D 20:26:02 :) 20:26:13 robcresswell: for a place to meet to talk about stuff there are the hacking rooms we have set aside. 20:26:20 whats the preferred process for getting +2s on changes that have a lot of +1s? I understand this dovetails into the issue from earlier... feels inappropriate to pester the couple of cores that are around a lot about every change, but theres a big backlog on gerrit of stuff waiting for core reviews 20:26:26 diablo_rojo_phon, perfect 20:26:37 diablo_rojo_phon: oo, hacking rooms? Did I miss an email? 20:26:44 jeremy_moffitt: pestering is the only way, though 20:26:49 robcresswell: I can pm you the link to sign up when I get back to my laptop :) It was in an email to the ml too. 20:26:56 Went out a few weeks ago. 20:27:04 jeremy_moffitt: If its been sat a couple of weeks, pester 20:27:05 It's just an ethercalc 20:27:17 Setup like the reservable rooms at the ptg. 20:27:24 diablo_rojo_phon: I'll have a look, thanks! 20:27:26 *especially* if it has +1s already 20:27:30 jeremy_moffitt, also raising wayward reviews in this part of the meeting is acceptable 20:27:40 +1 david-lyle 20:27:42 ok! I just dont want to become mosquito noise 20:27:58 Found the link: https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms 20:28:04 For the sign up anyway. 20:28:45 jeremy_moffitt, honestly we overlook things, reminders are not bad. 20:29:00 diablo_rojo_phon: Awesome, thanks 20:29:01 hourly reminders are another story 20:29:11 lol 20:29:14 great, thanks! delicate balancing act :) 20:29:40 someone will politely let you know if it's too much 20:29:49 Honestly, unless its been <48 hours or something, I would prefer noise and requests to silence and frustrated bug fixers. 20:30:05 < or > 20:30:08 ? 20:30:18 which way is the alligator ? 20:30:23 I got what he's saying, if the last pester was less than 48 hours ago, wait it out a smidge 20:30:37 otherwise, gentle reminders are acceptable 20:30:40 yeah :) or the patch is less than 48 hours old is actually what I meant :) 20:30:42 robcresswell's tired, so I kid 20:30:51 Yeah I did doubt myself haha 20:31:28 I'll check when there are no obvious collisions and put something in the ethercalc for Horizon then 20:33:06 that would be a great time to talk about future direction, so if you have things you're wanting in Horizon, that will be a great time to get agreement 20:33:27 or at least raise awareness 20:34:45 absolutely. We also have an ops/plugin feedback session, so if you're an operator or building a plugin, that would be a good thing to go to 20:35:39 I think we can call it there, if nobody has anything further? 20:36:47 Thanks everyone! 20:36:52 thanks! 20:36:55 thanks! 20:37:00 #endmeeting