fluid-work IRC Logs-2013-01-21

[10:43:10 CST(-0600)] <jessm> i have the embarrassing situation of having sent a message to a list i manage from an email that isn't subscribed. but now i can't remember my list mgr. passwd. does anyone know what i can do short of begging avatar to tell me what my password is?

[10:45:29 CST(-0600)] <Justin_o> jessm: sorry.. i don't know.. maybe colinclark or michelled might have access

[10:45:51 CST(-0600)] <Justin_o> heidiv: here's the video player stuff we were working on http://wiki.fluidproject.org/display/fluid/FLOE+Video+Player+Development+Planning

[10:46:03 CST(-0600)] <jessm> well, there's avtar. I'll just have to be honest about losing a password

[10:46:20 CST(-0600)] <heidiv> thanks Justin_o

[10:46:22 CST(-0600)] <avtar> which password?

[10:46:41 CST(-0600)] <Justin_o> most of it seems to have been done… but i think there is still some work on the big play button and the IDI integration.. i think you may need to check in with anastasiac and michelled on those though

[10:47:06 CST(-0600)] <Justin_o> heidiv: ^

[10:47:18 CST(-0600)] <heidiv> Justin_o it seems those liras are waiting for FLUID-4853 to be merged

[10:47:20 CST(-0600)] <Justin_o> heidiv: Actually FLUID-4889 might be a good one to pick up

[10:47:24 CST(-0600)] <jessm> avtar: to the global preferences mailing list that i'm the mgr. of

[10:47:49 CST(-0600)] <heidiv> Justin_o i can check out 4889 !

[10:48:12 CST(-0600)] <Justin_o> heidiv: thanks.. out of curiosity do you have more than 1 computer monitor?

[10:48:31 CST(-0600)] <heidiv> Justin_o i have this laptop and an iMac and an iphone

[10:48:40 CST(-0600)] <heidiv> but not dual monitors

[10:49:24 CST(-0600)] <Justin_o> heidiv: okay.. i think that should be okay.. we were noticing that the results are a bit different on the thunderbolt monitors at work vs. the laptop monitors.. i think it's because the aspect ratios are different..

[10:49:43 CST(-0600)] <heidiv> ah interesting. specifically for 4889 or generally

[10:49:51 CST(-0600)] <Justin_o> underneath i think it's the same issue, but on the wider monitors the transcripts may not disappear, they will just move over more

[10:49:59 CST(-0600)] <Justin_o> specifically for that one

[10:49:59 CST(-0600)] <heidiv> ok

[11:00:03 CST(-0600)] <jhung> heidiv: let me know if you need some help testing / diagnosing. I'll be working from home tomorrow and will be able to help you with testing on Firefox.

[11:00:51 CST(-0600)] <avtar> jessm: you should be receiving an email from the lists server soon

[11:00:56 CST(-0600)] <heidiv> jhung thanks jon!

[11:01:41 CST(-0600)] <jessm> avtar: thanks and sorry for being a monday-morning loser

[11:01:51 CST(-0600)] <avtar> np

[11:19:48 CST(-0600)] <michelled> jhung: I'm wondering if this really is a blocker. http://issues.fluidproject.org/browse/FLUID-4843

[11:20:48 CST(-0600)] <michelled> seems to me it's about support in Safari - I guess we could write some code to follow the WebVTT spec for styling and then when Safari introduces support for it, it will just work

[11:20:54 CST(-0600)] <michelled> what do you think?

[11:21:40 CST(-0600)] <jhung> michelled: The classifications of bugs in Jira are a bit off because of the lack of versioning for Video Player.

[11:21:57 CST(-0600)] <jhung> *rather release versions in jira.

[11:22:11 CST(-0600)] <jhung> So this may indeed not be a blocker currently.

[11:22:31 CST(-0600)] <michelled> ah, ok jhung thx

[11:54:22 CST(-0600)] <Justin_o> michelled, jhung, anastasiac, cindyli, heidiv: have you seen this before http://www.w3.org/2010/05/video/mediaevents.html

