16:01:29 #startmeeting Horizon 16:01:30 Meeting started Tue Aug 12 16:01:29 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:01:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:33 The meeting name has been set to 'horizon' 16:01:39 Hello everyone 16:01:48 hello 16:01:51 hi 16:01:52 hi 16:01:54 hello o/ 16:01:54 hi all 16:01:54 Hello 16:02:00 hi 16:02:15 <_crobertsrh> hello/ 16:02:15 o/ 16:02:21 Hello 16:02:32 Hi 16:02:50 hi 16:02:58 So today is feature proposal freeze for Horizon in Juno 16:03:24 I've moved ours ahead of the main OpenStack deadline because we already have so many items in flight and review 16:03:26 hello 16:03:37 adding more will just make landing things more difficult 16:04:15 of course, as with all things, there is an exception process but you request would have to be, well, exceptional :) 16:04:37 Perhaps we should notify the dev list as well? 16:04:53 ah yes the mailing list, sure 16:05:11 will do 16:05:20 Cool! 16:05:39 before we jump into the agenda, I just want to look at j-3 status 16:05:46 #link https://launchpad.net/horizon/+milestone/juno-3 16:06:06 blueprints: 4 Unknown, 11 Started, 6 Slow progress, 7 Good progress, 28 Needs Code Review, 7 Implemented 16:06:16 still cleaning up items 16:06:34 there are a few at the top I'd like to get a better status on 16:06:45 https://blueprints.launchpad.net/horizon/+spec/remove-javascript-bundling 16:07:02 rdopieralski: how are you feeling about this 16:07:11 how can we change the delivery status? 16:07:30 I know we were set back a bit with the plugin update 16:08:20 david-lyle: I had to change the versions of the xstatic packages several times already, and each time the change has to go through global-requirements, which makes it slow. I hope that the current change is the last one required, and that it will get merged soon, but I have no guarantees. 16:08:53 david-lyle: so basically I'm waiting for https://review.openstack.org/#/c/113184/ to be merged 16:09:24 rdopieralski: understood, I feel like we can land this 16:09:40 david-lyle: we will need to re-update the bootstrap wizard plugin after that, but that can hopefully be done in a separate patch 16:10:03 david-lyle: also, the bootstrap will be unbundled in a separate patch 16:10:24 we have ~3 weeks 16:11:04 https://blueprints.launchpad.net/horizon/+spec/launch-instance-ux-enhancement 16:11:08 seems to have stalled 16:11:23 anyone have an update or should I look to move to Kilo? 16:11:39 the patch is marked WIP 16:12:08 if we think high priority items aren't going to land, it's better to move them out earlier 16:12:15 MaxV: do you know? 16:12:55 rdopieralski, david-lyle: currently working on it with UX team 16:13:11 but it is slow progress 16:14:31 MaxV: what are the chances of finishing it on time> 16:14:37 ? 16:14:45 rdopieralski: can you remind me the deadline? 16:14:51 Sept 4 16:14:56 is the merge deadline 16:14:58 ouch 16:15:07 that's how we all feel :) 16:15:44 I may allow an exception for this, if it's really close by sept 4 16:16:12 but we shouldn't count on that time 16:16:35 I'll wait a week and see where we stand 16:16:35 hope the best expect the worse 16:16:46 MaxV: Are you blocked by UX? 16:16:59 we did the user testing 16:17:09 but there is some changes 16:17:18 (quite a lot) 16:17:39 yeah…all good ones at least :) But yes, lots to do I'm sure. 16:18:21 I can "try" to have a patch in two weeks 16:18:28 It will be really hard 16:19:20 MaxV, keep us posted, I would really like to see this land 16:19:35 thanks 16:19:38 is there anything anyone else can help you with? 16:21:04 clu_ https://blueprints.launchpad.net/horizon/+spec/client-side-pagination introduces a new js library, which is contradictory to the first bp we discussed, your change just got a lot more complicated 16:21:34 just so you're not surprised 16:21:43 thanks 16:21:46 david-lyle: o.O uh oh 16:22:17 clu_: I can package it for xstatic, but as everything it will need to go through infra review in global-requirements 16:22:33 clu_: where the packagers for different distros can veto it 16:23:02 The Launch Instance UX patch also introduces several new javascript libraries 16:23:08 just one 16:23:19 same thing applies 16:23:23 the bootstrap binding in angular 16:23:25 rdopieralski: that would be great 16:23:33 MaxV: will want to start the requirements process now to have any chance 16:23:44 MaxV: better package it early then, so that we have time for reviews 16:23:51 +1 16:23:53 I will remade the patches for the messages 16:23:59 and the accordion 16:24:09 MaxV thanks! 16:24:18 and ping radomir for his help on packaging the lib 16:24:20 If some parts can be broken down into multiple patches already, so that they can reviewed already that'd be cool too 16:24:52 I though about that 16:25:01 Cool :) 16:25:35 I will release patches during the week 16:26:01 generally speaking it is sometimes difficult to deal with patches which requires new js libs, ie xstatic packing and global-requirements. 16:26:04 for the next meeting in order to have visibility 16:26:40 I am sure rdopieralski will help me on this :) 16:26:43 can we merge new js libs into the repo once and unbundle it? Or do we require xstatic packaging and global-requirements update? 16:27:01 rdopieralski: I assume we were using this one: https://pypi.python.org/pypi/XStatic-JQuery.TableSorter/2.14.5.1? 16:27:10 amotoki: no, because then the packagers are screwed, as they won't be able to package horizon for their distros 16:27:14 amotoki: sorry for the language 16:27:28 clu_: yes 16:27:50 amotoki: the whole point is that they review the new dependency before it gets in 16:28:46 rdopieralski: sounds reasonable. I just would like to clarify the merging policy. 16:28:50 amotoki: the distros end up removing the embedded js anyway and replace it with the system packe, this is cleaner for them 16:29:05 s/packe/package/ 16:29:10 they don't want unpatched security holes 16:29:12 rdopieralski: ok thx 16:29:25 or multiple versions to maintain 16:30:31 amotoki: so the policy moving forward should be no more embedded 3rd party js libraries added 16:30:44 into the Horizon code base, only as dependencies 16:30:57 thanks. i believe i understand the background why we need to unbundle js libs. I just would like to clarify the *process* of proposing new libs. 16:30:59 I will write an e-mail about that to the -dev list tomorrow 16:31:12 david-lyle: or would you like to do it? 16:31:31 rdopieralski: I can do that, I'd like to add it to the developer docs too 16:31:33 coming from the ptl it would be more official 16:31:54 Wiki page would be good too for reference 16:32:08 Or I guess the dev docs if it's a policy 16:32:31 we have a section on js policy in the dev docs already 16:32:33 wow, 3 places is a lot. I was cool with 2 but 3 is more than I can handle 16:32:39 jpich: we can add a link to dev docs in wiki page. 16:32:40 :) 16:33:17 let's jump into the planned agenda 16:33:21 amotoki: Sure, one place is totally enough! I think we underuse the wiki sometimes, but as long as there's a doc somewhere I'm happy 16:33:45 I think we've touched on the first couple a bit, but 16:33:55 #link https://wiki.openstack.org/wiki/Meetings/Horizon 16:34:09 #topic xstatic-* repositories and their release process (rdopieralski) 16:34:29 so, now that we have all the stackforge/xstatic-* repos, we need to agree on a policy for updating and reviewing them 16:34:47 I had the infra people add horizon-core and horizon-ptl to xstatic-core and xstatic-ptl respectively 16:35:01 so you can all review the patches there 16:35:17 I started adding .gitreview files to those repos, so there are already some patches for review 16:35:28 also the upstream changes, which are, admittedly, a little messy 16:35:38 there's not a shortcut for adding all xstatic repos to my gerrit watch list I suppose? 16:35:42 but they are aready released, so we probably want to sync to that 16:35:53 david-lyle: I'm afraid not 16:35:58 david-lyle: gerrit-dashboard can do it. 16:36:19 rdopieralski: Is there a bug tracker for the xstatic projects? 16:36:25 oslo team does the similar. 16:36:35 david-lyle: I would also want to ask you to tag the released versions, if you have time, or add me to xstatic-ptl so that I can tag them 16:36:45 amotoki: like an xstatic wildcard? 16:36:46 jpich: no 16:36:56 david-lyle: yes 16:37:05 can we also update angular to v1.2.16 (or preferably v1.2.20) 16:37:12 ooh, I'll have to update my dashboard, thanks 16:37:36 it is the example of oslo: https://github.com/stackforge/gerrit-dash-creator/blob/master/dashboards/oslo-program.dash#L4 16:38:11 rdopieralski: Ok! So when it affects Horizon, simply file a Horizon bug even if the fix will be elsewhere 16:38:17 bluex-pl: Why? 16:38:21 jpich: yeah 16:38:42 jpich: there is a bug that is fixed in it 16:38:58 rdopieralski: send me a list of repos that are ready to tag 16:38:59 jpich: there is a bug with number validation ‌in current AngularJS 16:39:14 currently used in Horizon 16:39:25 rdopieralski: I guess we'll need to reference the new library requirement in Horizon anyway 16:39:42 Cool, if it fixes bugs let's 16:39:44 jpich: to resolve https://review.openstack.org/#/c/110578/ 16:40:06 jpich: the bug: https://github.com/angular/angular.js/issues/2144 16:40:14 Gerrit query "project:^stackforge/xstatic.* status:open" works too. https://review.openstack.org/#/q/project:%255Estackforge/xstatic.*+status:open,n,z 16:40:48 Ok 16:40:54 jpich: the thing is, debian testing has 1.2.16 16:41:07 jpich: so they will most likely veto anything higher 16:42:16 rdopieralski: If it's resolved in 1.2.16 sounds like a reasonable update to me, and sufficient for the requirements bump? Distros can package the most recent version if they prefer 16:42:24 *Other distros 16:42:27 jpich: yes 16:42:31 Sweet 16:43:28 so we can try the process for upgrade on that 16:44:07 1. send a patch to gerrit and have it merged, 2. have new version released to pypi, 3. add it to global-requirements and have it merged there, 4. add it to horizon 16:44:54 I wonder how much of it can happen in parallel 16:44:59 ;) 16:46:19 It'll be exciting to find out :-) 16:46:36 alright time is tight, let's move on 16:46:49 #topic the split (rdopieralski) 16:47:10 ok, so shortly 16:47:18 I don't think the split will happen this cycle 16:47:32 rdopieralski: I think you are correct 16:47:39 even if we are on time with patches, I think it's much better to do it early K 16:47:42 Milestone 3 isn't the best time for a change like that 16:47:50 happy to get the js out in this release 16:47:57 and be better staged for K 16:48:28 that's it about the split :) 16:49:03 Thanks rdopieralski! 16:49:08 thanks 16:49:24 #topic angular localization (TravT) 16:49:29 we have a question on localizing angular loaded partials in horizon - is there already a best practice for this documented anywhere? 16:49:39 I put up an etherpad with more info: #link https://etherpad.openstack.org/p/horizon-angular-partial-localization 16:49:51 so if anybody can help out, it'd be appreciated. 16:50:27 TravT: the only work so far with angular localization was done with the clientside tables patch 16:50:32 let me grab the link 16:51:06 https://review.openstack.org/#/c/94706/53 16:51:25 + 16:51:36 unfortunately tqtran is not here now, but you may want to ping him directly 16:51:50 ok. I can do that. 16:52:06 Cool! Hope we can document such new best practices somewhere, even quickly in a wiki page :-) 16:52:32 will do 16:52:36 tqtran may have, I just don't have the link handy 16:52:54 Cool! 16:53:02 We're still working on general JS best practices, maybe part of that 16:53:18 do we have a particular place for it? 16:53:31 not yet - open to ideas 16:53:49 ok 16:53:57 Idea: https://wiki.openstack.org/wiki/Horizon/Javascript , linked back from the Horizon main wiki page? 16:54:18 good starting point 16:54:20 that is memorable 16:54:23 works for me 16:54:29 jpich: ok, will tell Thai 16:54:47 I'll email tqtram about this as well 16:54:55 TravT: anything else? 16:55:06 no, guess not for now 16:55:11 thanks! 16:55:17 #topic Open Discussion 16:55:24 not much time left, but have at it 16:55:39 how can delivery status be changed (from code review to implemented) in here https://launchpad.net/horizon/+milestone/juno-3 16:55:59 david-lyle: still concerned about Bootstrap 3 bugs? I tagged one, but not approved yet. 16:55:59 I will change it once it's merged 16:56:24 david-lyle: so it will be changed for after merged? 16:56:38 nlahouti: Needs review is the correct state for now 16:56:54 There's a gerrit hook that updates the status 16:56:58 in case somebody missed last message about Merlin plans for PoC on ML (I made kind of announcement couple of weeks ago here), here it is: http://lists.openstack.org/pipermail/openstack-dev/2014-August/042128.html 16:57:00 nlahouti: yes, I will manually update it 16:57:07 david-lyle: even if the implementation is done. 16:57:07 jpich not for bps 16:57:15 I missed the meeting last week as I fall asleep. Regarding compiled message catalog, i agree it is better we keep the current in Juno and discuss about the policy of OpenStack projects as a while in Kilo. 16:57:25 * tsufiev unfortunately forgot to add it to the agenda 16:57:26 david-lyle: Really? I thought there used to be 16:57:30 implemented indicates it has merged into horizon tree 16:57:44 david-lyle: thx . got it 16:57:46 jpich, not that I've seen 16:57:56 david-lyle: My bad, ok! 16:58:14 jpich, I wish 16:58:28 Yeah 16:58:42 amotoki: +1 16:58:46 I must have seen it in a dream then 16:58:46 this message had some ideas about collaboration with Horizon, so please do not hesitate to respond :) 16:58:56 amotoki: Sounds good to me too 16:59:09 tsufiev: I'm ok doing the library work in Horizon proper if you are 16:59:46 david-lyle, what is the proper way of doing library work in Horizon? 16:59:58 david-lyle, just to make sure we understand each other :) 17:00:08 tsufiev: ping me after this, we're out of time 17:00:16 #endmeeting