16:00:52 #startmeeting Horizon 16:00:53 Meeting started Tue Jul 22 16:00:52 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:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:57 The meeting name has been set to 'horizon' 16:01:00 Hello everyone 16:01:02 hello o/ 16:01:12 hi 16:01:21 hi! 16:01:23 Hello 16:01:25 hi 16:01:47 hi 16:02:13 hello/ 16:02:17 I think EuroPython is going on right now and we have a few that won't make it to this meeting as a result 16:03:16 J-2 closes on July 24 16:03:42 https://launchpad.net/horizon/+milestone/juno-2 16:03:51 we have a lot of items that still need review 16:04:37 https://blueprints.launchpad.net/horizon/+spec/bootstrap-update is a large item that I would like to discuss first 16:05:13 Tihomir proposed merging it and fixing the bugs related to the merge rather than trying to fix everything up front 16:05:23 I think this is a good idea 16:05:43 o/ 16:05:44 would like to know if there is a strong opposition to this path 16:05:59 +1 16:06:00 none here. Getting that in is the path to getting it right. 16:06:06 +! 16:06:09 +1 16:06:10 +1 16:06:12 +1! 16:06:29 agree. good direction 16:06:44 so horizon in j-2 will have some visual issues 16:07:07 I think that's fine, as it's not the final juno release 16:07:39 it'll be easy to add small patches afterwards :) 16:07:53 s/easy/easier/g 16:08:03 ok, it's on it's long journey through the gate process 16:08:16 should we write bug reports for that or just go off the etherpad list when picking off bugs? 16:08:39 there are a few sahara patches that need another +2 16:09:01 this is another case where I think we can only fix so much before we merge it 16:09:22 clu_ : I would prefer to have real bugs entered vs just a etherpad line of text 16:09:40 remove the most egregious errors and move on to fix 16:10:11 +1 on ericpeterson's suggestion 16:10:11 two items are still blocked by requirements changes 16:10:37 ericpeterson, doug-fish definitely should be launchpad bugs 16:10:57 ericpeterson - okey, will open and tag bug reports with 'bootstrap' or something 16:11:10 clu_: thanks 16:11:23 np :) 16:12:34 so please keep up with the reviews and let's get a few more bps merged into j-2 16:12:44 the rest will slip to j-3 16:13:19 That's the only item I had for the agenda today 16:13:27 #topic Open Discussion 16:13:55 I think you covered my usual bit on sahara merge reviews....thanks. 16:14:13 anyone have some insight into when builds will get a bit more predictable ???? 16:14:35 the gozer / zuul / review jobs / whatever stuff I mean 16:15:46 ericpeterson: not really, there has been some discussion of the problem on the mailing list, but I haven't seen a road to an improvement yet 16:16:32 Clientside table rendering could use some love. https://review.openstack.org/#/c/94706/ 16:16:33 a developer can dream, I guess 16:16:36 unfortunately most of these bugs in the gating process are either race conditions in the tests, or issues in the code illuminated by the timing of the tests running 16:16:52 Not a blueprint, but a bug fix I'd love to se go into j-2: https://review.openstack.org/#/c/91338/ It's an enabler for making better translations for other panels too. 16:17:46 doug-fish I like fixing the issue, but oh my the solution is ugly 16:18:06 no offense to ygbo 16:18:19 lol 16:18:25 yeah, i think it can be done in a smaller patch 16:18:49 you went from a one line class property to many line of method call for every action 16:19:10 heres something else to consider doug, the angular patch im introducing will help with translation as well 16:19:14 seems like we could make it more developer friendly to get right 16:19:26 everything gets serialize to json, including the batch action names 16:19:39 I'll leave my comments, as I see I forgot to last time I looked at the patch 16:19:42 if anyone is already tired with modal forms losing modality when FileInput appears, the patch https://review.openstack.org/#/c/107769/ is ready for review 16:20:13 david-lyle: cool, thx - will be good to get attention on that and see if those concerns can be addressed 16:20:29 tsufiev: YES!!! 16:20:43 tqtran: I actually didn't realized the angular fix would change that processing, I'll have to look at that more closely. 16:20:48 clu_, I know you would be interested :) 16:21:02 tsufiev: I'll take a look 16:21:22 david-lyle, thank you :) 16:22:53 doug: it doesnt fix the processing, but it does make it easier 16:23:01 tqtran: I'm trying to make it to the clientside table patch 16:23:12 david: awesome =) 16:23:47 would love to get some feedback from others before you get there 16:24:31 BTW, I would like to know some pointers related to review guidelines. I think there are some references on I18N and UX review guidelines but I couldn't find them so far... 16:24:49 if anyone has links, it will be appreciated. 16:25:06 maybe https://wiki.openstack.org/wiki/I18n/TranslatableStrings 16:25:27 doug-fish: thanks. that's what I am looking for. 16:25:32 cool, yw 16:26:05 i will add it to https://wiki.openstack.org/wiki/Horizon/Reviews after the meeting. 16:27:59 If anyone knows good guidelines or referecens for reviews, please add information to the above page. I would like to collect pointers to share. 16:31:26 Also appreciate a good guideline for exception handling in Horizon. Have notice quite bit of code catched the exception, but lost it when present to the user. 16:33:14 just typed some stuff in the wrong window 16:33:16 :)_ 16:33:28 amotoki: As a newbie, a central place with pointers to documentation would be extremely helpful 16:33:35 let's review this to make sure it's accurate and helpful 16:33:49 https://review.openstack.org/#/c/100718/ 16:34:08 the old tutorial is just cruel 16:34:13 david-lyle, thanks 16:37:11 Any additional items? 16:38:25 just something in the back of my mind, we need more code control for javascripts 16:38:42 code control? 16:38:49 like verification tools? 16:38:51 some files define functions a certain way, others a another way 16:38:59 and the styling is all over the place 16:39:44 yes 16:39:49 :) 16:39:49 thinking of jshint settings? 16:40:04 yes =) 16:40:18 i think we should recommend a tool/plugin for people to use with certain settings 16:40:31 that way, its all consistent and easier to review/read/code 16:40:54 I'm sure I saw I patch to intergrate jshint into our automated testing 16:40:54 jshint plugs into most editors 16:41:04 but can't recall where it is just now 16:41:18 we've gone through a round of jshint standardization, there is a bp to use node based tools in the dev environment 16:41:29 doug-fish: there was a license issue 16:41:39 was merged, pulled back out in icehouse 16:41:43 "do no evil" 16:41:49 is it this patch? 16:41:49 https://review.openstack.org/#/c/97237/ 16:41:53 I thought there was a new and improved version that came about later 16:42:07 ah 16:42:22 tzumainn, yeah that's it! 16:42:43 whoa, totally missed that 16:42:47 thanks 16:43:21 I assume the license problem was with jshint and not with node? 16:43:29 right 16:43:47 The jshint developer added an extra clause to the license 16:44:03 which causes lawyers great concern 16:44:07 lol 16:44:23 yep, I've run into the "do no evil" clause before 16:44:38 "do no evil" sounds like google 16:46:23 Did the jshint license cause it to be pulled from the build? Still OK for dev environments? 16:47:01 so whats is the procedure to formalize/propose code styling guidelines? 16:47:26 rbertram certainly okay for dev environments 16:47:28 i think jshint is nice to have, but we should provide an independent guideline that "could" work with jshint 16:47:33 well, unless you are using it for evil. :-) 16:47:49 the "evil" is more a problem for distros 16:49:18 if we pass DFSG and Fedora, it is okay in most cases :-) 16:49:23 tqtran: I agree. The guideline should cover the kinds of things jshint covers, and some other things specific to AngularJS and jQuery. 16:50:14 tqtran: volunteering? 16:50:23 david: sure =) 16:50:23 * david-lyle ducks 16:50:29 lol 16:50:41 tqtran: I'll be glad to help 16:50:50 tqtran, rbertram: thanks 16:50:53 rbertram: awesome, thanks 16:52:31 i would like to know your opinion on extension supported aliases in api/neutron.py. 16:52:38 https://review.openstack.org/#/c/74066/8/openstack_dashboard/api/neutron.py 16:53:31 amotoki: seems like we should have a generalized capabilities method for neutron that is memoized 16:53:41 in api/neutron.py there are several number of wrapper methods for extension, but most of them are unnecesssrty 16:53:43 is a general method not supported in neutron 16:54:29 is_extension_supported() method is already memoized. 16:54:59 So I think we don't need wrapper methods per extension. 16:55:07 amotoki: so it is, and I agree 16:55:30 didn't expand enough code above before 16:56:02 david-lyle: thanks. i will ask patch authors to remove them and i will clean up existing ones. 16:56:44 amotoki: thanks for point it out, I think sometimes gerrit collapsing unchanged code is a disservice 16:57:10 s/point/pointing/ 16:57:21 david-lyle: that's all I have after catching up horizon reviews :-) 16:58:02 Let's call it. Thanks everyone. Keep up with the reviews and have a great week. 16:58:07 #endmeeting