[11:54:36 CST(-0600)] <Justin_o> wonder if it might be helpful for checking cross browser issues and etc.

[11:55:38 CST(-0600)] <anastasiac> Yes, Justin_o, I've seen that - it is very helpful for some things. Of course, it doesn't help with any of the polyfils

[11:55:50 CST(-0600)] <Justin_o> anastasiac: good point

[11:56:38 CST(-0600)] <Justin_o> i wonder if making something like this would help for testing purposes

[11:57:50 CST(-0600)] <heidiv> neat

[11:59:43 CST(-0600)] <jhung> anastasiac: I can't reproduce this Jira anymore. Can I close it? http://issues.fluidproject.org/browse/FLUID-4815

[12:01:17 CST(-0600)] <anastasiac> ah, right, jhung, I think that was filed before the videos themselves were also enlarged

[12:01:19 CST(-0600)] <anastasiac> I'll close it

[12:01:42 CST(-0600)] <anastasiac> ah, you beat me to it

[12:01:51 CST(-0600)] <jhung> I did? I don't think I closed.

[12:24:36 CST(-0600)] <jessm> colinclark: you around?

[12:25:26 CST(-0600)] <Justin_o> jhung, anastasiac, michelled, heidiv, cindyli: i'm about to head offline in 5 minutes. anything you might need from me before i go...

[12:25:57 CST(-0600)] <anastasiac> Justin_o, I'm good. michelled is at lunch

[12:27:00 CST(-0600)] <Justin_o> anastasiac: okay.. thanks

[12:29:14 CST(-0600)] <jhung> nope I'm good Justin_o

[12:29:32 CST(-0600)] <Justin_o> jhung: okay.. thanks

[12:29:37 CST(-0600)] <Justin_o> well see you guys tomorrow then

[12:29:44 CST(-0600)] <heidiv> be well Justin_o

[12:29:50 CST(-0600)] <Justin_o> thanks

[13:00:11 CST(-0600)] <colinclark> jessm: I'm around now, yes

[14:09:26 CST(-0600)] <jhung> anastasiac: do you know if this Jira can be closed? http://issues.fluidproject.org/browse/FLUID-4664

[14:10:48 CST(-0600)] <anastasiac> jhung, the status hasn't change: I can still reproduce it in Chrome and Safari

[14:11:45 CST(-0600)] <jhung> ok thanks.

[16:57:10 CST(-0600)] <colinclark> michelled: So are you setting up your Mac for GPII development?

[16:57:27 CST(-0600)] <michelled> colinclark: yep, I'm trying to

[16:57:36 CST(-0600)] <michelled> I was wondering if the instructions are up to date http://wiki.gpii.net/index.php/Setting_Up_Your_Development_Environment#Mac_Installation_Instructions

[16:57:38 CST(-0600)] <michelled> do you know?

[16:57:49 CST(-0600)] <colinclark> I think it's likely that yzen is the only one who actually develops natively on his Mac

[16:57:56 CST(-0600)] <colinclark> which occasionally worries me

[16:58:11 CST(-0600)] <michelled> oh - is it not a good idea colinclark?

[16:58:20 CST(-0600)] <colinclark> Well, I think it's a fine idea

[16:58:30 CST(-0600)] <michelled> I guess because we don't actually have ATs that will launch on the Mac?

[16:58:41 CST(-0600)] <colinclark> We don't have settingsHandlers for the Mac

[16:59:07 CST(-0600)] <colinclark> Hey kasper, how's your back?

[16:59:26 CST(-0600)] <colinclark> I guess the biggest weakness of developing directly on your Mac is that you're a bit abstracted from the system as it actually works

[16:59:27 CST(-0600)] <kasper> still really messed up

[16:59:31 CST(-0600)] <colinclark> ouch

[16:59:40 CST(-0600)] <kasper> just came back from the hospital

[16:59:45 CST(-0600)] <colinclark> Oh no!

