13:06:40 #startmeeting 13:06:40 Meeting started Wed Jul 8 13:06:40 2015 UTC. The chair is danielhb. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:06:40 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:06:47 #meetingname scrum 13:06:47 The meeting name has been set to 'scrum' 13:06:54 #info Agenda 1) Status 2) Open discussion 13:07:06 anyone wants to add anything for today's agenda? 13:07:21 it is good for me 13:07:33 moving on in 10 13:07:45 #topic Status 13:07:46 #info Please provide your status using the #info command: #info 13:08:32 #info danielhb set up OFTC bot to host the scrum meetings while alinefm is away 13:09:12 #info danielhb set up a temporary repository to push community patches and fixes during alinefm absence 13:09:51 #info alinefm pushed new branches upstream do handle different types of development: master (current release devel), next (new features), wok (wok framework + new UI) 13:10:29 #info alinefm there is also a branch named new-ui which is based on master branch but I suggest to have the new UI devel done on wok to avoid conflits when pushing everything to a new release 13:10:39 #info ziviani is working on PCI hotplug feature for kimchi 13:10:48 #info Status samhenri reviewing Bootstrap CSS and Foundation 5 for the new-ui, working on wok branch 13:12:17 samhenri, any conclusion on which one would be good to use for kimchi? 13:13:41 well, i think you can find more resources for bootstrap than foundation 13:14:11 so people developing plugins wouldn't have any trouble with the ui 13:16:39 Foundation is mobile-first oriented 13:17:33 and this is something that i believe is not covered in the new ui proposals 13:18:08 samhenri, well... UI and responsive design is definitely important. But the main focus of the community has been on web browsers... so your analysis is correct. 13:18:16 s/UI/mobile 13:20:59 anything else ? 13:22:50 lgarcia, what do you mean by UI/mobile? is this on the wiki? 13:24:09 samhenri, I was actually trying to say that where I said UI in the first sentence, I was meaning mobile 13:24:32 samhenri, mobile and responsive design are important... but, as you said, focus has been in web browsers 13:24:48 ah, ok 13:24:51 samhenri, I don't think there was suggestions around mobile interfaces yet 13:25:43 samhenri, lagarcia does Bootstrap provides support to more desktop browsers than foundation? because if that's the case + more resources available ...... 13:26:23 #info ramonn pretend to solve pci caching today. Also, will investigate bug about "handler exception: WSRequestHandler instance has no attribute 'last_code'" 13:30:02 the main difference is that foundation was built thinking in mobile interfaces and responsiveness first. Bootstrap has a lot of styles that we don't end up using, however you can find several themes, js plugins and other resources 13:30:41 that can speed up kimchi plugins development 13:32:38 and it seems that foundation 5 is not fully supported by IE9 13:33:12 samhenri, from what you're saying I believe bootstrap is the winner 13:33:45 samhenri, and after you said about foundation not fully supported in IE9, definitely the winner 13:34:27 samhenri, we definitely do not want to face avoidable, annoying problems with IE or even Safari 13:34:49 yes, Safari is the new IE 13:35:10 samhenri, and perhaps Bootstrap has some mobile support? I think in our case it is better to have a solid desktop UI with a 'best effort' mobile support than the other way around 13:36:26 it does have media queries but it is kinda heavy 13:37:01 samhenri, I see 13:38:02 samhenri, well, your call obviously, just doing my uninformed backend python guy opinion hehehe 13:39:20 samhenri, you can focus on the latest browser versions, ie, IE9 is a little bit old 13:39:25 as we ar eon IE 11, right? 13:39:30 yes 13:39:42 and the new Edge browser coming with Windows 10 13:40:01 alinefm, by that logic IE is old news. we need to support Spartan 13:40:07 lol 13:40:52 I'm going to switch the CSS files to Sass, that way I can choose which Bootstrap modules I'm going to load and it also makes support for older browsers easier 13:42:07 samhenri, please, as soon as you have something barely working, share with the community. That way others can see what you are doing and even give a try... don't wait to have a fully complete working solution before submitting it for review. 13:42:17 If we have to support older browsers, I just send a parameter to sass and it will compile with prefixes for last gen browsers 13:42:35 sure 13:42:39 samhenri, that sounds good to me 13:43:01 samhenri, and as lagarcia said feel free to send an email to Kimchi ML with your findings 13:43:48 ok 13:43:52 one more thing 13:44:28 can somebody send me kimchi logo in higher resolution? 13:45:04 alinefm, ^ 13:45:11 in the pdf we have a file named kimchi.png 13:45:34 samhenri, the logos available are in the git repository 13:45:40 otherwise we need to build new ones 13:45:49 samhenri, you can check on ui/images directory 13:45:59 the current version in the wok branch is logo-white.png 13:47:56 I got confused because in the pdf it has a different name and doesn't have kimchi text on it 13:48:43 samhenri, everything in the PDF is a mock up 13:48:51 the file names can not be the same on there 13:48:58 but since it has a transparent background I can use it 13:48:59 we can rename the files if needed 13:49:15 to get closer to the definition doc 13:49:45 ok, the same goes for the svg icons for the OS, right? 13:50:38 correct 13:50:59 ok 13:51:11 I saw you bug related to the svg icons (sorry to don't replay on github) but we need to pass through a legal process to include trademarks into Kimchi 13:51:22 so we need to contact, red hat, microsoft, etc 13:52:39 oh, i see 13:52:54 let's move the discussion to the open discussion topic 13:52:59 #topic Open Discussion 13:59:03 alright, let's end the scrum today. thanks for joining! 13:59:05 #endmeeting