15:01:47 #startmeeting horizon 15:01:47 Meeting started Wed Mar 10 15:01:47 2021 UTC and is due to finish in 60 minutes. The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:50 The meeting name has been set to 'horizon' 15:02:08 hi 15:02:13 hello 15:02:16 o/ 15:06:08 hi 15:06:20 let's start. I hope amotoki will join us soon 15:07:04 * e0ne #topic Notices 15:08:13 Xena PTG has been scheduled on 19-23 of April 15:08:20 registration is free 15:08:31 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020778.html 15:09:04 I hope everybody will join and we'll have a good number of conversations 15:09:18 again virtual ptg:( 15:09:47 vishalmanchanda: covid-19 situation is pretty bad still :( 15:10:02 yeah....... 15:10:58 congrats vishalmanchanda as our new PTL for Xena release! 15:11:06 #link https://governance.openstack.org/election/ 15:11:19 hehe thanks:) 15:11:30 vishalmanchanda: thanks for volunteering for being a PTL 15:12:34 looking forward to it. 15:12:43 Let's see how it goes. 15:13:23 everything will be good, I'm sure :) 15:13:32 vishalmanchanda: don't worry 15:13:32 I'm sure you will smash it 15:14:18 I hope you guys will continue to contribute in next cycle. 15:14:24 vishalmanchanda: +1 15:14:34 Sure! 15:15:11 let's finish some Wallaby businesses before 15:15:15 #link https://releases.openstack.org/wallaby/schedule.html 15:15:56 this week is a feature freeze and soft string freeze 15:16:51 after this milestone, only bugfixes are allowed 15:16:59 sorry for late. I watched two cycling races in parallel and didn't notice the time :p 15:17:31 technically, horizon uses other release model, but it's good to follow these milestones 15:18:36 folloing the feature freeze sounds fair. 15:20:04 amotoki: it's not fair that burton us cup cancelled but cycling championships are going :( 15:20:33 e0ne: hehe 15:21:57 do we have any unmerged feature proposal? 15:22:12 hopefully most tnings can recover in either of new or exsiting sways :) 15:22:31 s/sways/ways/ 15:22:35 the one about autofocus on login screen 15:22:52 I didn't find anything in the list https://review.opendev.org/q/project:openstack/horizon+status:open #link 15:23:15 I've added the discussion of it to agenda 15:23:22 tmazur: I prefer to treat it as bugfix 15:23:40 e0ne: even if we agree to add a new setting? 15:23:55 oh... I missed it 15:24:00 one more reason to not add a new setting ;-) 15:24:07 haha 15:24:12 let's discuss it in a dedicate topic anyway 15:24:18 yes 15:24:19 amotoki: +1 15:24:59 anyway, that's all updates from my side 15:25:24 one thing from me 15:25:25 e0ne: we also have to add Wallaby Cycle Highlights by this week. 15:25:35 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020900.html 15:26:03 vishalmanchanda: thanks for a reminder. I'll go via release notes and propose a patch today 15:26:16 e0ne: thanks. 15:26:24 I think that putting the domain field at the top is wrong 15:26:35 It should be below the password 15:26:36 amotoki: please continue. 15:26:37 field 15:26:50 Many web sites do that that way 15:26:52 ikanias: we will discuss it later in this meeting 15:26:59 sure 15:27:03 ikanias: we are in the "Notices" section 15:27:11 Renaming Chinese locales landed successfully. I confirmed all translation jobs worked as expected. 15:27:20 I hope all plugins can cut a release including it. 15:27:24 amotoki: awesome! 15:27:32 amotoki: great. 15:27:33 thank you for handling that 15:27:35 freezer-web-ui is the only plugin which does not merge it. 15:27:49 but what we can do is just to wait for them 15:28:09 most plugins landed translation imports, so it would be no problme. 15:28:14 that's all from me. 15:28:32 amotoki: thanks a lot for driving this effort 15:28:53 yw 15:29:44 let's move to the next topic 15:30:07 I don't know who added it but I like it 15:30:15 it was me 15:30:39 #topic Promoting Tatiana to core. 15:30:47 I would like to propose tmazur as a core reviewer 15:31:06 She has a long history with the horizon project 15:31:43 It would be great to have tatina in our core-team:) 15:31:59 #link https://www.stackalytics.io/?module=horizon-group&metric=commits&user_id=tmazur 15:32:07 #link https://www.stackalytics.io/?module=horizon-group&user_id=tmazur 15:32:49 will it be a double-horizon-core or just a second time horizon-core? 15:32:59 haha 15:33:08 I don't know :) 15:33:18 tmazur: oof, you still count as Mirantis! 15:33:28 in stackalytics 15:33:33 🙂 15:33:39 surprising.... 15:33:48 Yesss, I remember there were some difficulties with affiliation changing 15:33:54 tmazur: you can push your info to the stackalytics repo 15:34:03 rdopiera: me too... 15:34:32 I guess I even should contact someone directly 15:34:54 not like it's critically important 15:34:56 https://review.opendev.org/q/project:x%252Fstackalytics+status:open 15:35:32 rdopiera: definitely 15:36:20 aside from that, I am fine to add her to the core team. it would be a nice improvement to cover more areas deeply. She is familiar with angular area. 15:36:20 tmazur: AFAIR, there was some json file in the repo with mapping. I'll let you know once I find it 15:36:25 I need to do the same 15:36:33 e0ne: ok, thanks! 15:37:06 And thanks everyone for promoting me! 15:37:07 tmazur: I also have experience on stackalitics thing. we can help you. 15:37:19 tmazur: Congrats! 15:37:25 we have the technology ;-) 15:37:27 it looks like we have a consensus. 15:37:32 I will proceed with doing my best for Horizon ;p 15:37:44 I think we've got an agreement and there is no need to make a voting in a mailing list 15:37:47 amotoki: thanks! 15:37:56 do you need to nominate her officially in the mailing list or is it an apporval? 15:38:13 e0ne: you are faster than me. 15:38:51 amotoki: I'll send a mail to the ML just to make it a bit more official :) 15:38:57 IMO It is better to announce on mail chain as well as per openstack docs. 15:39:10 but since all cores agreed, we don't need a voting 15:39:28 of course, rdopiera can change his vote ;) 15:39:37 i think the notice would be fine 15:39:45 amotoki: +1 15:40:03 tmazur: welcome back to the team! 15:40:21 Woohoo! Happy to be back! :D 15:40:27 tmazur: Congrats:) 15:40:48 tmazur: welcome :) 15:41:48 #topic Login page autofocus discussion 15:42:02 #link https://review.opendev.org/c/openstack/horizon/+/777690 15:42:15 So we have a few options here 15:43:04 I don't really want to introduce a new config option for it 15:43:07 To add a new setting to shift it wherever we want, to pick the Domain field only when it's empty and to shift the Domain field to the bottom 15:44:36 at the staring point, the current behavior is to focus on "domain" field even if "domain" field is filled with the value used previously. 15:44:43 I think that putting the domain field at the top is wrong from UX point of view 15:44:48 I introduced the new setting solution but after a discussion we had with rdopiera and ikanias it seems not a good solution now 15:45:00 ikanias: why do you think so? 15:45:09 ikanias: do you have any examples of other services that put the username first? 15:45:23 ikanias: username is unque inside a domain 15:45:36 In all my previous apps I worked for the domain was always last to appear 15:45:59 I will get examples if you wish 15:46:21 a used ID can determined as a combination of username and domain name (or ID). 15:46:47 considering this, putting "password" field between "user" and "domain" is a bit confusing to me 15:46:54 but others can have other opinions. 15:47:14 amotoki: not between, after the password 15:47:30 amotoki: oops, please ignore 15:47:35 tmazur: np 15:47:36 amotoki: Username and password ahould always be one below the other IMO 15:47:50 amotoki: but that is the administrator's point of view, the users themselves don't think about themselves as belonging to a domain 15:49:03 amotoki: it's more like selecting where to log in for them 15:49:08 where they want to go 15:49:43 especially since often they may have logins in multiple domains 15:49:55 amotoki: I think we also need to be aligned to the rest of the web apps that exist 15:50:17 ikanias: good point. do you have examples by the hand? 15:50:39 I remembers that windows login page has "domain" selection at the bottom. 15:50:39 e0ne: currently no but i will get you 15:51:00 ikanias: it will be useful 15:51:13 e0ne: sure will work on it after the meeting 15:51:32 from my PoV, I prefer to have such order: 1)domain 2)login 3)password 15:51:35 Windows XP at least, yes 15:51:54 but in anyway, I don't want to introduce a new config option for it 15:53:16 I see less value in a new setting too 15:53:36 https://duckduckgo.com/?q=login+screen+domain+-windows&t=canonical&iar=images&iax=images&ia=images 15:53:49 a quick search shows that it seems to be a pattern 15:54:02 I remember seeing somewhere login - domain - password too... 15:54:18 http://2.bp.blogspot.com/-hVhEQWgDVLY/ULtR1Uq3CCI/AAAAAAAAA6M/BLOoFSv0Wkw/s1600/db3fde3a98cfc4eb3b2bd264bc8caeec-761004.jpeg 15:54:37 most examples have only user nad password fields though... :( 15:55:21 but the ones that have a domain field, have it last 15:55:22 The oracle example has a domain below 15:55:29 probably because of Windows 15:55:42 I would expect everyone to copy Windows 15:55:45 http://2.bp.blogspot.com/-hVhEQWgDVLY/ULtR1Uq3CCI/AAAAAAAAA6M/BLOoFSv0Wkw/s1600/db3fde3a98cfc4eb3b2bd264bc8caeec-761004.jpeg 15:56:22 oh yes, market leader ;-) 15:56:34 I believe that if ORACLE uses this method then it is a good one 15:56:39 :-) 15:57:03 While I still think the order of domain->user->password as natural, I have no strong opinion. 15:57:19 If we move the domainf field to the bottom, do you no longer need a new setting? 15:57:45 amotoki: yes, we will just have a focus on user field 15:57:54 as the first one 15:58:22 I agree that it is more logical, but habit trumps logic 15:58:38 okay.... I always feel frustrated in the login form of Windows when switching a domain though 15:59:22 we've got one minute left 15:59:40 let's continue in #openstack-horizon channel 15:59:55 yes 16:00:06 it looks better to confirm our consensus. let's contineu in #-horizon 16:00:22 #endmeeting