[16:59:52 CST(-0600)] <kasper> I suddenly noticed my back was all crooked

[16:59:52 CST(-0600)] <michelled> that's terrible kasper

[16:59:58 CST(-0600)] <kasper> so went to get it checked out

[17:00:08 CST(-0600)] <kasper> yeah – on the upside the gave me a ton of drugs

[17:00:09 CST(-0600)] <colinclark> michelled: My process tends to involve shared folders between VMWare and the Mac. So I code in TextMate and run the system on Linux and Windows

[17:00:13 CST(-0600)] <colinclark> sometimes both simultaneously

[17:00:15 CST(-0600)] <colinclark> kasper:

[17:00:41 CST(-0600)] <colinclark> But if your development is mostly infrastructural, I don't see why you can't do the bulk of your development locally

[17:00:43 CST(-0600)] <kasper> anyway - popping on an episode of whatever, eating dinner and then sleep - hopefully it's better tomorrow

[17:00:52 CST(-0600)] <colinclark> yeah, I hope so too

[17:01:00 CST(-0600)] <colinclark> kasper: While you're here, can I ask you one quick question?

[17:01:17 CST(-0600)] <kasper> sure

[17:01:27 CST(-0600)] <colinclark> GPII-1: Why doesn't it work?

[17:01:54 CST(-0600)] <colinclark> I guess I'm wondering what we'll do with QA reports… presumably we have to calibrate them against some set of expectations about what the system is supposed to do

[17:02:05 CST(-0600)] <colinclark> So far, my test results aren't looking 100% awesome on Windows XP

[17:02:15 CST(-0600)] <colinclark> I get the screen magnifier, but no settings seem to get set for it

[17:02:26 CST(-0600)] <colinclark> None of sammy's font or colour preferences are acted upon

[17:02:35 CST(-0600)] <colinclark> All off these may be "known issues" and the like

[17:02:46 CST(-0600)] <colinclark> But I guess I wonder how we know if it works "well enough"

[17:03:02 CST(-0600)] <kasper> yeah

[17:03:05 CST(-0600)] <colinclark> michelled: So there's something that bugs me slightly about these instructions

[17:03:14 CST(-0600)] <colinclark> kasper: Maybe it's a question for when your back feels better?

[17:03:26 CST(-0600)] <colinclark> michelled: They contain code.

[17:04:09 CST(-0600)] <kasper> colinclark: hehe, well, I guess at least it's not a simple question.. I guess we could make the distinction between whether it's 'framework' errors or it's solution errors

[17:04:16 CST(-0600)] <michelled> colinclark: yeah, needing to create a directory structure seemed odd to me too

[17:04:22 CST(-0600)] <kasper> so for example, if the magnifier issue is due to the registry handler being broke

[17:04:25 CST(-0600)] <kasper> that's a proper issue

[17:04:52 CST(-0600)] <kasper> if it's "just" that the solutions registry entry for the magnifier it's wrong, that's a different type of bug

[17:05:05 CST(-0600)] <colinclark> michelled: Interestingly, I'm not sure who contributed the instructions

[17:05:10 CST(-0600)] <colinclark> Someone named "Roeser"

[17:05:18 CST(-0600)] <colinclark> Do you know, by chance, who that is, kasper?

[17:05:29 CST(-0600)] <kasper> colinclark: I mean - obviously we want windows/linux to work relatively well out of the box - but as a general guideline

[17:05:33 CST(-0600)] <colinclark> kasper: How come the RegistryHandler is broken?

[17:05:39 CST(-0600)] <colinclark> And do we want it to be broken?

[17:05:42 CST(-0600)] <kasper> colinclark: it's not

[17:05:49 CST(-0600)] <kasper> it was just an example

[17:05:55 CST(-0600)] <colinclark> lol

[17:05:56 CST(-0600)] <colinclark> oops

[17:06:07 CST(-0600)] <colinclark>

