fluid-work IRC Logs-2013-01-07
- Fluid IRC Log Bot
[08:50:44 CST(-0600)] <colinclark> yzen1: Are you free to chat with me and Kasper about the GPII Registry today at noon?
[08:58:18 CST(-0600)] <yzen1> colinclark: definitely
[08:58:23 CST(-0600)] <colinclark> awesome!
[09:13:58 CST(-0600)] <colinclark> Hey Justin_o, michelled, and yzen1: I was thinking about Ramen Noodles, just now...
[09:14:15 CST(-0600)] <michelled> yumm!
[09:14:24 CST(-0600)] <michelled> followed by ping pong?
[09:14:25 CST(-0600)] <colinclark> yzen1, while you were on vacation, Justin_o, michelled, avtar and I ate noodles and played ping pong
[09:14:25 CST(-0600)] <Justin_o> colinclark: 
you want to get your picture taken again
[09:14:29 CST(-0600)] <colinclark> lol
[09:14:44 CST(-0600)] <colinclark> I wore my Russian Ping Pong Shorts
[09:14:56 CST(-0600)] <colinclark> Okay, I don't have ping pong shorts
[09:14:57 CST(-0600)] <michelled> unfortunately we've lost the pictures 
[09:14:59 CST(-0600)] <colinclark> but it would be cool if I did
[09:15:17 CST(-0600)] <Justin_o> http://devour.com/video/best-table-tennis-shots-of-2012/
[09:15:41 CST(-0600)] <colinclark> that's michelle in the first clip
[09:15:50 CST(-0600)] <colinclark> spiking the guy in the red shirt
[09:15:57 CST(-0600)] <colinclark> Anyway, Justin_o and michelled, we did a bit of informal planning while eating noodles
[09:16:02 CST(-0600)] <colinclark> regarding Floe
[09:16:17 CST(-0600)] <colinclark> Can you remind me of what we talked about?
[09:16:48 CST(-0600)] <michelled> we talked about UIO and video player and cloud for all
[09:17:01 CST(-0600)] <colinclark> I guess they're all interrelated, eh?
[09:17:18 CST(-0600)] <colinclark> At the moment, I see the Video Player as useful for Cloud4all as well as Floe
[09:17:34 CST(-0600)] <colinclark> and undoubtedly jessm could tell us tons about how important UIO is for both Cloud4all and Floe at the moment
[09:18:07 CST(-0600)] <michelled> we thought that there was quite a bit of architectural work to be done on UIO to get it to the point where it is configurable enough to build the new designs
[09:18:59 CST(-0600)] <colinclark> yeah, I imagine there is quite a bit of refactoring
[09:19:05 CST(-0600)] <colinclark> "antification"
[09:19:46 CST(-0600)] <michelled> yes, we only have half ants right now
[09:21:54 CST(-0600)] <jessm> ants
[09:22:53 CST(-0600)] <jessm> so, fluid-everyone: want to see an amazing table tennis shot from the paralympics, watch this: http://www.youtube.com/watch?v=riR_SyhvB6s
[09:23:18 CST(-0600)] <michelled> wow!
[09:23:28 CST(-0600)] <jessm> see?!
[09:23:29 CST(-0600)] <Justin_o> jessm: i find it hard to believe these guys are in the paralympics
[09:23:41 CST(-0600)] <jessm> Justin_o: agreed!
[09:24:07 CST(-0600)] <colinclark> jessm: Can you summarize the general trajectory you see UI Options taking for both Cloud4all and Floe over the next few months?
[09:25:25 CST(-0600)] <colinclark> And that is indeed a "ridiculous shot," jessm. Super amazing!
[09:26:28 CST(-0600)] <jessm> colinclark: I see a trajectory for UIO, VP, and authoring that stretches to first week in April
[09:27:10 CST(-0600)] <jessm> UIO needs to be antified (whatever that means) and we need to start developing the new design, the prefs we already have updated, and a few new prefs (e.g. text to speech)
[09:27:40 CST(-0600)] <colinclark> What forms will the new designs take, at this point?
[09:27:56 CST(-0600)] <jessm> colinclark: wondertwins?
[09:28:01 CST(-0600)] <colinclark> lol
[09:28:35 CST(-0600)] <colinclark> This page is the latest? http://wiki.fluidproject.org/display/fluid/User+Interface+Options+design+high+fidelity%2C+C.1
[09:28:47 CST(-0600)] <colinclark> We'll do both "full-web" and mobile interfaces?
[09:29:15 CST(-0600)] <jessm> colinclark: roger that url
[09:29:25 CST(-0600)] <jessm> colinclark: i think we focus on full-web
[09:29:32 CST(-0600)] <jessm> mobile i think can be preview-y at this point
[09:29:47 CST(-0600)] <jessm> we need to remain nimble lest browser-based rears up and needs attention
[09:29:50 CST(-0600)] <jessm> methinks
[09:30:10 CST(-0600)] <colinclark> what does that mean, practically speaking?
[09:30:11 CST(-0600)] <colinclark>
[09:30:18 CST(-0600)] <colinclark> "nimble"
[09:30:34 CST(-0600)] <jessm> we wear a suit and tie with UIO full-web and we wear flip-flops with mobile
[09:30:40 CST(-0600)] <jessm> dress code for developers
[09:31:33 CST(-0600)] <colinclark> Justin_o: Can you translate, King? ^ 
[09:32:29 CST(-0600)] <colinclark> And how would this approach relate to designing it responsively yet, I think, iteratively, michelled?
[09:32:43 CST(-0600)] <colinclark> I find myself slightly confused
[09:34:04 CST(-0600)] <Justin_o> I think that means we're focused on getting the full-web version to production.. where as the mobile one will be more of a preview of what it will be like.. so earlier on in the dev cycle i guess
[09:34:06 CST(-0600)] <Justin_o> something like that
[09:34:14 CST(-0600)] <Justin_o> jessm ^?
[09:34:20 CST(-0600)] <jessm> Justin_o: dude, you get me – love that about you
[09:34:25 CST(-0600)] <colinclark> lol
[09:34:27 CST(-0600)] <colinclark>
[09:34:43 CST(-0600)] <Justin_o> cool.. just as long as I don't have to wear a suit and tie while working on it
[09:34:56 CST(-0600)] <jessm> these are just figurative outfits
[09:34:57 CST(-0600)] <colinclark> you could wear your t-shirt tux, Justin_o!
[09:35:10 CST(-0600)] <jessm> stop! Justin_o has a t-shirt tux?
[09:35:11 CST(-0600)] <Justin_o> colinclark: 
[09:35:22 CST(-0600)] <Justin_o> jessm: i'll have to send you a picture
[09:35:28 CST(-0600)] <jessm> !
[09:35:55 CST(-0600)] <Justin_o> jessm: sadly I don't have it right now.. i'll have to dig it up at home tonight
[09:36:10 CST(-0600)] <colinclark> okay, so then the question I have just revolves around responsiveness
[09:36:23 CST(-0600)] <colinclark> I figure michelled probably has the most experience with that
[09:37:22 CST(-0600)] <michelled> colinclark: a lot of what we are now doing when we develop components gets the fairly ready to be responsive
[09:37:36 CST(-0600)] <michelled> you know, stuff like using ems and percentages when laying things out
[09:37:38 CST(-0600)] <colinclark> yeah
[09:38:12 CST(-0600)] <michelled> colinclark: but it makes sense to me to make sure we have something that works in flip flops on both mobile and desktop early
[09:38:17 CST(-0600)] <colinclark> So are there some coding techniques/review heuristics we can use to ensure that we're not putting huge barriers in against mobile responsiveness, even if we don't get it perfect from the start?
[09:38:46 CST(-0600)] <colinclark> jessm: It's an interesting issue...
[09:38:54 CST(-0600)] <colinclark> HiFi on one platform first...
[09:39:03 CST(-0600)] <colinclark> or medium-fi across them both
[09:39:39 CST(-0600)] <colinclark> or some blend of the two
[09:39:45 CST(-0600)] <michelled> the secret is that one of the prioritized features gets us almost all the way to mobile
[09:39:57 CST(-0600)] <colinclark> michelled: elaborate?
[09:40:04 CST(-0600)] <michelled> "simplify" === mobile version
[09:40:14 CST(-0600)] <michelled> let me elaborate a little more
[09:40:18 CST(-0600)] <colinclark> lol
[09:40:21 CST(-0600)] <colinclark> +1
[09:40:25 CST(-0600)] <jessm> ah, good point michelled !
[09:40:40 CST(-0600)] <michelled> so, the presets listed on this page: http://wiki.fluidproject.org/display/fluid/User+Interface+Options+design+specifications,+C.1
[09:40:55 CST(-0600)] <michelled> give us our starting point for what we want to implement first
[09:41:16 CST(-0600)] <michelled> you'll notice, colinclark, that many of them already work to some degree in our current UIO
[09:41:30 CST(-0600)] <colinclark> this is a nice spec page
[09:41:44 CST(-0600)] <michelled> the new features are 'simplify', 'text-to-speech' and 'keyboard shortcuts'
[09:41:54 CST(-0600)] <colinclark> The "simplify" requirement would "mobilize" the page itself, right? But not necessarily UIO?
[09:42:14 CST(-0600)] <colinclark> Or perhaps the point is moot, since anything UIO does to the page, it should also do to itself?
[09:42:41 CST(-0600)] <michelled> yeah, I think that's correct - although I'm a bit confused about that - there was so much back and forth on that point
[09:42:55 CST(-0600)] <michelled> stability versus change
[09:43:46 CST(-0600)] <colinclark> Yeah, in the wireframes it seems that the page changes but UIO does not
[09:44:34 CST(-0600)] <colinclark> in which case responsivizing UIO is a separate requirement--i.e. making it work on mobile, tablets, etc.
[09:46:16 CST(-0600)] <michelled> good point colinclark
[09:46:20 CST(-0600)] <colinclark> Anyway, I guess the key, either way, is to find some techniques to make sure that we're not committing to something not working up front...
[09:46:34 CST(-0600)] <colinclark> Our current UIO is awkward, since it simply does not work on tablets or mobile
[09:46:40 CST(-0600)] <colinclark> for two reasons:
[09:46:45 CST(-0600)] <colinclark> 1. Some controls aren't touch-aware
[09:47:00 CST(-0600)] <colinclark> 2. It doesn't adapt its layout to the device size
[09:47:32 CST(-0600)] <arashs> colinclark: those are really good points
[09:48:40 CST(-0600)] <jessm> i'm excited to gets these conversations kicked up again
[09:48:52 CST(-0600)] <jessm> things like the "does UIO itself change"
[09:49:09 CST(-0600)] <jessm> i think we settled on 'no' but i think we need to be clear on why we arrived somewhere anew
[09:49:39 CST(-0600)] <arashs> I am doing some thinking on that in my scenarios
[09:50:20 CST(-0600)] <colinclark> arashs: Good to hear
[09:50:21 CST(-0600)] <colinclark> thanks
[09:50:46 CST(-0600)] <colinclark> So, perhaps I'll propose a very rough approach
[09:50:53 CST(-0600)] <colinclark> and you all can tell me what you think
[09:51:05 CST(-0600)] <colinclark> I believe this is just a translation of Justin_o's translation of jessm
[09:51:31 CST(-0600)] <colinclark> 1. We focus on producing a "production-ready" UIO experience on large screens
[09:51:57 CST(-0600)] <colinclark> 2. We do the basic development work required to ensure that UIO is at least roughly responsive to small screens and to touch control
[09:52:31 CST(-0600)] <colinclark> 3. Detailed mobile design, plus any extensions of UIO (such as in-browser integration) will be covered in future design iterations
[09:52:48 CST(-0600)] <colinclark> So the core development activity involves:
[09:53:04 CST(-0600)] <colinclark> a. Make sure UIO is architecturally ready for a new look, feel, and feature set
[09:53:14 CST(-0600)] <colinclark> b. do #1 and #2 based on the C1 wireframes and spec
[09:53:21 CST(-0600)] <colinclark> Does that seem right?
[09:53:56 CST(-0600)] <jessm> yes, exactly
[09:54:10 CST(-0600)] <arashs> yes
[09:55:11 CST(-0600)] <colinclark> ok
[09:55:40 CST(-0600)] <Justin_o> in regards to point 2. http://touchpunch.furf.com
[09:55:41 CST(-0600)] <arashs> colinclark are tablets included in "large screens"?
[09:55:58 CST(-0600)] <colinclark> michelled, Justin_o: So the question now I guess is, "what do we need to do to enable #2 without having it totally distract us from #1?"
[09:56:06 CST(-0600)] <colinclark> arashs: I wasn't including tablets, no
[09:56:17 CST(-0600)] <arashs> ok
[09:56:20 CST(-0600)] <colinclark> I was including tablets in #2
[09:56:56 CST(-0600)] <michelled> colinclark: well, as we know, everything does take time and there is no magic
[09:57:03 CST(-0600)] <michelled> so we do have to some effort in
[09:57:11 CST(-0600)] <michelled> but I think a lot of the effort is what we are doing anyway
[09:57:23 CST(-0600)] <michelled> colinclark: the extra effort, is some testing
[09:57:30 CST(-0600)] <michelled> Justin_o: do you think that's correct?
[09:57:41 CST(-0600)] <michelled> we'd add some mobile testing into our iterations?
[09:58:34 CST(-0600)] <Justin_o> michelled: that sounds about right… at this stage it probably doesn't need to be very exhaustive testing either.. at least that's what i'm getting from the flip-flops
[09:58:58 CST(-0600)] <Justin_o> but enough that we can make sure that we catch the obvious things
[09:59:51 CST(-0600)] <michelled> so we'd want to
[10:00:05 CST(-0600)] <michelled> 1. be able to interact with all the controls
[10:00:11 CST(-0600)] <michelled> 2. have the settings actually do something
[10:00:22 CST(-0600)] <michelled> 3. not look horribly broken
[10:00:38 CST(-0600)] <michelled> and we'd want that on some very basic subset of devices
[10:00:48 CST(-0600)] <michelled> does that seem right Justin_o?
[10:00:57 CST(-0600)] <Justin_o> michelled: yep.. sounds good…
[10:01:04 CST(-0600)] <michelled> what devices Justin_o?
[10:01:16 CST(-0600)] <colinclark> jessm: Does this seem like an adequate approach to you, or are we spreading ourselves too thin in your mind? My goal is to try to avoid retrofit costs.
[10:01:21 CST(-0600)] <Justin_o> michelled: funny.. i was just going to ask you what we had available for testing
[10:01:27 CST(-0600)] <colinclark> Speaking of devices, jessm...
[10:01:51 CST(-0600)] <colinclark> We need to spend some CFI money on a Nexus 4, 7, and 10 so we can do reasonable Android testing
[10:02:07 CST(-0600)] <colinclark> I think, with our iPads and recent iPod touches, we've probably got iOS covered nicely
[10:02:24 CST(-0600)] <jessm> so, i was having bibimbop and i tried to pull UIO up on my iPhone to show my lunch buddy
[10:02:46 CST(-0600)] <colinclark> I know how this story ends
[10:02:46 CST(-0600)] <jessm> it was horribly broken and sad – yes, that is the moment that it needs to be good-'nough
[10:02:55 CST(-0600)] <jessm> the bibimbop was great
[10:03:14 CST(-0600)] <jessm> i agree, let's avoid retrofitting costs
[10:03:32 CST(-0600)] <colinclark> So does michelled's 3-point criteria suit your bibimbap needs?
[10:03:34 CST(-0600)] <jessm> and re: spreading too thin… that's where the magic of kingliness (yes michelled there is magic!) comes in
[10:03:49 CST(-0600)] <jessm> colinclark: yes, the bibimbop 3 are perfect
[10:04:21 CST(-0600)] <colinclark> Okay, I'm satisfied with this general approach, then.
[10:04:38 CST(-0600)] <colinclark> Let's get us some Android devices and some Windows 8 licenses, and we'll be ready to rock
[10:04:47 CST(-0600)] <colinclark> There is another issue we could bring up, but perhaps it's a can of worms...
[10:04:49 CST(-0600)] <jessm> +1
[10:05:05 CST(-0600)] <arashs> I did some research on the differences in the browsers of phones vs tablets, and there are some major differences
[10:05:37 CST(-0600)] <colinclark> arashs: Yes, that's right. What differences do you think are most interesting?
[10:05:49 CST(-0600)] <colinclark> So yzen1, this is where you come in...
[10:06:17 CST(-0600)] <colinclark> As jessm has described it to me, UIO is increasingly the hottest thing we've got
[10:06:18 CST(-0600)] <arashs> browsers in tablets already have some accessibility options
[10:06:37 CST(-0600)] <colinclark> arashs: What sorts of options are you thinking of, in particular?
[10:06:50 CST(-0600)] <arashs> specially in android
[10:07:53 CST(-0600)] <arashs> text scaling
[10:08:04 CST(-0600)] <arashs> force enable zoom
[10:08:30 CST(-0600)] <colinclark> yzen1, Justin_o, michelled: So with UIO so hot, we find ourselves in a bind with the Video Player
[10:08:37 CST(-0600)] <colinclark> we're making progress, it's getting closer, but we're running out of itme
[10:08:39 CST(-0600)] <colinclark> time
[10:09:02 CST(-0600)] <colinclark> So, Justin_o and michelled, our idea was to split our effort pretty evenly in two areas:
[10:09:13 CST(-0600)] <colinclark> 1. Preparing UIO architecturally for its new incarnation
[10:09:20 CST(-0600)] <colinclark> 2. Getting the Video Player to the point where people can really use it
[10:09:34 CST(-0600)] <colinclark> Is that roughly what we discussed while eating noodles/
[10:09:47 CST(-0600)] <jessm> we as a community eat a lot of noodles
[10:09:52 CST(-0600)] <michelled> yep, that's what we decided
[10:10:37 CST(-0600)] <colinclark> so then the resource split
[10:10:42 CST(-0600)] <colinclark> the part where we name names
[10:11:37 CST(-0600)] <colinclark> yzen1: We were hoping, in addition to continuing to work with evgeni and co. on Cloud4all, that you'd be interested in "smashing UIO"
[10:12:32 CST(-0600)] <colinclark> i.e. antifying it to the best of our current abilities
[10:12:46 CST(-0600)] <colinclark> and starting the effort to implement its amazing new user interface
[10:13:10 CST(-0600)] <yzen> colinclark: sounds good, how much of a fresh start is it ?
[10:13:26 CST(-0600)] <colinclark> yzen: Visually and feature-wise, it's pretty fresh
[10:13:33 CST(-0600)] <colinclark> http://wiki.fluidproject.org/display/fluid/User+Interface+Options+design+high+fidelity%2C+C.1
[10:13:41 CST(-0600)] <colinclark> Architecturally, I think our goals are fairly clear...
[10:13:43 CST(-0600)] <yzen> colinclark: ya i saw those
[10:13:53 CST(-0600)] <colinclark> we want to make it easier for others to adapt and extend it
[10:14:28 CST(-0600)] <colinclark> which is something you're already thinking about while working with evgeni on his PCP
[10:14:40 CST(-0600)] <yzen> colinclark: where there any more conversation about the bus approach or is it in context of clould4all?
[10:14:49 CST(-0600)] <colinclark> bus approach?
[10:17:09 CST(-0600)] <colinclark> yzen: ^
[10:17:16 CST(-0600)] <yzen> i remember before the break, Justin_o and you? where talking about the overall picture of how uioptions are set/announced
[10:18:18 CST(-0600)] <jessm> so, i have a comment i wrote a few minutes ago
[10:18:25 CST(-0600)] <colinclark> yzen: oh yes
[10:18:27 CST(-0600)] <yzen> the idea analogous to dbus
[10:18:29 CST(-0600)] <jessm> there doesn't seem to be the right moment to plunk it in
[10:18:40 CST(-0600)] <colinclark> no further talk about that, but it's something we should consider, yes, yzen
[10:18:45 CST(-0600)] <jessm> so i'm just going to since this convo has gone a bit like a planning session
[10:18:47 CST(-0600)] <jessm> not to confuse 3 things with the bibimbop 3, but here are our 3 to show first week of April: developed and working UIO in new designs and with new prefs, Vid player, and a start at a basic authoring environ with access4all metadata tagging
[10:19:16 CST(-0600)] <colinclark> I'm willing to give you more or less carte blanche to take the lead on re-envisioning it
[10:19:31 CST(-0600)] <colinclark> along with help from me and Bosmon and Justin_o, of course
[10:19:50 CST(-0600)] <colinclark> jessm: cool
[10:20:00 CST(-0600)] <colinclark> So
[10:20:24 CST(-0600)] <colinclark> THE BY APRIL, NOT RAMEN NOR BIBIMBAP LIST:
[10:20:45 CST(-0600)] <colinclark> i. Design & implement new version of UI Options
[10:20:53 CST(-0600)] <colinclark> ii. Working, "finished" Video Player
[10:21:42 CST(-0600)] <colinclark> iii. Super-simple authoring tool skeleton (used as an environment to experiment with and integrate early our accessibility metadata components)
[10:22:43 CST(-0600)] <colinclark> right, jessm? ^^
[10:22:59 CST(-0600)] * colinclark the list nerd.
[10:23:33 CST(-0600)] <jessm> yes exactly! shall we call it the udon or you done list?
[10:25:10 CST(-0600)] <colinclark> i'll leave the clever names to you
[10:25:54 CST(-0600)] <colinclark> So yzen and Justin_o, I guess the first step on the UIO side of things is to come up with a clear technical plan
[10:26:04 CST(-0600)] <colinclark> with the things we'd like to add/remove/refactor
[10:26:25 CST(-0600)] <colinclark> michelled: I'm sure we've probably already got some of that planning in place from previous discussions, right?
[10:27:12 CST(-0600)] <michelled> colinclark: it's likely very out of date. I think it would make sense to make the list again
[10:27:16 CST(-0600)] <colinclark> ok
[10:27:22 CST(-0600)] <michelled> colinclark: and it probably makes a lot of sense to have Bosmon involved
[10:27:41 CST(-0600)] <colinclark> should we plan an architectural meeting to craft a plan?
[10:27:47 CST(-0600)] <michelled> yes
[10:27:56 CST(-0600)] <colinclark> Justin_o: Do we have something scheduled for this week's community meeting already?
[10:28:23 CST(-0600)] <michelled> there's work that has been done in the video player repo that should be considered as well
[10:28:23 CST(-0600)] <Justin_o> colinclark: http://wiki.fluidproject.org/display/fluid/Community+workshops
[10:28:27 CST(-0600)] <michelled> relating to the media panel
[10:28:29 CST(-0600)] <Justin_o> they can all be changed though
[10:28:42 CST(-0600)] <colinclark> It's up to you...
[10:28:52 CST(-0600)] <colinclark> We should meet soon, it sounds like
[10:29:10 CST(-0600)] <colinclark> I think we could probably start without Bosmon if we wanted; I believe he's back in action on Wednesday
[10:29:31 CST(-0600)] <colinclark> yzen: Can I leave it up to you to schedule, whenever you prefer, that technical roadmapping meeting?
[10:29:40 CST(-0600)] <Justin_o> colinclark: so he'll be available at the community meeting if we schedule the uio talk for then?
[10:29:49 CST(-0600)] <colinclark> And are you cool to take the lead on this work, now that you're CSpace-free, yzen?
[10:29:53 CST(-0600)] <colinclark> Justin_o: I believe so, yes
[10:30:22 CST(-0600)] <yzen> colinclark: sure, i would like to have it asap i guess, if that's ok with everyone
[10:31:05 CST(-0600)] <Justin_o> yzen: if want.. i can slot it into the community meeting spot for this week then
[10:32:53 CST(-0600)] <colinclark> So Justin_o, if I remember from ramen, you were going to split your time in half between Video Player and UI Options with yzen, is that right?
[10:33:19 CST(-0600)] <colinclark> And michelled, you were going to hold off on diving into the obscurities of GPII Windows programming to help see the Video Player through, right?
[10:35:07 CST(-0600)] <colinclark> Ah, I assume everyone has drifted to standup
[10:35:18 CST(-0600)] <colinclark> I'm in another call, so I will have to miss it in person
[10:35:56 CST(-0600)] <colinclark> My update is, well, that I'm doing planning here in the channel, as well as continuing my work on the Prosperity4all proposal
[10:36:00 CST(-0600)] <colinclark> AT THE SAME TIME!
[10:36:06 CST(-0600)] <colinclark> I expect the day will roughly go like this
[10:36:33 CST(-0600)] <colinclark> kasper and yzen and I will be meeting today to talk about user preferences, conditionals, and the Common Terms Registry.
[10:45:49 CST(-0600)] <colinclark> hey kasper!
[10:45:58 CST(-0600)] <colinclark> yzen and kasper: You'll be unsurprised by this...
[10:46:01 CST(-0600)] <kasper> hey colinclark
[10:46:02 CST(-0600)] <colinclark> but I double booked myself
[10:46:03 CST(-0600)] <Justin_o> colinclark: regarding my time split.. i think that's right.. although i'm a bit foggy on things that happened last year
[10:46:18 CST(-0600)] <colinclark> Would 2:30 pm EST work for you? That's 8:30 pm your time, kasper
[10:46:26 CST(-0600)] <colinclark> Justin_o: you and me both
[10:47:06 CST(-0600)] <kasper> colinclark: yup that's fine by me
[10:47:13 CST(-0600)] <colinclark> phew, awesome
[10:47:17 CST(-0600)] <colinclark> sorry for the inconvenience
[10:47:36 CST(-0600)] <colinclark> Okay, so planning as I see it so far:
[10:47:56 CST(-0600)] <colinclark> 1. We have a half King and a whole Fish working on Video Player for roughly the month of January
[10:48:15 CST(-0600)] <colinclark> 2. We have the other half King and an Island working UI Options
[10:48:45 CST(-0600)] <colinclark> 3. I'm thinking that it might make sense to get someone familiar with UIO working with Evgeni and Yura on UI Options integration into the PCP
[10:49:01 CST(-0600)] <colinclark> I was thinking you might be really good at this, anastasiac
[10:49:21 CST(-0600)] <colinclark> yzen is Evegni's mentor, so he'd be your contact on that
[10:49:33 CST(-0600)] <colinclark> and cindyli, it sounds like you're back on the Floe scene now as well
[10:49:41 CST(-0600)] <cindyli> yes, colinclark
[10:50:00 CST(-0600)] <colinclark> I'll leave it to Justin_o, but I'm thinking you know UIO pretty well, and could work with him and yzen on that work.
[10:50:12 CST(-0600)] <cindyli> sounds good
[10:50:30 CST(-0600)] <colinclark> cool
[10:52:49 CST(-0600)] <anastasiac> colinclark, sounds good
[10:53:31 CST(-0600)] <colinclark> anastasiac, yzen: My sense, and it might be a bit out of date, was that Evgeni wasn't quite sure how he'd dive into the process of actually using UIO to power the Cloud4all Personal Control Panel
[10:53:57 CST(-0600)] <colinclark> As a rough summary, this Panel will display preferences largely for desktop and platform access features
[10:54:09 CST(-0600)] <colinclark> which overlaps partially with the kinds of settings we should in UIO currently, but will also involve others
[10:55:58 CST(-0600)] <anastasiac> colinclark, could you elaborate on what you mean by "using UIO to power the PCP"? Do you mean implement the PCP using UIO code?
[10:56:08 CST(-0600)] <colinclark> yes
[10:56:21 CST(-0600)] <colinclark> exactly
[10:56:28 CST(-0600)] <anastasiac> would this be something that is dependent on the full antification?
[10:57:04 CST(-0600)] <colinclark> I'll defer to yzen to fill in all the details
[10:57:14 CST(-0600)] <colinclark> but my sense is that it will benefit from antification, but can't wait for it entirely
[10:58:08 CST(-0600)] <jessm> Justin_o michelled: for to summarize… the convo was a sort of planning, roadmapping, resource allocating one – are all the details clear? should we start picking them out and putting them into the wiki somewhere?
[10:58:28 CST(-0600)] <yzen> colinclark, anastasiac it is possible to use uio as is in pcp, but there's a missing component that would integrate the pcp and the rest of the gpii architecture
[10:59:06 CST(-0600)] <jessm> yzen: what's the missing component?
[10:59:08 CST(-0600)] <Justin_o> jessm: i think it would make sense in the wiki somewhere…
[10:59:48 CST(-0600)] <yzen> well the way of communicating preferences to the flow manager in particular
[10:59:49 CST(-0600)] <anastasiac> yzen, sounds like you and I should meet, and you can bring me up to speed on the PCP, etc.
[10:59:52 CST(-0600)] <yzen> jessm: ^
[12:39:13 CST(-0600)] <jessm> yzen: not sure what i'm supposed to look at?
[12:41:34 CST(-0600)] <yzen> jessm: you asked about the missing component , that's where i mentioned the communication of preferences to flow manager as an example
[12:41:50 CST(-0600)] <yzen> perhaps it is a component missing in cloud4all
[12:41:50 CST(-0600)] <jessm> ah
[13:32:22 CST(-0600)] <jessm> Justin_o: re: the wiki – is this something I should try to put together or are you already on it?
[13:45:11 CST(-0600)] <Justin_o> jessm: don't know what's up
[13:46:02 CST(-0600)] <jessm> Justin_o: meaning what's already in the wiki?
[13:53:46 CST(-0600)] <Justin_o> jessm: sorry.. was totally confused about what you meant
[13:54:07 CST(-0600)] <Justin_o> jessm: i think i get it now.. you want the conversation up in the wiki
[13:54:08 CST(-0600)] <jessm> ah, now i understand
[13:54:28 CST(-0600)] <jessm> so, not the conversation, but the details pulled out into a sort of roadmap?
[13:54:32 CST(-0600)] <jessm> or maybe we don't need that
[13:54:43 CST(-0600)] <jessm> we just needs folks to be clear and then we can work out some iteration plans?
[13:54:48 CST(-0600)] <jessm> what do you think Justin_o ?
[13:55:23 CST(-0600)] <Justin_o> jessm: makes sense..
[13:55:47 CST(-0600)] <Justin_o> i can put it up somewhere.. maybe in point form or something.. i'll get your lists up
[13:56:08 CST(-0600)] <jessm> or i can do it – i'm happy to as well...
[13:57:11 CST(-0600)] <Justin_o> jessm: i can probably take a few minutes to get something up.. and you can modify if you like
[13:57:18 CST(-0600)] <Justin_o> by the way, is this all still valid http://wiki.fluidproject.org/display/fluid/Fluid+2013+Roadmap
[13:57:30 CST(-0600)] <Justin_o> i'll probably just add a child page to that
[13:57:52 CST(-0600)] <jessm> Justin_o: yes, that is the year list from which we can pick and choose
[13:58:05 CST(-0600)] <jessm> and that is both dev and design
[13:58:06 CST(-0600)] <Justin_o> jessm: cool.. thanks
[14:29:42 CST(-0600)] <Justin_o> jessm: here's the first pass at moving the channel conversation to a roadmap http://wiki.fluidproject.org/display/fluid/FLOE+2013+Q1+Roadmap
[14:30:04 CST(-0600)] <Justin_o> it's basically the high level stuff for now
[14:33:52 CST(-0600)] <jessm> Justin_o: looks great
[14:33:59 CST(-0600)] <Justin_o> thanks
[14:34:00 CST(-0600)] <jessm> a nice condensing of all that noodle nonsense
[14:34:56 CST(-0600)] <Justin_o>
[14:34:58 CST(-0600)] <Justin_o> but not as fun