fluid-work IRC Logs-2011-01-13
[09:28:11 CST(-0600)] <heidi> mlam is uploader using flash in your safari ?
[09:30:08 CST(-0600)] <mlam> heidi: i have to get my virtual box running with windows first . i'll let you know when it's going
[09:30:43 CST(-0600)] <heidi> mlam on mac?
[09:33:45 CST(-0600)] <heidi> mlam justin_o's safari 5 and 4 not using flash so not sure why mine is. i'll try upgrading to 5
[09:33:52 CST(-0600)] <mlam> no, on windows
[09:33:54 CST(-0600)] <mlam> oh ok
[09:37:34 CST(-0600)] <jessm> did our IDRC jabber server go down for everyone or just me?
[09:39:08 CST(-0600)] <heidi> mlam i think there might be weirdness - i updated my OS but not safari so possibly bizzaro stuff happening. going to update/restart
[09:39:40 CST(-0600)] <mlam> jessm: mine is down as well
[09:40:15 CST(-0600)] <jessm> jamon: ^ do you know why we might not be seeing the IDRC chat server?
[09:40:45 CST(-0600)] <jamon> jessm: just working on that, ran out of disk space
[09:41:11 CST(-0600)] <jessm> jamon: did you know that was going to happen? is that server being monitored?
[09:41:45 CST(-0600)] <jamon> i was unpacking a tarball
[09:42:52 CST(-0600)] <jessm> jamon: and then tarball pushed it over the edge?
[09:43:06 CST(-0600)] <jamon> indeed, fluidsvn is hefty, ~3gb
[09:43:47 CST(-0600)] <jessm> jamon: it took down the whole physical server? aren't Fluidsvn and the chat server both different virtual servers?
[09:43:59 CST(-0600)] <jamon> jessm: let me resolve this first
[09:44:07 CST(-0600)] <jessm> of course
[09:46:59 CST(-0600)] <jamon> so, chat server is back: issue was this
[09:47:21 CST(-0600)] <jamon> it is a newer debian, with ruby gems that are easily installed to be able to run svn2git
[09:48:01 CST(-0600)] <jamon> running svn2git on the fluidsvn repository ended up consuming the rest of the available disk space on the server
[09:59:55 CST(-0600)] <heidi> mlam after update no longer getting flash prob
[10:00:03 CST(-0600)] <mlam> ok, good stuff!
[10:03:07 CST(-0600)] <heidi> mlam patch here: http://issues.fluidproject.org/browse/FLUID-3837 going to test it on other browers. that progress bar width issue is back tho
[10:03:22 CST(-0600)] <mlam> ok, thanks, i'll try to test it out later today
[10:09:49 CST(-0600)] <michelled> Justin_o: the Conceptual Mapping JIRA component for Infusion contains three issues that are closed and were from Engage. I'm going to delete the component.
[10:10:12 CST(-0600)] <Justin_o> michelled: thank you
[10:11:30 CST(-0600)] <michelled> Justin_o: do you think I should delete the issues for just leave them closed?
[10:11:56 CST(-0600)] <Justin_o> michelled: hmm.. maybe just leave them closed in case there were links to them
[10:12:02 CST(-0600)] <michelled> oh wait - never mind - I can move them to the Engage component
[10:12:15 CST(-0600)] <Justin_o> michelled: that's a good idea
[10:18:51 CST(-0600)] <michelled> Justin_o: there are no issues in Engage Components so I'm deleting that one too
[10:20:24 CST(-0600)] <Justin_o> michelled: thanks... it's nice to start shortening that list.. at the dev meeting we were also talking about removing some of the ux ones and I think the quick start examples one.. was that correct anastasiac
[10:21:06 CST(-0600)] <anastasiac> Justin_o, yes, we decided to remove the quick start examples. issues with demos should be filed against the demo portal and the relevant component
[10:22:25 CST(-0600)] <Justin_o> we might have to make another pass through later and identify anything that is for the demo but not yet filed against the portal as well
[10:44:24 CST(-0600)] <colinclark> There's also a "Mobile" component
[10:44:32 CST(-0600)] <colinclark> I wonder what we should do with that one
[10:45:00 CST(-0600)] <colinclark> We're definitely safe to retire the UX: U-Camps component
[10:45:24 CST(-0600)] <colinclark> I'm not fully sure what to do with the other UX components
[10:45:49 CST(-0600)] <colinclark> I know jameswy personally has an allergy to JIRA, but I don't think we want to cut off the possibility of using it to organize UX-related tasks
[10:46:16 CST(-0600)] <jameswy>
[10:46:45 CST(-0600)] <Justin_o> colinclark: that makes sense.. i think we can minimize the components though.. or maybe jhung, jameswy, and erin can reorganize it later
[10:47:15 CST(-0600)] <colinclark> When you say minimize, do you mean consolidate them into fewer components?
[10:47:36 CST(-0600)] <colinclark> or just prune out the individual JIRAs?
[10:48:22 CST(-0600)] <Justin_o> um... both i guess...
[10:48:56 CST(-0600)] <Justin_o> i'm not sure how it should be organized though... so maybe it's in as few components as possible already..
[10:52:58 CST(-0600)] <jameswy> colinclark, Justin_o: I don't mind if we consolidate some of those UX components or prune within them, but doesn't it make sense to keep them for posterity as well?
[10:53:19 CST(-0600)] <colinclark> We can always keep the issues around
[10:53:20 CST(-0600)] <colinclark> and just move them
[10:53:30 CST(-0600)] <colinclark> but perhaps the starting point is just to close all the crufty stuff
[10:53:44 CST(-0600)] <Justin_o> yes.. that is what i would have meant by pruning
[10:53:59 CST(-0600)] <jameswy> That makes sense to me.
[10:55:31 CST(-0600)] <jameswy> And, I can see Infusion design using JIRA again someday (despite my personal allergy to it)
[10:56:49 CST(-0600)] <michelled> Justin_o: I just deleted the Engage Services component
[12:34:08 CST(-0600)] <heidi> colinclark so i think progress might have to be tweaked - it calculates its width by taking the width of the container but doesn't include any padding on that container
[12:34:18 CST(-0600)] <heidi> progress component
[12:34:22 CST(-0600)] <colinclark> ah, okay
[12:34:37 CST(-0600)] <colinclark> So why do you think it needs padding now?
[12:34:57 CST(-0600)] <heidi> well if you look at that footer bar for uploader
[12:35:08 CST(-0600)] <heidi> padding is used to ... make it look nice
[12:35:19 CST(-0600)] <heidi> but the progress bar won't fill it all the way
[12:35:30 CST(-0600)] <heidi> cos it thinks the width is smaller than it is when padding is added
[12:35:59 CST(-0600)] <colinclark> Do you think that has something to do with the means by which Progress calculates its width?
[12:36:06 CST(-0600)] <heidi> yes
[12:36:19 CST(-0600)] <heidi> it doesn't include any padding on the container
[12:36:21 CST(-0600)] <heidi> just gets the width
[12:36:42 CST(-0600)] <colinclark> Looks like it's using jQuery's width() method?
[12:36:46 CST(-0600)] <colinclark> Is that right?
[12:37:17 CST(-0600)] <heidi> yep
[12:37:32 CST(-0600)] <heidi> doesn't look like .width() incl padding/borders
[12:37:56 CST(-0600)] <heidi> looks like there's now an outerwidth() function?
[12:37:58 CST(-0600)] <heidi> reading..
[12:38:21 CST(-0600)] <heidi> yep
[12:38:46 CST(-0600)] <colinclark> Sounds like a promising avenue
[12:38:58 CST(-0600)] <colinclark> don't forget to keep the unit tests running as you make any changes
[12:39:10 CST(-0600)] <colinclark> Progress has a reasonably-sized suite of unit tests now
[12:43:14 CST(-0600)] <heidi> colinclark the change that.progressBar.width() to outerWidth() fixes it for me
[12:43:18 CST(-0600)] <heidi> line 77
[12:43:45 CST(-0600)] <colinclark> heidi: Cool
[12:43:51 CST(-0600)] <colinclark> there are other places where width is calculated
[12:44:10 CST(-0600)] <colinclark> most prominently in updateWidth(), starting on line 62
[12:49:41 CST(-0600)] <michelled> Justin_o: I just deleted the Spatial Mapping component from the Infusion project in JIRA
[12:50:10 CST(-0600)] <jhung> michelled: do you know much about the Tooltip component?
[12:50:30 CST(-0600)] <michelled> jhung: ya, I did some code review on it - what's up?
[12:51:04 CST(-0600)] <Justin_o> michelled: thanks i'll mark that one on my list
[12:51:05 CST(-0600)] <jhung> michelled: Can you tell me what it is in less than 30 words?
[12:51:12 CST(-0600)] <heidi> colinclark yeah it's just the width of the container that matters - the width of the green bar is fine. and innerWidth() is the function we want (excludes borders, but includes padding). i'll make a jira and attach a path... run through unit tests and connect to the uploader markup jira.
[12:52:10 CST(-0600)] <colinclark> cool
[12:52:12 CST(-0600)] <colinclark> thanks, heidi
[12:52:19 CST(-0600)] <colinclark> how did your markup changes look in IE, btw?
[12:55:12 CST(-0600)] <heidi> colinclark pretty good - one top border missing but otherwise fine. IE 7 and 8... haven't checked 6
[12:55:36 CST(-0600)] <heidi> i couldn't load the win 7 vm into virtualbox - haven't tried the ie6 one
[12:55:47 CST(-0600)] <heidi> but there's a win7 machine next to me so ill check there
[12:58:43 CST(-0600)] <colinclark> cool, this is exciting
[13:06:49 CST(-0600)] <michelled> Justin_o: the Research component is now deleted - it was all Engage research.
[13:07:21 CST(-0600)] <Justin_o> michelled: thanks
[13:17:08 CST(-0600)] <heidi> justin_o colinclark fyi FLUID-4029 progress issue
[13:37:01 CST(-0600)] <Justin_o> heidi: thanks
[14:15:41 CST(-0600)] <colinclark> jameswy: I imagine this is still a long way off from Versions, eh? http://gitx.frim.nl/
[14:16:14 CST(-0600)] <jameswy> colinclark: Hahaha... it looks like it could use some more love.
[14:18:05 CST(-0600)] <jameswy> colinclark: I hope Cornerstone (http://www.zennaware.com/cornerstone/) or Versions comes out with git and hg support.
[14:19:10 CST(-0600)] <colinclark> jameswy: You know I am a solid command-line guy when it comes to SVN
[14:19:18 CST(-0600)] <colinclark> but Cornerstone actually looks pretty good
[14:19:19 CST(-0600)] <colinclark>
[15:13:26 CST(-0600)] <michelled> fluid-everyone: Right now we have a lot of JIRA issues with no component. Some of these have no component because there is no relevant component to give them and other just fell through the cracks. I'm thinking of creating three new JIRA components: 'Testing', 'Release' and 'Demos'
[15:13:30 CST(-0600)] <michelled> what do you think?
[15:13:52 CST(-0600)] <michelled> those three should take care of most of the no component JIRA issues
[15:14:03 CST(-0600)] <heidi> michelled whats an example of a testing jira with no component?
[15:14:27 CST(-0600)] <heidi> oh like, running through tests before a release etc?
[15:14:29 CST(-0600)] <michelled> I'll also be able to move issues that currently have a component of 'General' over to those three and get rid of it since it doesn't seem to be used much and isn't very informative.
[15:14:40 CST(-0600)] <anastasiac> michelled, yesterday we discussed JIRAs related to demos. At the time, we decided that they should be filed against the "Demo Portal" component (since that's what seems to be happening anyway)
[15:14:50 CST(-0600)] <michelled> heidi: possibly, but more likely it is anything that is related to jqUnit
[15:14:53 CST(-0600)] <michelled> or manual tests
[15:14:58 CST(-0600)] <heidi> ah
[15:15:00 CST(-0600)] <anastasiac> (and also filed against the relevant infusion component)
[15:15:39 CST(-0600)] <michelled> anastasiac: ok, so Demo Portal also means any demos we create or want to create?
[15:15:54 CST(-0600)] <anastasiac> michelled, if the 'testing' jiras are more about tests than about testing, might the component better be names "Tests" ? or am I misunderstanding?
[15:16:15 CST(-0600)] <anastasiac> and yes, right now "demo portal" covers the portal and the demos that are or should be in it
[15:16:16 CST(-0600)] <michelled> well, changes to jqUnit are tests
[15:17:12 CST(-0600)] <michelled> it doesn't really matter to me what we call it but I think testing is more descriptive. it's about our testing infrastructure
[15:17:30 CST(-0600)] <michelled> I wouldn't want JIRAs about unit tests to be filed under testing
[15:17:46 CST(-0600)] <michelled> they should be filed with the component they are testing
[15:18:59 CST(-0600)] <michelled> anastasiac: this is an example of the JIRA that I would file under testing: http://issues.fluidproject.org/browse/FLUID-4027
[15:20:04 CST(-0600)] <anastasiac> ok, sure - "Testing" is fine. and I agree about unit tests for a particular component
[15:27:22 CST(-0600)] <michelled> Justin_o: I just added two new components - Testing and Release
[16:18:39 CST(-0600)] <michelled> fluid-everyone: I've removed the QA component in JIRA and renamed Testing to Testing Infrastructure