[17:06:22 CST(-0600)] <kasper> ... so IF the registry handler was broken, that would be a serious issue, something like a blocker, as it's part of the framework

[17:06:29 CST(-0600)] <colinclark> ok

[17:06:39 CST(-0600)] <kasper> .. whereas if it's a matter of windows solution registry entry for the magnifier being faulty

[17:06:45 CST(-0600)] <kasper> that's a different category

[17:06:55 CST(-0600)] <colinclark> At a functional level, we more or less expect the Windows XP Magnifier to be able to have its settings set, right?

[17:07:08 CST(-0600)] <colinclark> And we more or less expect a browser to open up with UI Options in it?

[17:07:14 CST(-0600)] <kasper> yes we do

[17:07:47 CST(-0600)] <colinclark> michelled: Honestly, if this were me, I'd be at least taking the boilerplate out of this tutorial, and placing it into our currently-empty Mac repository

[17:08:07 CST(-0600)] <kasper> colinclark: so yeah, I agree with you that we want a certain set of ATs/built in stuff to work out of the box

[17:08:08 CST(-0600)] <colinclark> I love it when people update tutorials

[17:08:23 CST(-0600)] <kasper> colinclark: btw, dont know who that person was

[17:08:24 CST(-0600)] <colinclark> I like it even more when they make pull requests

[17:08:41 CST(-0600)] <colinclark> But it's easy enough to take this and put it into the repo, michelled

[17:08:45 CST(-0600)] <colinclark> your first pull request, perhaps?

[17:08:48 CST(-0600)] <colinclark> kasper: Okay, great

[17:09:08 CST(-0600)] <colinclark> So perhaps once I'm finished QA, we can go through all the reports, do some triage, and decide which ones we'll fix now

[17:09:17 CST(-0600)] <kasper> yeah, that sounds like a plan

[17:09:32 CST(-0600)] <colinclark> I'm trying to write down what a tester should expect to see, for a given persona

[17:09:40 CST(-0600)] <kasper> cool

[17:09:44 CST(-0600)] <colinclark> kasper: It's still ugly: http://wiki.gpii.net/index.php/Release_0.1_-_QA_planning#Testing

[17:10:18 CST(-0600)] <kasper> colinclark: I did it for linux: http://wiki.gpii.net/index.php/QA_Testing_-_NP_Sets

[17:10:55 CST(-0600)] <kasper> ... but that's somewhat easier, since one can basically just fire off a set of commands and check the output against a list of 'expected'

[17:10:56 CST(-0600)] <colinclark> It looks like someone did it for Windows 7, too

[17:11:04 CST(-0600)] <kasper> I think I sort of started it

[17:11:11 CST(-0600)] <kasper> but something went wrong on saving

[17:11:19 CST(-0600)] <kasper> so nothing really got proper saved

[17:11:37 CST(-0600)] <colinclark> Actually, I'm so confused

[17:11:39 CST(-0600)] <colinclark> yeah, I guess that's it

[17:11:55 CST(-0600)] <colinclark> it looks like in some cases that the gsettings info all fell down into the Windows section

[17:12:06 CST(-0600)] <colinclark> I can't figure out how anyone actually did QA

[17:12:12 CST(-0600)] <colinclark> michelled: You've never really used this system

[17:12:19 CST(-0600)] <colinclark> how did you figure out how to do QA?

[17:12:27 CST(-0600)] <colinclark> I've tested it a million times, and I'm completely confused

[17:12:29 CST(-0600)] <colinclark>

[17:13:05 CST(-0600)] <colinclark> okay, kasper, I'll try to add to this page as I go

[17:13:15 CST(-0600)] <colinclark> sorry to bug you while you're in pain

[17:13:29 CST(-0600)] <michelled> colinclark: I got yzen to show me what to do and then tried to write up enough details to the list that it would catch someone's attention if I had done QA wrong

[17:14:35 CST(-0600)] <kasper> colinclark: np - and thanks for doing the wiki notes ... it's gonna be hugely helpfull for next QA