08:00:20 <robcresswell> #startmeeting horizon
08:00:21 <openstack> Meeting started Wed May  4 08:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:24 <openstack> The meeting name has been set to 'horizon'
08:00:34 <r1chardj0n3s> o/
08:01:58 <robcresswell> Wow, quiet.
08:02:13 <r1chardj0n3s> well, agreement will come more easily in this meeting :-)
08:02:22 <r1chardj0n3s> so, what big-ticket decisions should we make?
08:02:44 <robcresswell> I'll run through the notices for logs/lurkers anyway
08:02:52 <robcresswell> #topic Notices
08:03:27 <robcresswell> I'm planning the midcycle, there'll be a form of some sort out later today(doodle, probably)
08:03:41 <robcresswell> If anyone wants to volunteer to host or suggest a location, now is the time.
08:04:36 <robcresswell> #info Midcycle planning - suggested dates will be sent out soon. Potential hosts should also speak up :)
08:04:58 <robcresswell> For those not at the summit, the etherpads and their notes can be found here:
08:05:05 <robcresswell> #link https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Horizon
08:06:10 <robcresswell> #info I've brought back the weekly bug report, which is linked in the horizon irc topic.
08:06:23 <robcresswell> #link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport
08:06:45 <robcresswell> That's all for notices I think.
08:07:25 <robcresswell> The only agenda item needs more input, but will mentioned it quickly.
08:07:30 <robcresswell> will mention*
08:07:40 <robcresswell> #topic Earlier feature freeze
08:08:20 <robcresswell> #link http://lists.openstack.org/pipermail/openstack-dev/2016-April/093525.html
08:09:07 <r1chardj0n3s> curses, the archive doesn't follow that discussion well - I guess the message id got lost on the third message
08:09:22 <robcresswell> If you follow the email chain, you'll see a proposed earlier FF (1 week). Another suggestion is to freeze some aspects, like the horizon lib
08:09:27 <robcresswell> Ah, it doesnt
08:09:43 <robcresswell> As it happens, the first two are the valuable ones.
08:09:58 <robcresswell> The request and the releases meeting reference.
08:10:20 <r1chardj0n3s> yep
08:11:18 <robcresswell> #info Proposed earlier feature freeze (R-6). Should we scope to entire codebase, or just horizon/ ?
08:11:37 <r1chardj0n3s> that's an interesting proposition!
08:12:02 <r1chardj0n3s> I heard someone say that plugins often extend openstack_dashboard panels - it'd be good to get more info on that
08:12:11 <robcresswell> It was mentioned a lot this cycle, the pain we're causing plugins.
08:12:14 <r1chardj0n3s> but freezing horizon/ earlier seems reasonable
08:12:36 <robcresswell> Well for the all the internal Cisco work its almost exclusively extend o_d.
08:12:52 <robcresswell> Because we add steps to Routers or Networks etc, or new fields in details pages.
08:13:14 <r1chardj0n3s> right, but hopefully the mechanisms to extend those things are coded in horizon/
08:14:55 <robcresswell> The issue is with the content changing late in the game, breaks things. Because you're still consuming a lot of the code in o_d
08:15:02 <robcresswell> even if the base classes are defined elsewhere
08:15:05 <r1chardj0n3s> right
08:16:26 <robcresswell> Anyway, shifting a week earlier at least gives plugins a bit of breathing room.
08:16:48 <r1chardj0n3s> agreed
08:17:24 <robcresswell> I'll be working on adding liaison roles for the active plugins too, so we can keep in contact better
08:17:48 <robcresswell> I'll bring up this discussion later and then post to the mailer.
08:18:09 <robcresswell> That's everything on the agenda, so I think you can have your evening back r1chardj0n3s :)
08:18:17 <r1chardj0n3s> thanks robcresswell :-)
08:18:40 <robcresswell> #endmeeting