[13:51] <Guest77794> TigerLuo
[13:54] <JackYu> hi, all
[13:54] <csslayer> hi
[13:55] <JackYu> csslayer, hi
[13:55] <TigerLuo> hi
[13:57] <JackYu> ypwong, it seems that my VPN got some problem, would you please help to chair the session first.
[14:01] <maclin> csslayer, hi
[14:15] <csslayer> maclin: sorry for interrupt.. is there a link for hangout?
[14:15] <maclin> https://plus.google.com/hangouts/_/3f399901093affca6063d4113420c6417b76ccef?authuser=0&hl=en
[14:15] <jzheng> csslayer, https://plus.google.com/hangouts/_/3f399901093affca6063d4113420c6417b76ccef?authuser=0&hl=en
[14:18] <csslayer> maclin: thanks!
[14:18] <jzheng> csslayer, discussion is taken following "Whiteboard" on https://blueprints.launchpad.net/ubuntukylin/+spec/client-1305-ubuntukylin-applications-development
[14:19] <maclin> csslayer:welcome
[14:25] <PHLin> Some personal suggestion: mute you mic when you're not talking
[14:25] <PHLin> Background noise is annoying
[14:57] <app_>  总结work item 没有
[15:01] <smartboyhw_> Hi UbuntuKylin people;)
[15:10] <kgunn> I would think you would want to support ARM
[15:11] <liuxingapp> may be
[15:12] <ypwong> http://releases.ubuntu.com/raring/
[15:15] <kgunn> i assume you will want to support ubuntu touch in the near future as well
[15:16] <liuxingapp> i think so it will support ubuntu touch ,may be develop app for ubuntu touch for chinese
[15:16] <kgunn> today ubuntu touch development is happening on ARM
[15:16] <kgunn> for the following devices
[15:17] <kgunn> galaxy nexus & nexus4
[15:17] <liuxingapp> yeah
[15:17] <kgunn> it might be possible for you to leverage all that work (kernel/bootloader etc)
[15:17] <kgunn> and test against those devices
[15:17] <liuxingapp> yes test nexus4
[15:17] <kgunn> wonder if QA team might be able to help with testing/using their infrastructure
[15:18] <smartboyhw> balloons: ^
[15:20] <liuxingapp> weather forecast for ubuntu touch UI look like nice
[15:25] <kgunn> wonder if its using a program/binary name to create the string ?
[15:25] <kgunn> bregma: ^
[15:25] <kgunn> bregma: they are saying the "unity desktop" string can't be localized?
[15:25] <liuxingapp> yes
[15:26] <bregma> I can't find anything in the code like that, it may be a visual asset
[15:26] <liuxingapp> i think it shoud can define for user
[15:26] <bregma> at any rate, it needs a bug filed so we can follow up
[15:27] <liuxingapp> i read unity code it write 'ubuntu desktop'
[15:29] <zhangchao>   the language package translate  "unity desktop"  to “ubuntu桌面”
[15:31] <zyga> QUESTION: is there a seed file for ubuntu kylin
[15:31] <ypwong> zyga, nope
[15:31] <zyga> so that it can be installed remotely with netboot
[15:32] <zyga> can we make one?
[15:59] <zyga-uds> hi
[16:00] <liuxingapp> good bye
[16:02] <gema> hi
[16:02] <gema> do we have a link to the hangout?
[16:03] <ypwong> zyga, i am not sure, do you have more information about that?
[16:09] <roadmr> yay we have video
[16:10] <roadmr> good/bad as in "works/doesn't work"? or do you want something quantitative so you can rather say "better/worse than yesterday?"
[16:10] <kgunn> QUESTION: will this include mobile/arm platforms (of any kind)
[16:11] <roadmr> but just a % is somewhat meaningless, right? what if it's 99% good but the 1% that's bad is what I need?
[16:12] <zyga> ypwong: sure, sorry
[16:12] <kgunn> just my 2 cents - for the most part app developers want to know what is stable (e.g. subsystems, i can use audio but not camera)
[16:12] <gema> kgunn: yes
[16:12] <gema> kgunn: wanna join the hangout?
[16:12] <zyga> ypwong: I'd like to create a virtual machine or a netbooted phyisical machine that runs ubuntu kylin
[16:12] <kgunn> whereas OEM's will care about "performance indicators"
[16:12] <zyga> ypwong: to do that I need to know the set of packages that go into ubuntu kylin
[16:12] <gema> kgunn: I am not sure if they'll care
[16:12] <gema> we'll show the reference devices that are in the lab, ideally
[16:13] <kgunn> gema: sure
[16:16] <balloons> from a community perspective, we would love to see a page tracking what's "good", what's "bad" currently in the dev release
[16:16] <roadmr> balloons: +1
[16:16] <balloons> that can help drive efforts for everyone from development to QA to tester
[16:20] <josepht> doanac: +1
[16:22] <victorp_uds> gema, I dont think OEMs are going to be looking at it as such
[16:22] <gema> victorp_uds: good point
[16:22] <victorp_uds> maybe developers at the OEM team will, but they will have the same req that community guys
[16:22] <gema> victorp_uds: ack
[16:24] <balloons> this isn't really the session to bring it up, but hey, kgunn is here :-) I'd like to see smoke testing for the display stack (aka, Xorg and most importantly, Mir)
[16:24] <gema> cjohnston: can you mute yourself whilst typing?
[16:26] <kgunn> balloons: whatcya thinkin' ?....i'm more familiar with mir, where there's tons of unit testing & example clients
[16:27] <kgunn> and i'm working with ThomiR on adding stress testing
[16:27] <kgunn> which we think we might do short run stress testing to add in for CI of MP's
[16:27] <balloons> kgunn, I saw the sessions but wasn't quite able to attend them sadly
[16:27] <cgregan_uds> This sounds familiar
[16:28] <balloons> kgunn, unit and stress testing is great.. I'm speaking of more at a system and integration level. I suppose the unity tests might solve some of this. But, I would like to see the display stack being run across a plethora of hardware
[16:29] <balloons> there's a bunch of configurations.. drivers + graphics cards that it would be good to have some basic assurance is working properly
[16:29] <kgunn> balloons: yeah, totally agree...i think system/integ tests are needed (as we finally get unity8 shell running on mir)
[16:29] <alesage> gema, how did you do bootspeed, did you set a threshold, e.g.?
[16:29] <kgunn> balloons: wrt hw configs, i would say pick 1 to hold as kind of golden
[16:30] <kgunn> e.g. you would gate release on
[16:30] <gema> alesage: bootspeed is a trend graph
[16:30] <balloons> kgunn, yes on the ubuntu touch stuff, we get a bit of a pass because we can control the hw :-)
[16:30] <gema> alesage: we keep measuring and show a line as we go
[16:30] <kgunn> but to gate on multiple hw configs isn't realistic
[16:30] <balloons> so phablet isn't so bad
[16:30] <kgunn> balloons: actually...its just as bad....
[16:30] <balloons> on the desktop, grabbing the big 3, with open/closed drivers is sufficient
[16:30] <kgunn> balloons: we're just limiting exposure :)
[16:31] <roadmr> how do you identify inflection points in the graph that need your attention? manually?
[16:31] <balloons> so intel/amd/nvidia with amd open/closed, nvidia open/closed
[16:31] <kgunn> balloons: agree on desktop approach
[16:31] <balloons> kgunn, ofc, ofc.. It's only a baseline for assuring it works
[16:32] <balloons> but I think that small number of setups should be doable for smoke testing
[16:32] <kgunn> balloons: i do agree tho, mobile oem's will do loads of testing for tuning to their hw config....so they will understand
[16:32] <kgunn> if we test against say nexus4 or something its  really only "reference"
[16:33] <cgregan_uds> In the dashboard we spec'd a year ago the user determined the limits for notification which was stored in a db
[16:43] <tvoss> gema, what is the eta for getting an iteration 0 up?
[16:45] <tvoss> gema,  is there a blueprint that tracks this?
[16:45] <gema> tvoss: yes, it's linked to the session, it's the qa-dashboard one
[16:45] <cjohnston> tvoss: https://blueprints.launchpad.net/ubuntu/+spec/qa-s-dashboard is the dashboard BP
[16:45] <tvoss> gema, cjohnston thanks
[18:08] <ptl> has the session started?
[18:08] <cyphermox> ptl: yes
[18:08] <pitti> there's no video yet
[18:08] <cyphermox> can you see the video?
[18:09] <roadmr> cyphermox: ?! I have no video?
[18:09] <cyphermox> just a second
[18:09] <roadmr> thanks!
[18:09] <cyphermox> sorry, it wasn't on air yet
[18:09] <cyphermox> seeing us now?
[18:09] <sforshee> I don't see any video yet
[18:10] <ptl> me too
[18:10] <roadmr> cyphermox: nope, "please stand by"
[18:10] <ptl> *neither
[18:10] <cyphermox> should be a few seconds we're supposed to be on air now
[18:10] <pitti> ah, now
[18:11] <ptl> yes
[18:11] <josepht> awe: yes
[18:11] <ptl> I can see the video
[18:11] <cyphermox> there's a slight delay it seems :D
[18:11] <tedg> I can see it!
[18:11] <sergiusens> awe_: yes
[18:11] <plars> yes we can
[18:11] <ptl> and 3G data
[18:12] <ptl> we need 3G data \o/ till the end of this month :P
[18:14] <cyphermox> if anyone things they should join the actual hangout, ping me plz
[18:14] <cyphermox> *thinks
[18:14] <cyphermox> or ping jasoncwarner :D
[18:15] <seb128> cyphermox, you guys should just share the link on IRC ;-)
[18:15] <seb128> cyphermox, I've been doing that and there was no issue so far
[18:15] <jasoncwarner> https://plus.google.com/hangouts/_/621c24ff5f6a9e6a9bf540260cb27ea0275cc9c7?authuser=0&hl=en
[18:16] <cyphermox> jasoncwarner: thanks!
[18:17] <tedg> \o/
[18:17] <tedg> cyphermox, Those are tracked in the indicator-backend blueprints
[18:17] <tedg> https://blueprints.launchpad.net/ubuntu/+spec/indicator-backend
[18:22] <cyphermox> ack
[18:29] <tedg> awe_, oh no, it was already confusing enough with the number of ricardo's that we had!  ;-)
[18:32] <sergiusens> awe_: cyphermox yeah, I can do it
[18:32] <pitti> awe_: wrt udev, did you happen to try the current version in my PPA by any chance?
[18:33] <cyphermox> pitti: I have not, remind later
[18:33] <pitti> awe_: I know upstream systemd has done quite a lot of work to make all this work in containers
[18:33] <awe_> pitti, no I haven't
[18:33] <pitti> otherwise, please feel free to give me a WI to investigate thsi
[18:33] <awe_> the bigger problem is that we're running android components which consume uevents
[18:34] <pitti> hm, uevents are not meant to be "consumed" though?
[18:34] <pitti> but I don't know what android changed in that regard
[18:34] <awe_> pitti, maybe we can talk after the session
[18:35] <awe_> I can't follow both threads at simultaneously
[18:35] <pitti> *nod*
[18:36] <tedg> Doesn't that require some UI changes?  (WPA Enterprise)
[18:36] <awe_> yes
[18:36] <tedg> It seems like we wouldn't be able to prioritize that work...
[18:36]  * tedg is worried enough about the work items he has
[18:36] <tedg> I think that's a 14.04 thing, not a 13.10 one.
[18:39] <tedg> I think that we probably have a req open for the network UI work... if someone is here and interested
[18:39] <tedg> awe_, cyphermox, ack
[18:41] <sergiusens> cyphermox: mtp had patent issues I've been told
[18:41] <sergiusens> mtp server that is
[18:44] <cyphermox> tedg: what do you mean open req?
[18:44] <cyphermox> tedg: I spoke to mpt about it, he knows my concerns, but I did mention it wasn't a priority
[18:44] <tedg> Employee position.
[18:45] <cyphermox> I'm just trying to avoid people pain when wpa enterprise (or anything else really) needs to be added and dramatically changes the design
[18:45] <cyphermox> because that would just be sad
[18:46] <awe_> pitti, the short answer re: udev is that when we started it in our container... it caused breakage in our images, so we disabled it
[18:47] <cyphermox> awe_: btw, bluetooth session in a few hours at Google IO...
[18:47] <pitti> awe_: I have a current (from yesterday) phablet install on my n7, so I can test a current version there
[18:47] <awe_> I believe we could make it work, however no work has progressed on this due to our work to try and verify the container flip
[18:47] <pitti> awe_: what should I look out for, i. e. how does the breakage manifest?
[18:48] <awe_> pitti, you'd have to ask ChickenCutlass
[18:48] <awe_> but again, I think we want to see how ogra makes out on the container flip work
[18:48] <pitti> awe_: curious that nothing in our image actually listens to uevents; I had assumed that not much will work at all without them
[18:48] <pitti> awe_: ack
[18:48] <pitti> awe_: ok, let me know if you need anything
[18:48] <awe_> pitti, will do