[09:05:48 CDT(-0500)] <cindyli> Justin_o, michelled, with regards to the renaming of UIO to prefs framework, the last remaining issue as I know is whether the demo that uses grade components should be moved into manual tests. do we have a decision on that?
[09:08:27 CDT(-0500)] <michelled> I think it should be moved
[09:08:45 CDT(-0500)] <michelled> cindyli: we are expecting most people to use the schema, right?
[09:12:30 CDT(-0500)] <cindyli> michelled: yes, i agree. Justin_o, anastasiac, let me know if you have another opinion. otherwise, i will start moving it
[09:19:37 CDT(-0500)] <Justin_o> cindyli: i also think it should be moved
[09:20:15 CDT(-0500)] <cindyli> ok
[09:32:24 CDT(-0500)] <Justin_o> jhung: I merged in your GPII-204 pull request
[09:33:06 CDT(-0500)] <jhung> Thanks Justin_o
[10:01:21 CDT(-0500)] <cindyli> michelled: i sent a pull request for UIO renaming - https://github.com/fluid-project/infusion/pull/414 Can you review it when you have a chance?
[10:02:39 CDT(-0500)] <michelled> thanks cindyli, Justin_o will take a look at it
[10:02:48 CDT(-0500)] <cindyli> ok. thanks
[12:07:53 CDT(-0500)] <Justin_o> michelled: did you fix for the styling on the contrast panel go in?
[12:08:19 CDT(-0500)] <michelled> I think so Justin_o - I saw the pull request close
[12:08:42 CDT(-0500)] <michelled> and it looks fixed on the nightly build too
[12:08:53 CDT(-0500)] <Justin_o> michelled: great thanks
[12:08:59 CDT(-0500)] <michelled> np
[12:19:06 CDT(-0500)] <clown> jhernandez, ping
[12:44:33 CDT(-0500)] <Justin_o> cindyli: did you want help with the build related comments i left on the pull request?
[12:45:15 CDT(-0500)] <cindyli> Justin_o: yes
[12:45:40 CDT(-0500)] <cindyli> Justin_o: have you done with all the reviews?
[12:46:27 CDT(-0500)] <Justin_o> cindyli: i think so
[12:46:34 CDT(-0500)] <cindyli> i left a comment regarding moving UIO demo to framework demos. I don't see such a directory for framework demos, or you meant to create one?
[12:46:45 CDT(-0500)] <Justin_o> i replied to that one
[12:46:55 CDT(-0500)] <cindyli> cool. thanks, will take a look
[12:47:08 CDT(-0500)] <Justin_o> basically there is no directory for it.. but it's organized in the demo portal.
[12:48:20 CDT(-0500)] <cindyli> cool. got you, Justin_o
[12:49:42 CDT(-0500)] <Justin_o> anastasiac, cindyli: any thoughts about renaming generateUIOThemes. I'm thinking generatePEThemes or generatePrefsEditorThemes
[12:50:06 CDT(-0500)] <Justin_o> The first is shorter, but could be confused with progressive enhancement or something else
[12:50:25 CDT(-0500)] <cindyli> +1 on the second
[12:50:52 CDT(-0500)] <anastasiac> +1 on the second one, Justin_o
[12:51:04 CDT(-0500)] <Justin_o> cindyli, anastasiac: thanks
[12:52:45 CDT(-0500)] <jhernandez> clown: pong
[12:52:57 CDT(-0500)] <clown> hi jhernandez
[12:53:05 CDT(-0500)] <clown> did you see my email from Friday?
[12:53:09 CDT(-0500)] <jhernandez> of course
[12:53:18 CDT(-0500)] <jhernandez> :]
[12:53:34 CDT(-0500)] <clown> did you get chance to look at the new version of the tests?
[12:54:03 CDT(-0500)] * clown waiting for another "of course"
[12:54:15 CDT(-0500)] <jhernandez> heh
[12:54:23 CDT(-0500)] <jhernandez> of course, but didn't tried them
[12:54:49 CDT(-0500)] <clown> okay. I was just worried that you didn't know about them.
[12:54:51 CDT(-0500)] <jhernandez> it's time to try them, right now!
[12:55:03 CDT(-0500)] <clown> But you are aware of them, and it is a work in progress.
[12:55:08 CDT(-0500)] <clown> oh, okay. Cool.
[12:55:41 CDT(-0500)] * clown waiting for comments and requests for changes.
[12:55:53 CDT(-0500)] * jhernandez pulling your branch ...
[12:56:47 CDT(-0500)] * clown crosses fingers
[12:58:25 CDT(-0500)] <jhernandez> you don't have to
[12:58:32 CDT(-0500)] <jhernandez> you're a rock star!
[12:58:33 CDT(-0500)] <jhernandez>
[12:59:16 CDT(-0500)] <jhernandez> and ... re your friday's email
[12:59:27 CDT(-0500)] <jhernandez> you don't have to create another pull request
[13:00:16 CDT(-0500)] <jhernandez> just keep commiting on the same branch, and the commits will be included in tue pull request
[13:00:17 CDT(-0500)] <clown> ah, okay. I was wondering about that.
[13:00:31 CDT(-0500)] <clown> cool. I guessed correctly!
[13:00:35 CDT(-0500)] <clown> wonders never cease.
[13:00:43 CDT(-0500)] <jhernandez> yup!
[13:01:19 CDT(-0500)] <clown> what do you think about the console.log()s I put in? I put them there to get some idea of what was being tested, but is there a better way?
[13:06:02 CDT(-0500)] <jhernandez> i am ok with that
[13:06:11 CDT(-0500)] <clown> \o/
[13:06:16 CDT(-0500)] <jhernandez> (and with the latest changes ofc)
[13:08:08 CDT(-0500)] <clown> so, in terms of mechanics, does this mean you pull into your branch and this work is finished (for now)?
[13:09:45 CDT(-0500)] <jhernandez> merged
[13:11:08 CDT(-0500)] <jhernandez> now we have a packagekit add-on within their associated tests in jqUnit
[13:11:22 CDT(-0500)] <clown> okay.
[13:11:57 CDT(-0500)] <clown> what does this mean about my "packageBridgeTests" branch? I guess I just switch to your branch, and do an update.
[13:12:19 CDT(-0500)] <clown> something like git pull --rebase.
[13:12:39 CDT(-0500)] <jhernandez> now, we have almost the same with Android (still working on it because I still need to add install and remove capabilities)
[13:13:02 CDT(-0500)] <clown> that's good, jhernandez.
[13:13:09 CDT(-0500)] <clown> it's good that it's mostly "common".
[13:13:18 CDT(-0500)] <jhernandez> yeah, now switch back to my branch, fetch my repo and pull from it
[13:13:30 CDT(-0500)] <clown> Okay.
[13:14:50 CDT(-0500)] <Justin_o> cindyli: I've fixe the two build related issues in my FLUID-5161 branch
[13:15:02 CDT(-0500)] <Justin_o> cindyli: did you need help with any of the other parts?
[13:15:10 CDT(-0500)] <clown> I'm thinking the next step is more unit tests, but from a webserver perspective, along the lines of these tests: https://github.com/javihernandez/linux/tree/packagekitBridge/node_modules/gsettingsBridge/tests
[13:15:26 CDT(-0500)] <clown> (that's a weird url).
[13:15:42 CDT(-0500)] <cindyli> thanks, Justin_o, i will merge in your branch. can you take a look on contrast icons
[13:15:53 CDT(-0500)] <Justin_o> cindyli: sure will do
[13:16:00 CDT(-0500)] <cindyli> thanks, Justin_o
[13:16:05 CDT(-0500)] <Justin_o> cindyli: can you also double check my changes when you pull them in
[13:16:14 CDT(-0500)] <cindyli> sure
[13:16:18 CDT(-0500)] <Justin_o> thanks
[13:18:15 CDT(-0500)] <jhernandez> clown: more or less
[13:19:41 CDT(-0500)] <clown> I'll make a start on it, then.
[13:20:03 CDT(-0500)] <jhernandez> right now we should start thinking on the deviceReporter integration from the core architecture perspective
[13:20:26 CDT(-0500)] <clown> okay.
[13:20:57 CDT(-0500)] <clown> so, what is the core architecture (the matchmaker?) expecting to get from us?
[13:21:06 CDT(-0500)] * clown thinking out loud
[13:21:15 CDT(-0500)] <Justin_o> cindyli: fixed the contrast panel.. seems like we lost something in a merge somewhere.. but it's all sorted out now... you can pull it down from my branch
[13:21:21 CDT(-0500)] <Justin_o> cindyli: need help with anything else?
[13:21:45 CDT(-0500)] <clown> correction: what is the matchmaker expecting to get from the deviceReporter?
[13:22:28 CDT(-0500)] <jhernandez> to do that, I have to finish my non-sent-mail, resuming the current status of our device reporting in Linux and Android and my thoughts about the next steps
[13:23:26 CDT(-0500)] <clown> okay, over to you jhernandez
[13:23:28 CDT(-0500)] <jhernandez> the core architecture == core's deviceReporter, yes
[13:23:56 CDT(-0500)] <cindyli> that was fast, Justin_o. thanks. other than text size you've noticed, i found line spacing also doesn't apply to the iframe, do you want to take a look on that?
[13:24:13 CDT(-0500)] <jhernandez> and re the matchMaker, not sure
[13:24:19 CDT(-0500)] <Justin_o> cindyli: sure i'll take a look at those
[13:24:27 CDT(-0500)] <cindyli> thanks, Justin_o
[13:25:00 CDT(-0500)] <clown> i'm just wondering what part of the architecture is getting information from the deviceReporter — I thought it was the matchmaker, but I shall review.
[13:28:57 CDT(-0500)] <jhernandez> clown: as a clue, our deviceReporter should prvovide the information from this static payload: https://github.com/GPII/universal/blob/v0.2/testData/deviceReporter/linux_installedSolutions.json
[13:29:18 CDT(-0500)] <jhernandez> heh, look at the architecture overview
[13:30:15 CDT(-0500)] <clown> jhernandez, I just took a peek at "A Detailed Tour of the Cloud4all Architecture", and it looks like the deviceReporter interfaces with the soutionsRegistry.
[13:30:43 CDT(-0500)] <jhernandez> http://wiki.gpii.net/index.php/Architecture_Overview
[13:30:47 CDT(-0500)] * clown looks at static payload link
[13:31:47 CDT(-0500)] * clown at the architecture overview links.
[13:32:05 CDT(-0500)] <clown> okay, device reporter interfaces with the flowmanager.
[13:32:46 CDT(-0500)] <clown> but the numbers (1, 2, 3, …) suggest that the flow manager passes the results of the deviceReporter to the matchmaker.
[13:33:23 CDT(-0500)] <clown> jhernandez: http://wiki.gpii.net/index.php/A_Detailed_Tour_of_the_Cloud4all_Architecture
[13:34:04 CDT(-0500)] <clown> especially http://wiki.gpii.net/index.php/A_Detailed_Tour_of_the_Cloud4all_Architecture
[13:34:11 CDT(-0500)] <clown> whoops.
[13:34:17 CDT(-0500)] <clown> I mean, especially: http://wiki.gpii.net/index.php/A_Detailed_Tour_of_the_Cloud4all_Architecture#Device_Characteristics_Reporter
[13:36:10 CDT(-0500)] <jhernandez> the numbers are meaning the workflow steps, yes
[13:36:56 CDT(-0500)] <jhernandez> and the wiki is fine too
[13:38:34 CDT(-0500)] <jhernandez> in fact, I started a new add-on
[13:38:58 CDT(-0500)] <jhernandez> this time, an xrandr one
[13:39:40 CDT(-0500)] <jhernandez> with this add-on, we will be able to get/set the screen capabilities (screen resolution, brightness, gamma ...)
[13:40:35 CDT(-0500)] <clown> neat
[13:41:40 CDT(-0500)] <jhernandez> and it could be used both by the deviceReporter (to get information) and by a settingsHandler (to get/set settings)
[13:41:40 CDT(-0500)] <jhernandez> clown: does it sounds funny?
[13:42:10 CDT(-0500)] <clown> funny? no. It sounds clever.
[13:50:39 CDT(-0500)] <clown> brb
[13:56:55 CDT(-0500)] <colinclark> michelled, kasparnet: I'm just reviewing The Artist Formerly Known as Nacho's list from today's Pilot call, and I noticed that it mentions a "logging tool"
[13:57:24 CDT(-0500)] <colinclark> This is something that hasn't been properly prioritized by the architecture team, but I believe is a critical blocker
[13:57:46 CDT(-0500)] <colinclark> We'll need to figure out who can do the work
[13:57:53 CDT(-0500)] <colinclark> might be a good project for yzen
[14:00:24 CDT(-0500)] <michelled> colinclark: do you know much about what is meant by 'logging tool'?
[14:00:32 CDT(-0500)] <colinclark> yes
[14:00:33 CDT(-0500)] <colinclark> somewhat
[14:00:46 CDT(-0500)] <colinclark> They want very fine-grained tracking of a user's preference set over the course of usage