...
[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
[14:02:41 CDT(-0500)] <clown> jhernandez, another topic, while I think about it.
[14:04:46 CDT(-0500)] <clown> I will be at a conference beginning Wed, and am not back in the office until next Tue
[14:04:46 CDT(-0500)] <clown> So, not much time for GPII work this week
[14:17:46 CDT(-0500)] <clown> jhernandez: I was disconnected for about 15 min. If you said anything, I missed it.
[15:05:21 CDT(-0500)] <jhernandez> clown: sorry, I was finishing with the mail
[15:05:29 CDT(-0500)] <jhernandez> re your conference, no prob
[15:05:40 CDT(-0500)] <clown> just got your email, jhernandez.
[15:06:38 CDT(-0500)] <jhernandez> yeah, it's basically a "what we've discussed, what we've agreed, where we are and what's next" mail
[15:09:16 CDT(-0500)] <clown> While I'm away, you and the others can decide what's next.
[15:09:40 CDT(-0500)] <jhernandez> I think that some people will want to say something about it
[15:10:11 CDT(-0500)] <jhernandez> clown: yup
[15:10:12 CDT(-0500)] <jhernandez>