16:00:22 #startmeeting Horizon 16:00:23 Meeting started Tue Apr 29 16:00:22 2014 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:26 The meeting name has been set to 'horizon' 16:00:35 morning dansmith 16:00:40 erm 16:00:42 morning david-lyle 16:00:44 hi everyone 16:00:49 good morning 16:00:49 o/ 16:00:51 Hey 16:00:52 hi akrivoka - feeling better? 16:01:05 hi 16:01:06 jrist: yes! all better now :) 16:01:08 jrist: thanks! 16:02:19 hiya! 16:02:36 hi all! 16:02:41 hi =) 16:02:52 I really only wanted to use today to discuss the proposed session schedule for the summit and hopefully address any conflicts before the schedule is finalized. 16:03:10 hello 16:03:10 http://junodesignsummit.sched.org/overview/type/horizon 16:03:23 as this is the "off week" 16:03:25 :) 16:03:55 david-lyle: thanks very much for switching my session yesterday…Sounds like we will be able to reschedule the conflict we are having with the Horizon/Ops session…so it looks great to me :) 16:04:07 lblanchard: excellent 16:04:18 thanks for the flexibility 16:05:21 the tripleO sessions all fall after the Horizon, so that should be ok. Does anyone else have a conflict that prohibits their participation in a session they are leading? 16:06:24 I did double up several sessions slots, I think we will still be ok time wise. 16:07:20 As for the logistics around the sessions... Typically there will be a unified cross-project page to link all the session etherpads from 16:08:31 once we have that, if the topic owners would create an etherpad for their session/part of session and fill in whatever content they feel relevant to their part, typically an outline, link to related bps, even discussion topics 16:08:35 david-lyle: https://wiki.openstack.org/wiki/Summit/Juno/Etherpads 16:08:39 that will help the flow of the sessions 16:09:09 ah, thanks lblanchard 16:09:11 noticed an e-mail on the TripleO list this morning about the wiki for Etherpads… 16:10:27 then the flow of the sessions for those who haven't participated before, is usually the floor is given to the individual who proposed the topic and they can present/lead a discussion, and others will take additional notes on the etherpad 16:11:14 This not a formal talk, but an interactive discussion and there will be questions input, requests for input, etc 16:11:51 +1 16:11:52 there will be a project to for demo/sharing etc 16:12:14 oh nice 16:12:30 cool 16:12:50 does anyone have questions? I know we have some new folks that have topics, so I wanted to give you an idea what the expectations are, if you just want to start the conversation that's fine too 16:13:56 easy enough :) 16:14:06 #topic Open Discussion 16:14:12 david-lyle: all sounds great to me! 16:14:48 I have one topic 16:14:58 sure 16:15:21 * lsmola is looking forward to his first OpenStack summit 16:15:26 we had a debate with MaxV about the ethics of monkey patching, here is the relevant patch: https://review.openstack.org/#/c/80990/ 16:15:27 * jrist too 16:15:44 I think the comments tell it all 16:16:13 we couldn't decide if monkey patching is ok or not, se we wanted to get some other opinions about it 16:17:19 I give -1 to monkey patching 16:17:27 pbelanyi_: so we have a select few cases of monkey patching in Horizon now 16:17:57 the one I can think of is related to django/auth 16:19:40 The monkey patch approach has the advantage of not requiring the tests to be changed when it gets removed later. And it would happen in one of the test files (test settings) 16:20:03 or we stop supporting django 1.4 16:20:13 I don't have a super strong opinion on it either way, up to the patch author to decide IMO :) 16:20:53 * pbelanyi_ feels the power flowing through him 16:20:58 lol 16:21:34 hehe 16:21:53 never thought I'd call a monkey patch elegant, but it feels more elegant than the other proposed solution 16:22:27 Django 1.4 is listed as a LTS upstream and supported until March 2015, it'd be nice to keep supporting it as long as it's not an otherwordly effort to do so imo 16:23:54 well, it seems to me there is slightly more support for the monkey patch, so I think I'll submit it and see if it gets pluses 16:24:01 thanks for the feedback! 16:25:07 jpich, I don't think we're rushing to remove support for 1.4 16:25:34 dansmith: Sounds good to me, that was in reply to your comment :) 16:25:52 just that it will happen, after we all long forget what patch_bug_1273943() related to 16:26:03 haha 16:26:43 anyone else have anything, or should we pretend we take off weeks off 16:29:16 may I ask for someone to look at https://review.openstack.org/#/c/90997/ - it is required by a tuskar UI patch 16:29:45 akrivoka: sure 16:29:46 actually quick question, how stable is wifi during the summit? 16:29:53 david-lyle: thanks David 16:30:05 akrivoka, I'm still taking a look as well, although my voting powers are far less : ) 16:30:14 tqtran: quite stable usually 16:30:37 some sites like the summit schedule and etherpad sometimes topple under the load 16:30:40 tzumainn: they are very much appreciated, nonetheless! thanks! 16:30:44 for short periods of time 16:30:53 there's also a long forgotten patch needing some attention: https://review.openstack.org/#/c/58214/ 16:32:00 that is long in the tooth :( 16:32:41 many reviews in general are needed 16:33:18 remember non-core reviews help a great deal as well, I know a lot of people are active reviewers and that is greatly appreciated 16:33:26 review all the things! 16:33:36 :) 16:34:33 I think we can call it early today. Thanks everyone. Have a great week and pretend to be off for a little while this week. 16:34:38 #endmeeting