fluid-work IRC Logs-2009-09-30
- Fluid IRC Log Bot
[06:31:25 EDT(-0400)] * heidi_ (n=thesumme@bas5-oshawa95-1176457717.dsl.bell.ca) has joined #fluid-work
[07:08:48 EDT(-0400)] * heidi_ (n=thesumme@bas5-oshawa95-1176457717.dsl.bell.ca) has joined #fluid-work
[08:23:31 EDT(-0400)] * laurel (n=Laurel@142.150.154.178) has joined #fluid-work
[08:26:18 EDT(-0400)] * Justin_o (n=Justin@142.150.154.171) has joined #fluid-work
[09:09:34 EDT(-0400)] * fj4000 (n=Main@CPE0018f85ab63e-CM001692f5798c.cpe.net.cable.rogers.com) has joined #fluid-work
[09:16:59 EDT(-0400)] * anastasiac (n=team@142.150.154.189) has joined #fluid-work
[09:23:08 EDT(-0400)] <anastasiac> Justin_o, I was asked to work on a renderer demo for the portal, and to try to get it done before the end of bug parade, but the JIRA I created for it, FLUID-3209, isn't on the bug parade... should it be added?
[09:23:33 EDT(-0400)] <anastasiac> colinclark is reviewing the code I have so far, but there's still work to be done
[09:23:44 EDT(-0400)] <Justin_o> anastasiac: i thought it was there
[09:23:50 EDT(-0400)] <anastasiac> so did I 
[09:25:39 EDT(-0400)] <Justin_o> jessm: I thought FLUID-3209 was on the bug parade, but it doesn't seem to be there... was it removed or did it just not get added or did we decide not to add it... i can't seem to remember
[09:37:55 EDT(-0400)] <jessm> Justin_o: i haven't updated with the two new adds yet this a.m.
[09:38:51 EDT(-0400)] <Justin_o> oh okay
[09:39:09 EDT(-0400)] <jessm> 3209 + 3202
[09:39:21 EDT(-0400)] <jessm> i'll get it out in a few minutes
[09:45:50 EDT(-0400)] <jessm> Justin_o: what is the convention for marking things completed in the bug parade emails? *COMPLETED*?
[09:45:57 EDT(-0400)] <jessm> or *CLOSED*
[09:46:17 EDT(-0400)] <Justin_o> jessm: once it's passed review and testing it is marked as closed in jira and on the bug parade
[09:46:38 EDT(-0400)] <jessm> k
[09:54:30 EDT(-0400)] <fj4000> jessm: FLUID-3212 should be marked for review in the parade, i think
[09:55:03 EDT(-0400)] <jessm> ok
[09:55:25 EDT(-0400)] <fj4000> thanks
[09:57:15 EDT(-0400)] <jessm> any other changes to bug parade? i'll send out another email
[09:57:43 EDT(-0400)] <fj4000> jessm: you might want to look at my email response to Laurels stuff
[09:57:50 EDT(-0400)] <fj4000> i reviewed a fair # of her items
[09:57:51 EDT(-0400)] <jessm> got that, thanks
[10:03:44 EDT(-0400)] <jessm> Justin_o: any idea if we'll actually be able to get FLUID-2980 done by release?
[10:04:47 EDT(-0400)] <Justin_o> jessm: doubtful since I Antranig hasn't been available.. that one is there if he gets a chance to do some work...
[10:05:15 EDT(-0400)] <jessm> k
[10:06:12 EDT(-0400)] <jessm> sorry for all the update emails y'all β i think i've caught up with all the emails and IRC logged information. Please let me know your updates
[10:10:18 EDT(-0400)] * athena (i=482479dc@gateway/web/freenode/x-oovxovocpnutwivf) has joined #fluid-work
[10:32:46 EDT(-0400)] * Bosmo1 (n=Bosmon@ucb-np1-236.colorado.edu) has joined #fluid-work
[10:33:16 EDT(-0400)] <Bosmo1> Hello guys
[10:33:23 EDT(-0400)] <Bosmo1> I am officially Alive again 
[10:33:35 EDT(-0400)] <Bosmo1> I guess I will take http://issues.fluidproject.org/browse/FLUID-2980 first...
[10:34:47 EDT(-0400)] <jessm> Bosmo1: that's the one!
[10:35:11 EDT(-0400)] <jessm> we were just talking about that this a.m.
[10:42:29 EDT(-0400)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[10:42:35 EDT(-0400)] * clown (n=clown@142.150.154.101) has left #fluid-work
[10:43:05 EDT(-0400)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[11:03:56 EDT(-0400)] * michelled (n=team@142.150.154.193) has joined #fluid-work
[11:15:49 EDT(-0400)] <laurel> fj4000: some advice on your advice??
[11:15:59 EDT(-0400)] <fj4000> fire away
[11:16:09 EDT(-0400)] <laurel> http://issues.fluidproject.org/browse/FLUID-3200 - reviewed (perhaps it is better to keep your testing material only in your test files? It's too easy to forget to comment out code...)
[11:16:16 EDT(-0400)] <laurel> quote from your email
[11:16:24 EDT(-0400)] <fj4000> oh
[11:16:37 EDT(-0400)] <fj4000> the comment said teh code commented out was for testing purposes only
[11:16:41 EDT(-0400)] <fj4000> i was thinking
[11:16:46 EDT(-0400)] <laurel> I'm good with that, but probably need a better way to test out the php code
[11:17:01 EDT(-0400)] <laurel> so was looking for a suggestion
[11:17:01 EDT(-0400)] <fj4000> maybe that testing material could be put somewhere else other than the core code
[11:17:10 EDT(-0400)] <fj4000> like your testing suite
[11:17:28 EDT(-0400)] <fj4000> so.....
[11:17:42 EDT(-0400)] <laurel> hmm...not sure the testing suite will do it, because I wanted to test posting some variables to the page directly
[11:17:50 EDT(-0400)] <fj4000> could you make a (non-committed, perhaps) post test file?
[11:17:57 EDT(-0400)] <fj4000> the file could fake the $_POST var
[11:17:59 EDT(-0400)] <laurel> yes... i think that would work better
[11:18:16 EDT(-0400)] <fj4000> that way, we never see your "just testing" code...only the main code
[11:18:43 EDT(-0400)] <laurel> at the moment the commented code hard codes the two posted vars - in order to hit the page directly (bypass the js pages).
[11:18:45 EDT(-0400)] <colinclark> that makes a fair bit of sense
[11:19:01 EDT(-0400)] <laurel> ok..I'll pull those commented pieces out
[11:19:52 EDT(-0400)] <laurel> Justin_o, jessm: is there a jira I can use to commit this change under?
[11:21:31 EDT(-0400)] <michelled> laurel: http://issues.fluidproject.org/browse/FLUID-3208
[11:21:50 EDT(-0400)] <laurel> thats what I was thinking too (though strictly speaking it isn't really a "comment")
[11:22:00 EDT(-0400)] <laurel> but it is "code cleanup"
[11:22:05 EDT(-0400)] <laurel> thx michelled
[11:22:37 EDT(-0400)] <michelled> np, also, I committed your framework copyright patch
[11:22:57 EDT(-0400)] <michelled> I was wondering if you are checking the dates on the copyright statements as you are fixing them?
[11:23:32 EDT(-0400)] <michelled> they are probably correct but it wouldn't hurt to take a peak at when the file was created since you are looking at the file histories anyway
[11:25:29 EDT(-0400)] <jessm> standup
[11:25:42 EDT(-0400)] <jessm> standup in 5 that is
[11:25:51 EDT(-0400)] * anastasiac sits back down
[11:26:08 EDT(-0400)] <jessm> LOL
[11:26:10 EDT(-0400)] <laurel> ha...i just said that aloud at the same time you posted...thx jessm
[11:26:11 EDT(-0400)] <jessm> that was funny
[11:33:05 EDT(-0400)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[11:39:23 EDT(-0400)] * elicochran (n=elicochr@169.229.212.41) has joined #fluid-work
[11:48:07 EDT(-0400)] <fj4000> wow.....
[11:48:36 EDT(-0400)] <colinclark> ok, so, scheduling
[11:48:48 EDT(-0400)] <laurel> jessm: Jacob reviewed 3189 (the cache key issue) but listed it in the email he wrote yesterday as 3149.
[11:48:50 EDT(-0400)] <colinclark> we can do a kettle "talkthrough" as yura called it
[11:49:08 EDT(-0400)] <colinclark> my secret is that i didn't have time to eat breakfast before my morning meeting
[11:49:11 EDT(-0400)] <colinclark> so i'm kind of hungry
[11:49:13 EDT(-0400)] <jessm> laurel: roger that
[11:49:22 EDT(-0400)] <colinclark> can we do it in an hour or so?
[11:49:37 EDT(-0400)] <colinclark> that way i can talk to fj4000 and eat a snack
[11:49:39 EDT(-0400)] <fj4000> colinclark: want to talk after that?
[11:49:51 EDT(-0400)] <michelled> a little process thing which perhaps people already know - when you review a bug from bug parade and it has passed the review, put a comment on the JIRA
[11:49:55 EDT(-0400)] <fj4000> ok, pls ping me when your good to chat
[11:50:00 EDT(-0400)] <michelled> then the JIRA can be closed
[11:50:25 EDT(-0400)] <colinclark> so jessm was a bit worried about the backlog of "needs review" in our bug parade
[11:50:29 EDT(-0400)] <laurel> fj4000: so are we re-scheduling the line endings thing for tomorrow?
[11:50:32 EDT(-0400)] <laurel> or shall I just start work and post patches?
[11:50:32 EDT(-0400)] <colinclark> which tends to be the case at this stage while big blockers are being resolved
[11:50:40 EDT(-0400)] <colinclark> but jessm, are you seeing that list shrink a bit today?
[11:50:51 EDT(-0400)] <fj4000> laurel: go ahead without me
[11:50:58 EDT(-0400)] <laurel> thx
[11:50:59 EDT(-0400)] <jessm> colinclark: yes, shrinkage is happening
[11:51:15 EDT(-0400)] <fj4000> shudder
[11:51:39 EDT(-0400)] <colinclark> i was waiting for fj4000 there
[11:51:44 EDT(-0400)] <fj4000> lol
[11:51:49 EDT(-0400)] <fj4000> am i that predictable?
[11:51:55 EDT(-0400)] <colinclark> jessm: +1 on your latest M&W abstract
[11:52:03 EDT(-0400)] <colinclark> fj4000: pretty predictable 
[11:52:10 EDT(-0400)] <jessm> colinclark: bio from you and i'll submit
[11:52:14 EDT(-0400)] <colinclark> k
[11:52:19 EDT(-0400)] <colinclark> gonna grab my ajaxian bio and tweak slighlty
[11:52:22 EDT(-0400)] <colinclark> so
[11:52:25 EDT(-0400)] <colinclark> 1. bio
[11:52:27 EDT(-0400)] <colinclark> 2. breakfast
[11:52:29 EDT(-0400)] <colinclark> 3. fj4000
[11:52:32 EDT(-0400)] <colinclark> 4. kettle talkthrough
[11:52:35 EDT(-0400)] <colinclark> seem cool?
[11:52:39 EDT(-0400)] <jessm> rt
[11:52:47 EDT(-0400)] <laurel> fj4000: just so you know, I just removed that testing code that you noted in your review and committed using 3208 as issue number
[11:52:57 EDT(-0400)] <fj4000> ok
[11:53:00 EDT(-0400)] <fj4000> thnx
[11:53:18 EDT(-0400)] <laurel> thx to you for reviewing
[11:56:10 EDT(-0400)] <colinclark> so fj4000 and laurel, are we getting somewhere on the user experience for when a file actually gets downloaded from the Builder?
[11:56:25 EDT(-0400)] <colinclark> I'm a bit worried about shipping it until the experience is a little less jarring
[11:56:32 EDT(-0400)] <fj4000> we spoke about some ideas yesterday
[11:56:57 EDT(-0400)] <colinclark> is it at the point where some implementation can happen?
[11:57:00 EDT(-0400)] <fj4000> im not sure how we can handle the fast cached returns gracefully
[11:57:06 EDT(-0400)] <fj4000> i think so
[11:57:18 EDT(-0400)] <fj4000> we can toss some implementations to the list
[11:57:36 EDT(-0400)] <colinclark> maybe even here is fine
[11:58:37 EDT(-0400)] <fj4000> laurel: do you have any rough benchmarks on build performance?
[12:02:22 EDT(-0400)] <michelled> colinclark: I'll review your reorderer fixes tomorrow
[12:02:31 EDT(-0400)] <michelled> I'm bent on getting this path issue resolved today
[12:04:18 EDT(-0400)] * elicochran_ (n=elicochr@169.229.212.36) has joined #fluid-work
[12:11:12 EDT(-0400)] <colinclark> michelled: +1
[12:17:44 EDT(-0400)] <jessm> is it just me or did we lose a few pages here: http://fluidproject.org/about-us/our-mission/
[12:17:58 EDT(-0400)] <jessm> i thought our about us also had a contact us and our funder?
[12:18:28 EDT(-0400)] <jessm> laurel: ^ any idea what happened?
[12:20:37 EDT(-0400)] * clown_afk (n=clown@142.150.154.101) has joined #fluid-work
[12:31:50 EDT(-0400)] * athena (i=482479dc@gateway/web/freenode/x-wybzxtoncpvyvfcm) has joined #fluid-work
[12:33:27 EDT(-0400)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[12:38:17 EDT(-0400)] <colinclark> laurel: Have you had review on FLUID-3156 yet?
[12:41:28 EDT(-0400)] <laurel> colinclark: no review yet...reminded justin this morning
[12:41:31 EDT(-0400)] <laurel> hi jessm
[12:41:34 EDT(-0400)] <laurel> i'll go look
[12:42:25 EDT(-0400)] <laurel> sheesh
[12:42:31 EDT(-0400)] <laurel> looking at back end now.
[12:42:54 EDT(-0400)] <laurel> they were made inactive
[12:43:00 EDT(-0400)] <laurel> hmm...wonder how?
[12:45:01 EDT(-0400)] * clown (n=clown@142.150.154.101) has joined #fluid-work
[12:46:43 EDT(-0400)] <laurel> jessm?
[12:49:01 EDT(-0400)] <laurel> it is likely to be related to the upgrade...looking into it.
[12:49:17 EDT(-0400)] <jessm> laurel: thanks
[12:50:00 EDT(-0400)] <colinclark> jessm: fj4000 and I are going through his bug parade issues.
[12:50:03 EDT(-0400)] <jessm> laurel: partners page is also affected β it's our beige nave box
[12:50:06 EDT(-0400)] <jessm> nav
[12:50:19 EDT(-0400)] <colinclark> One of the things we are doing is making the titles clearer, and adding descriptions to them.
[12:50:23 EDT(-0400)] <jessm> colinclark: cool
[12:50:24 EDT(-0400)] <colinclark> Here's one for example: http://issues.fluidproject.org/browse/FLUID-3151
[12:52:36 EDT(-0400)] <jessm> colinclark: just gimme the numbers and i'll update
[12:52:48 EDT(-0400)] <colinclark> k
[12:53:15 EDT(-0400)] <colinclark> I think we're going to need to add another demo portal issue to bug parade... it was one we were intending to do all along, but it just slipped off the list.
[12:53:17 EDT(-0400)] <colinclark> http://issues.fluidproject.org/browse/FLUID-3210
[12:53:31 EDT(-0400)] <colinclark> Remove final report-specific cruft from demo portal once we've snapshotted the final report
[12:53:38 EDT(-0400)] <colinclark> jessm: Does this seem reasonable to you?
[12:54:03 EDT(-0400)] <jessm> yes β isn't it very similar to 3151?
[12:54:24 EDT(-0400)] <jessm> no matter β yes, to adding 3210
[12:57:26 EDT(-0400)] <colinclark> jessm: yes, they're related but slightly different
[12:57:36 EDT(-0400)] <colinclark> jessm: FLUID-3209 has been updated to be a bit more descriptive
[12:58:53 EDT(-0400)] <colinclark> jessm: I'm just chatting with fj4000 to decide if we can consolidate 3151 and 3210
[13:00:11 EDT(-0400)] <colinclark> jessm: Okay, you're totally right.
[13:00:18 EDT(-0400)] <colinclark> FLUID-3210 is really the best description of the issue
[13:00:37 EDT(-0400)] <colinclark> So we can close 3151 as being superseded by 3210
[13:00:43 EDT(-0400)] <colinclark> If you're comfortable with that
[13:00:44 EDT(-0400)] <colinclark> makes life easier
[13:00:46 EDT(-0400)] <colinclark> I can do it
[13:01:26 EDT(-0400)] <jessm> colinclark: do it to it
[13:02:57 EDT(-0400)] <laurel> jessm: poof! fixed
[13:03:06 EDT(-0400)] <fj4000> laurel: got a second?
[13:03:15 EDT(-0400)] <laurel> soonish.
[13:03:24 EDT(-0400)] <laurel> let me fix this website problem first
[13:03:25 EDT(-0400)] <jessm> laurel: thanks!
[13:03:26 EDT(-0400)] <fj4000> ok. Pls ping me when your ready to chat
[13:03:38 EDT(-0400)] <laurel> known bug in the version of cmsms that we have
[13:03:50 EDT(-0400)] <laurel> i'll fix it on the virtual server too
[13:04:02 EDT(-0400)] <jessm> laurel: thanks β looks good again
[13:04:07 EDT(-0400)] <laurel> silliness
[13:04:20 EDT(-0400)] <laurel> had to actually edit the php for cmsms
[13:04:46 EDT(-0400)] <jessm> laurel: how's that going to go for upgrades?
[13:05:25 EDT(-0400)] <laurel> hopefully they fix problem for next version, since apparently they've already fixed it in the SVN (according to forum posts).
[13:05:55 EDT(-0400)] * Bosmo1 (n=Bosmon@ucb-np1-212.colorado.edu) has joined #fluid-work
[13:07:13 EDT(-0400)] <colinclark> jessm: I've gone ahead and related the two issues, then closed FLUID-3151 and replaced it with 3210 on the bug parade. Sorry for all the confusion; we've got it all sorted out now
[13:07:14 EDT(-0400)] <colinclark> http://issues.fluidproject.org/browse/FLUID-3210
[13:07:56 EDT(-0400)] <jessm> rt β i've got it updated in the next email update
[13:08:05 EDT(-0400)] <colinclark> There is one other bug I'd like to chat with you about if you have a sec
[13:08:08 EDT(-0400)] <colinclark> jessm
[13:08:13 EDT(-0400)] <jessm> sure
[13:08:28 EDT(-0400)] <laurel> fj4000: what's up?
[13:08:32 EDT(-0400)] <colinclark> So at the moment, the experience of our Builder is a bit raw in one area.
[13:08:53 EDT(-0400)] <fj4000> laurel: can we chat about the download process?
[13:08:57 EDT(-0400)] <laurel> sure
[13:09:02 EDT(-0400)] <colinclark> When you click the download button, you get what appears to be a new page, with a very subtle message saying something to the effect of "Your download will start soon..."
[13:09:13 EDT(-0400)] <colinclark> But it's hard to notice, and will confuse the user in its current form.
[13:09:32 EDT(-0400)] <colinclark> fj4000 has agreed to do a minor design tweak to that experience to make it awesomer.
[13:09:51 EDT(-0400)] <colinclark> I don't have a JIRA ticket for it yet, but it strikes me as a last bit of polish we want to include in the Builder.
[13:10:00 EDT(-0400)] <colinclark> jessm: I'd love to hear your opinion about it.
[13:10:03 EDT(-0400)] <jessm> colinclark: i like the "last"
[13:10:08 EDT(-0400)] <jessm>
[13:10:08 EDT(-0400)] <colinclark>
[13:10:11 EDT(-0400)] <jessm> last bit of polish
[13:10:21 EDT(-0400)] <colinclark> For reference, here's a link to the Builder so you can see it yourself and see if you agree:
[13:10:22 EDT(-0400)] <jessm> bug parade still feels like a swarm
[13:10:33 EDT(-0400)] <colinclark> http://142.150.154.58/builder/
[13:10:44 EDT(-0400)] <colinclark> jessm: Yep, but it's starting to settle down, I think.
[13:11:03 EDT(-0400)] <colinclark> Our biggest concern right now is michelled's blocker, which is taking quite a bit of time. And it's a total blocker for Engage 0.1
[13:11:04 EDT(-0400)] <jessm> colinclark: i agree β polish needed β i didn't even see it at first
[13:11:09 EDT(-0400)] <colinclark> ok
[13:11:17 EDT(-0400)] <colinclark> I'll file a JIRA about it.
[13:11:21 EDT(-0400)] <jessm> k, thanks
[13:11:29 EDT(-0400)] <jessm> colinclark: which # is MDs blocker?
[13:11:35 EDT(-0400)] <colinclark> lemme check
[13:11:36 EDT(-0400)] <fj4000> colinclark: is that ticket going on the parade?
[13:11:43 EDT(-0400)] <colinclark> fj4000: If the proxy king wills it, yes
[13:11:48 EDT(-0400)] <fj4000> ok
[13:12:03 EDT(-0400)] <jessm> fj4000: colinclark yeah, let's put it on, but it's obviously not a blocker and is a last bit o' polish
[13:12:48 EDT(-0400)] <colinclark> jessm: http://issues.fluidproject.org/browse/ENGAGE-88
[13:12:51 EDT(-0400)] <colinclark> That's MD's big blocker
[13:12:58 EDT(-0400)] <colinclark> In short, she's got Kettle building nicely
[13:13:08 EDT(-0400)] <colinclark> We're still sorting out some last URL path issues.
[13:13:20 EDT(-0400)] <jessm> cool
[13:13:22 EDT(-0400)] <colinclark> Now that Bosmo1 is around, he might be able to help
[13:13:26 EDT(-0400)] <colinclark> sorry, not ENGAGE-88
[13:13:28 EDT(-0400)] <colinclark> I suck
[13:13:30 EDT(-0400)] <jessm> keep on keeping on gang β this feels exciting
[13:13:37 EDT(-0400)] <colinclark> This one, jessm: http://issues.fluidproject.org/browse/ENGAGE-95
[13:13:40 EDT(-0400)] <colinclark> It is exciting
[13:14:22 EDT(-0400)] <laurel> hi jessm and colinclark: overhearing your conversation
[13:14:46 EDT(-0400)] <laurel> wondering if the "polish" is going to be applied to the component or the website or both (I think both is most likely, but just checking)
[13:16:06 EDT(-0400)] <colinclark> laurel: Is there a difference?
[13:16:11 EDT(-0400)] <colinclark> I imagine this stuff goes in the component?
[13:16:17 EDT(-0400)] <colinclark> jessm: http://issues.fluidproject.org/browse/FLUID-3215
[13:16:24 EDT(-0400)] <colinclark> I'm not sure the title is super awesome
[13:16:49 EDT(-0400)] <laurel> um yes, in that one is suitably added to bug parade and involves checking in code, whereas a website task isn't really needed to be added to bug parade, since there are no commits
[13:17:05 EDT(-0400)] <laurel> doesn't*
[13:17:05 EDT(-0400)] <colinclark> Well, I guess that wasn't quite my question.
[13:17:18 EDT(-0400)] <colinclark> The question here is "where should this fix go?"
[13:17:27 EDT(-0400)] <colinclark> And I'm assuming it goes within the markup for the component, right?
[13:17:57 EDT(-0400)] <laurel> kinda hard to tell so far. I've not checked in any of the instructions or other surrounding info in the markup for the component.
[13:18:04 EDT(-0400)] <colinclark> ?!?
[13:18:17 EDT(-0400)] <fj4000> so the instructions sit outside the component?
[13:18:21 EDT(-0400)] <laurel> yes
[13:18:26 EDT(-0400)] <colinclark> Any particular reason why?
[13:18:49 EDT(-0400)] <laurel> hmm
[13:19:31 EDT(-0400)] <laurel> i guess because the markup for the page could be done in different ways, so the instructions would probably change depending on the markup
[13:19:55 EDT(-0400)] <laurel> so for instance, the demo html has both a checkall and a reset button, but the website doesn't
[13:21:36 EDT(-0400)] <colinclark> laurel: I'm not sure I follow your logic. We build Infusion component to be, by nature, customizable in terms of their markup.
[13:21:54 EDT(-0400)] <colinclark> And we like to ship templates with our components the represent the best possible default design.
[13:22:09 EDT(-0400)] <colinclark> So I guess I'm trying to understand if there's stuff in the web site that should actually be in the component's template?
[13:22:22 EDT(-0400)] <colinclark> Or whether it's just too context-dependent, in which case it should be on the web site.
[13:22:39 EDT(-0400)] <fj4000> an easy fix, in my mind, would be to simlpy put the instructions within the component container, right?
[13:23:04 EDT(-0400)] <fj4000> and identify it through an option
[13:23:46 EDT(-0400)] <laurel> seems reasonable
[13:23:52 EDT(-0400)] <colinclark> fj4000: Definitely one strategy is to put awesome stuff in the template
[13:23:56 EDT(-0400)] <fj4000> since it seems like the component is going to need to control the state of the instructions
[13:24:09 EDT(-0400)] <colinclark> It's just a question of whether this counts as "awesome" or as something really specific to our website.
[13:24:10 EDT(-0400)] <fj4000> colinclark: yes
[13:25:48 EDT(-0400)] <fj4000> maybe we could merge the instructions proper with the verbose instructions... since it feels a little redundant
[13:26:09 EDT(-0400)] <fj4000> and generalize them at the same time
[13:30:13 EDT(-0400)] <fj4000> laurel: ok, i think im going to take some liberties here and revamp all the text up to and including the 3 instructions
[13:36:36 EDT(-0400)] <laurel> not a problem.
[13:36:54 EDT(-0400)] <laurel> i'm not at all attached to them
[13:38:48 EDT(-0400)] <laurel> so colinclark...did we decide to proceed with modifications to the website version and merge that back into the component for 1.2?
[13:39:01 EDT(-0400)] <colinclark> laurel: I'd suggest doing whatever is most convenient
[13:39:11 EDT(-0400)] <colinclark> And let's file a bug for the template cut & paste in the website
[13:39:20 EDT(-0400)] <laurel> ok..i can do that.
[13:39:24 EDT(-0400)] <colinclark> And one for merging any awesomeness from the website into the template
[13:39:28 EDT(-0400)] <colinclark> And we're cool
[13:39:33 EDT(-0400)] <laurel> great{color}
[13:41:25 EDT(-0400)] <colinclark> laurel: I reviewed your FLUID-3156 fixes and they look good
[13:41:30 EDT(-0400)] <colinclark> Commented to this effect on the JIRA
[13:41:34 EDT(-0400)] <laurel> thanks so much
[13:41:43 EDT(-0400)] <colinclark> So jessm, we can close FLUID-3156
[13:42:48 EDT(-0400)] <laurel> any chance you can check 3157 too?
[13:43:00 EDT(-0400)] <laurel> related
[13:43:33 EDT(-0400)] <colinclark> laurel: I'm looking at 3157 right now
[13:43:40 EDT(-0400)] <laurel> yeehaw
[13:43:56 EDT(-0400)] <colinclark> I like what you've got here, but I see a few problems to address before we ship it.
[13:45:06 EDT(-0400)] <colinclark> So it looks like you've got your ARIA roles and properties inside the markup there.
[13:45:18 EDT(-0400)] <colinclark> laurel: Line 34 of CustomBuild.html
[13:45:39 EDT(-0400)] <colinclark> This is pretty much the same issue as Joan encountered, and it's a common one.
[13:45:57 EDT(-0400)] <colinclark> Basically, we should always add ARIA roles, properties, and states via JavaScript instead of in the markup.
[13:46:02 EDT(-0400)] <colinclark> The reason here is graceful degradation
[13:46:12 EDT(-0400)] <colinclark> An ARIA role describes a JS-powered behaviour of the UI.
[13:46:19 EDT(-0400)] <colinclark> But if JavaScrpt is turned off, that behaviour will be missing
[13:46:29 EDT(-0400)] <colinclark> So the markup shouldn't have that role attached to it.
[13:46:41 EDT(-0400)] <colinclark> Whereas, if we add roles and properties in JavaScript, they won't get added if JS is turned off.
[13:46:43 EDT(-0400)] <laurel> ah...again learning new stuff
[13:46:46 EDT(-0400)] * jayshao (n=jayshao@ool-4573130c.dyn.optonline.net) has joined #fluid-work
[13:47:00 EDT(-0400)] <colinclark> Along with it, a super-minor issue
[13:47:10 EDT(-0400)] <colinclark> This is totally trivial, but still worth addressing
[13:47:20 EDT(-0400)] <colinclark> looks like your buttons have titles on them, which is great
[13:47:30 EDT(-0400)] <colinclark> but you've got funny whitespace there
[13:47:38 EDT(-0400)] <laurel> ok...willcheck that
[13:47:39 EDT(-0400)] <colinclark> title = "Check all Modules"
[13:47:48 EDT(-0400)] <colinclark> as opposed to title="Check all Modules"
[13:48:03 EDT(-0400)] <laurel> doh
[13:48:09 EDT(-0400)] <laurel> will do
[13:48:33 EDT(-0400)] <laurel> can i re-open, address those issues and then commit?
[13:48:43 EDT(-0400)] <laurel> they aren't closed, but "unresolve"
[13:48:50 EDT(-0400)] * jayshao (n=jayshao@ool-4573130c.dyn.optonline.net) has joined #fluid-work
[13:49:35 EDT(-0400)] <laurel> do you have a ref for adding aria roles via javascript?
[13:49:50 EDT(-0400)] <colinclark> yes, go ahead and reopen those issues
[13:50:40 EDT(-0400)] <colinclark> laurel: this is sort of a funny place to send you...
[13:50:41 EDT(-0400)] <colinclark> http://www.slideshare.net/ajaxexperience2009/colin-clark-accessible-u-is-with-j-query-and-infusion1
[13:50:48 EDT(-0400)] <laurel> grin
[13:51:10 EDT(-0400)] <colinclark> Slide 27 has the meat of it
[13:51:21 EDT(-0400)] <colinclark> It's all just plain old jQuery
[13:51:52 EDT(-0400)] <colinclark> For FLUID-3157, a couple of other comments
[13:52:32 EDT(-0400)] <colinclark> I wonder if it might make sense for your getNameString() code to change slightly
[13:52:41 EDT(-0400)] <colinclark> I notice that you return "" if there are no modules selected
[13:52:53 EDT(-0400)] <colinclark> but then in another method you check if it's "" and then reset it to "none"
[13:53:15 EDT(-0400)] <colinclark> Why not actually start getNameString() by explicitly checking for no selections and returning the string "none"
[13:53:35 EDT(-0400)] <colinclark> And then you just need to blast the string directly into the DOM
[13:53:59 EDT(-0400)] <colinclark> Also, this line here: jQuery("#modulesSelected").html("<p>Modules Selected: " + modulesSelected + "</p>");
[13:54:09 EDT(-0400)] <colinclark> line 90 of builder.js
[13:54:24 EDT(-0400)] <laurel> yup
[13:54:27 EDT(-0400)] <anastasiac> colinclark, for whenever you get back to the Renderer demo code review: Please do an update - I've added all possible strings to the rendering process, to illustrate its usefulness for internationalization
[13:54:30 EDT(-0400)] <colinclark> I wonder if there's a way to do this without outputting the HTML directly
[13:54:41 EDT(-0400)] <colinclark> anastasiac: You're on deck. Thanks for the reminder
[13:54:46 EDT(-0400)] <anastasiac> np
[13:54:57 EDT(-0400)] <colinclark> laurel: the last issue about outputting HTML directly is a post-1.1.2 fix
[13:55:13 EDT(-0400)] <laurel> ok
[13:55:18 EDT(-0400)] <colinclark> but i wanted to mention it while I'm looking at the code
[13:55:37 EDT(-0400)] <colinclark> you should feel free to just grab this IRC transcript and dump it into the comments of the relevant JIRA issues (that's what I usually do)
[13:55:42 EDT(-0400)] <laurel> still getting the hang of a new programming paradigm
[13:56:11 EDT(-0400)] <colinclark> Oh!
[13:56:19 EDT(-0400)] <colinclark> And I just found a funny little bug
[13:56:24 EDT(-0400)] <colinclark> Sorry to lay all these on you at once
[13:56:39 EDT(-0400)] <colinclark> you have a function in CustomBuilder.js that is very well-named
[13:56:41 EDT(-0400)] <colinclark> createModuleNamesArray
[13:56:55 EDT(-0400)] <laurel> one by one wouldn't really be useful
[13:57:00 EDT(-0400)] <colinclark> And in it, there's a really funny statement
[13:57:03 EDT(-0400)] <colinclark> var array = {};
[13:57:07 EDT(-0400)] <colinclark>
[13:57:44 EDT(-0400)] <colinclark> So maybe it should be an object, maybe an array
[13:58:07 EDT(-0400)] <colinclark> I guess it depends on what moduleValue actually is.
[13:58:39 EDT(-0400)] <colinclark> And I think that's it for FLUID-3157
[13:58:48 EDT(-0400)] <colinclark> I'll make a quick note on the JIRA that it needs a bit more baking
[13:59:10 EDT(-0400)] <colinclark> jessm: We'll need to reflect the fact that 3157 is being reopened in the parade, too
[13:59:29 EDT(-0400)] <laurel> ok...so not too terrible considering that was essentially the first javascript I've written
[13:59:45 EDT(-0400)] <jessm> colinclark: go it
[13:59:47 EDT(-0400)] <jessm> got it
[14:01:23 EDT(-0400)] <colinclark> laurel: One more issue... let's move the ARIA-related code from builder.js into CustomBuild.js
[14:01:32 EDT(-0400)] <colinclark> It should be integrated into the component, not living outside of it
[14:05:43 EDT(-0400)] <laurel> confirming to jessm: just re-opened http://issues.fluidproject.org/browse/FLUID-3157
[14:12:41 EDT(-0400)] <colinclark> oh, one other thing I thought of, fj4000
[14:12:43 EDT(-0400)] <colinclark> You still around?
[14:12:52 EDT(-0400)] <fj4000> yup
[14:13:00 EDT(-0400)] <colinclark> Are we gonna get rid of the standalone-demos folder?
[14:13:08 EDT(-0400)] <colinclark> or is there more of a discussion that needs to happen?
[14:13:15 EDT(-0400)] <colinclark> and what will we do with integration-demos?
[14:13:18 EDT(-0400)] <fj4000> eventually, when the keyboard assy demo and some others are ported
[14:13:21 EDT(-0400)] <colinclark> just leave it where it is?
[14:13:29 EDT(-0400)] <fj4000> we have to for now, i think
[14:13:32 EDT(-0400)] <colinclark> ah, didn't we do a keyboard-a11y demo?
[14:13:35 EDT(-0400)] <colinclark> How did that go?
[14:13:44 EDT(-0400)] <fj4000> ie isnt liking my code 
[14:13:49 EDT(-0400)] <colinclark> yack
[14:13:56 EDT(-0400)] <colinclark> so it got punted from the release, fj4000 ?
[14:14:05 EDT(-0400)] <colinclark> (that's okay if it did)
[14:14:06 EDT(-0400)] <fj4000> remember i mentioed it firing my events twice? i cant figure it out
[14:14:11 EDT(-0400)] <colinclark> yeah
[14:14:11 EDT(-0400)] <fj4000> i think so
[14:14:15 EDT(-0400)] <colinclark> so it's not in bug parade, right?
[14:14:19 EDT(-0400)] <colinclark> ok
[14:14:20 EDT(-0400)] <fj4000> no
[14:14:32 EDT(-0400)] <fj4000> i would have loved to have cleaned it all up
[14:14:41 EDT(-0400)] <colinclark> So I guess we could perhaps do some minor restructuring
[14:14:50 EDT(-0400)] <fj4000> but its going to be almost impossible, unless someone else could look at my demo and figure it out
[14:14:56 EDT(-0400)] <colinclark> here's an idea... don't know if it makes sense
[14:15:07 EDT(-0400)] <fj4000> ok
[14:15:09 EDT(-0400)] <colinclark> We create a directory inside demos/ called "other-demos"
[14:15:18 EDT(-0400)] <colinclark> And we put integration/ and standalone/ in there
[14:15:28 EDT(-0400)] <colinclark> and we don't link it to the portal, but at least all the demos live together
[14:15:29 EDT(-0400)] <colinclark> is that insane?
[14:15:35 EDT(-0400)] <fj4000> well....
[14:15:42 EDT(-0400)] <fj4000> i just have one issue....
[14:15:44 EDT(-0400)] <colinclark> ok
[14:16:00 EDT(-0400)] <fj4000> it feels like we're moving it for the sake of moving it to a nicer sounding folder
[14:16:08 EDT(-0400)] <fj4000> since in the end, they will all be ported
[14:16:16 EDT(-0400)] <fj4000> everything should have a new home
[14:16:33 EDT(-0400)] <fj4000> so we would move them, and then continue working on porting them?
[14:18:07 EDT(-0400)] <colinclark> fj4000: That's the idea
[14:18:19 EDT(-0400)] <colinclark> My suggestion was just that it might be confusing to have three different demos folders?
[14:18:25 EDT(-0400)] <colinclark> I'm not convinced of this, just wondering out loud
[14:18:26 EDT(-0400)] <fj4000> yes, its horrible
[14:19:04 EDT(-0400)] <fj4000> if we want to really force a cleanup then it makes sense
[14:19:18 EDT(-0400)] <fj4000> and i hate having 3 demo folders
[14:19:55 EDT(-0400)] <fj4000> we should have a disclaimer
[14:20:17 EDT(-0400)] <fj4000> saying that any new place would be extremely temp. until they're all ported
[14:24:45 EDT(-0400)] <fj4000> colinclark, laurel: http://issues.fluidproject.org/browse/FLUID-3215
[14:24:53 EDT(-0400)] <fj4000> pls have a look at the attached images
[14:25:07 EDT(-0400)] <fj4000> one before you build, one during/after the build
[14:25:25 EDT(-0400)] <laurel> fj4000: thanks
[14:25:54 EDT(-0400)] <colinclark> fj4000: as for demo folders, i think that makes sense
[14:26:14 EDT(-0400)] <fj4000> ok
[14:33:09 EDT(-0400)] <laurel> fj4000: very nice
[14:33:52 EDT(-0400)] <fj4000> laurel: thanks. Let's see what the rest of the feedback is
[14:38:06 EDT(-0400)] * athena (i=482479dc@gateway/web/freenode/x-hlhceqhomqfymwld) has joined #fluid-work
[14:38:30 EDT(-0400)] <colinclark> laurel: How do fj4000's screens look in terms of time to implement?
[14:38:55 EDT(-0400)] <fj4000> assuming we pair on it?
[14:39:11 EDT(-0400)] <colinclark> that depends on how much time we've all got
[14:39:15 EDT(-0400)] <colinclark> fj4000: Two questions/concerns about the first screen.
[14:39:33 EDT(-0400)] <fj4000> shoot
[14:39:49 EDT(-0400)] <colinclark> I think there might be a problem with including links while the download is being generated
[14:39:55 EDT(-0400)] <colinclark> basically, we're not using any fancyness
[14:40:03 EDT(-0400)] <colinclark> So the browser sits and waits for a response to its request
[14:40:11 EDT(-0400)] <colinclark> if the user were to click a link, we'd stop the request, right?
[14:40:21 EDT(-0400)] <colinclark> I guess we could open them up in new windows, but that might be awkward
[14:40:27 EDT(-0400)] <colinclark> thoughts?
[14:40:35 EDT(-0400)] <fj4000> not necessarily
[14:40:56 EDT(-0400)] <fj4000> if the links point to new tabs/windows, we're no interrupting the process, i dont think
[14:41:19 EDT(-0400)] <fj4000> oh, sorry - i didnt see you already thought of that
[14:41:22 EDT(-0400)] <colinclark>
[14:41:24 EDT(-0400)] <colinclark> ok
[14:41:34 EDT(-0400)] <colinclark> do the other question...
[14:41:38 EDT(-0400)] <colinclark> how does the dialog ever close?
[14:41:50 EDT(-0400)] <colinclark> does the user have to do it? is this page just a dead end?
[14:41:55 EDT(-0400)] <fj4000> there would have to be a close button of sorts
[14:41:58 EDT(-0400)] <colinclark> ok
[14:42:00 EDT(-0400)] <colinclark> so the user would do it
[14:42:03 EDT(-0400)] <fj4000> other than the main nav, yes
[14:42:11 EDT(-0400)] <fj4000> is there another way?
[14:42:14 EDT(-0400)] <fj4000> the thing is
[14:42:30 EDT(-0400)] <fj4000> I asked Laurel how long would it take to run a heavy build
[14:42:54 EDT(-0400)] <fj4000> and it sounds so fast, we might even assume to auto close the dialog after a couple minutes
[14:43:11 EDT(-0400)] <fj4000> since a heavy build takes (1st time) around 30s. or so
[14:43:22 EDT(-0400)] <fj4000> (pls correct me if im wrong laurel)
[14:43:30 EDT(-0400)] <colinclark> fj4000: it could get slower under load, i think
[14:43:32 EDT(-0400)] <fj4000> either way, its not super graceful
[14:43:33 EDT(-0400)] <laurel> i think so
[14:43:43 EDT(-0400)] <fj4000> yes, it could
[14:43:53 EDT(-0400)] <colinclark> I guess I'm wondering if it makes more sense to make it a "new page" rather than a dialog box
[14:43:54 EDT(-0400)] <fj4000> sourceforge just throws the page as a dead end
[14:43:57 EDT(-0400)] <colinclark> yeah
[14:43:57 EDT(-0400)] <laurel> i recorded some specs - let me check the jira
[14:44:46 EDT(-0400)] <fj4000> the little catch here, is js can throw up this dialog....if the server is under major stress, it might be a while before you see a page refresh
[14:45:02 EDT(-0400)] <fj4000> which means to the user, a blank page for an unknown amount of time
[14:45:26 EDT(-0400)] <laurel> 22 seconds, and then 33ms for subsequent requests
[14:46:07 EDT(-0400)] <fj4000> but, perhaps if we go to a new page and then begin the build, it wouldnt be a noticeable delay....im not sure....
[14:48:07 EDT(-0400)] * elicochran (n=elicochr@dhcp-169-229-212-36.LIPS.Berkeley.EDU) has joined #fluid-work
[14:49:48 EDT(-0400)] <fj4000> colinclark: what do you think of the pre- Build layout ?
[14:51:04 EDT(-0400)] <fj4000> now that im thinking about it, a new page does seem more desireable that a dialog box....
[14:51:52 EDT(-0400)] <colinclark> fj4000: I think it looks good
[14:57:58 EDT(-0400)] <colinclark> jessm: elicochran just found a bug in my uploader fix
[14:58:10 EDT(-0400)] <colinclark> It works, but it has a subtle and dramatic error in it.
[14:58:17 EDT(-0400)] <colinclark> Cause by JavaScript's own evilness.
[14:58:32 EDT(-0400)] <colinclark> Don't get me wrong, I love JavaScript, but this should have caused an error in the interpreter
[14:59:37 EDT(-0400)] <colinclark> anyway, I'm gonna reopen FLUID-3114
[15:00:34 EDT(-0400)] <laurel> michelled: more stuff in 3192 for you http://issues.fluidproject.org/browse/FLUID-3192
[15:01:42 EDT(-0400)] <laurel> i'm not feeling confident to do the demos directory (since none of them have history).
[15:02:14 EDT(-0400)] <laurel> i can work with someone else to do it if anyone has time.
[15:02:24 EDT(-0400)] <laurel> and knows the history of those demos
[15:03:52 EDT(-0400)] <jessm> colinclark: i still have 3114 in review
[15:04:42 EDT(-0400)] <colinclark> thx
[15:06:54 EDT(-0400)] * Bosmo1 (n=Bosmon@dlc75-204-dhcp.colorado.edu) has joined #fluid-work
[15:10:05 EDT(-0400)] * athena waves to Bosmo1
[15:10:16 EDT(-0400)] <athena> do i need to create a JIRA for that pager issue we emailed about?
[15:10:16 EDT(-0400)] <jessm> anyone know the date that Fluid Infusion 0.1 was released?
[15:10:30 EDT(-0400)] <colinclark> jessm: I can find out if you want
[15:10:36 EDT(-0400)] <jessm> colinclark: awesome
[15:11:44 EDT(-0400)] <colinclark> jessm: http://www.nabble.com/Announcing-the-Fluid-0.1-Release-td14106420.html
[15:11:47 EDT(-0400)] <colinclark> Dec 01, 2007
[15:12:13 EDT(-0400)] <jessm> thanks much
[15:12:19 EDT(-0400)] <jessm> i couldn't find the nabble thing β
[15:12:21 EDT(-0400)] <colinclark> so 9 months, it took us
[15:12:37 EDT(-0400)] <jessm>
[15:14:53 EDT(-0400)] <athena> how's the release going?
[15:40:05 EDT(-0400)] <fj4000> Justin_o: 3198 is ready for review (again)
[15:44:28 EDT(-0400)] <Justin_o> fj4000: thanks... i'll just be a minute... checking something with yura
[15:44:39 EDT(-0400)] <fj4000> ok
[16:13:50 EDT(-0400)] <fj4000> laurel: ping
[16:16:08 EDT(-0400)] <jessm> athena: it's going
[16:31:58 EDT(-0400)] <laurel> fj4000: sorry was coding with some help
[16:34:44 EDT(-0400)] * elicochran (n=elicochr@dhcp-169-229-212-41.LIPS.Berkeley.EDU) has joined #fluid-work
[16:37:28 EDT(-0400)] * laurel (n=Laurel@142.150.154.178) has left #fluid-work
[16:39:41 EDT(-0400)] <elicochran> colinclark, anastasiac : Ignore me if I'm being a pest. But when we released 1.1, we renamed the fluid namespace "fluid_1_2" (since 1.2 was going to be the next version). But now we're releasing 1.1.2, what should that namespace really be?
[16:43:14 EDT(-0400)] <anastasiac> elicochran, do you mean "what is the 'next version' going to be after 1.1.2?
[16:44:59 EDT(-0400)] <elicochran> anastasiac: no, not really. The release process includes a "post-release" step, that increments the namespace for the "next" version of Infusion, but that assumed steps like 1.1, 1.2. It didn't anticipate 1.1.2 (or 1.1.1 for that matter) so now we have a namespace that doesn't accurately represent the version number of the release.
[16:45:10 EDT(-0400)] <elicochran> the release that we're working on
[16:45:49 EDT(-0400)] <colinclark> elicochran: The namespace should be 1.1
[16:46:03 EDT(-0400)] <colinclark> We'll make a global change backwards before the release.
[16:46:20 EDT(-0400)] <elicochran> colinclark: just checking
[16:46:21 EDT(-0400)] <colinclark> Ordinarily, 1.1.x release would but cut off the 1.1.x branch, not out of trunk
[16:46:35 EDT(-0400)] <colinclark> But in this case, we did some fairly substantial directory restructuring that would have made backporting annoying.
[16:47:00 EDT(-0400)] <colinclark> So, a pretty standard release process for maintenance releases would be to do your work in trunk, then backport to the maintenance branch.
[16:47:15 EDT(-0400)] <colinclark> In this case, it's just a bit of a pain, so we'll "rewind" the version number in trunk and cut 1.1.2 from there.
[16:47:16 EDT(-0400)] <elicochran> those of use developing off of trunk will have to make a note of it
[16:47:28 EDT(-0400)] <colinclark> yes, it'll be a very short-term change
[16:47:31 EDT(-0400)] <colinclark> and then trunk will go back to 1.2
[16:47:38 EDT(-0400)] <elicochran> true
[16:47:44 EDT(-0400)] <elicochran> so I'll "skip" the release
[16:47:47 EDT(-0400)] <colinclark> We'll freeze the repository, tell everyone on fluid-work about it, and then off we go
[16:47:54 EDT(-0400)] <colinclark> elicochran: Yep
[16:48:04 EDT(-0400)] <colinclark> 1.2 is coming by end of November, I expect
[16:48:21 EDT(-0400)] <colinclark> With vast simplifications to both initSubcomponent() and the Renderer
[16:48:41 EDT(-0400)] <elicochran> colinclark: I figured you all were on top of it.
[16:48:48 EDT(-0400)] <colinclark> well, I don't feel quite on top of it
[16:49:01 EDT(-0400)] <colinclark> Had I been on top of it, we'd be cutting 1.1.2 out of the maintenance branch
[16:49:02 EDT(-0400)] <colinclark> but we're close
[16:49:03 EDT(-0400)] <colinclark>
[16:49:29 EDT(-0400)] <elicochran> colinclark: well, this was something that could have been overlooked
[16:49:40 EDT(-0400)] <colinclark>
[16:49:48 EDT(-0400)] <elicochran> so laurel is release manager?
[16:53:19 EDT(-0400)] * anastasiac (n=team@142.150.154.189) has left #fluid-work
[16:56:38 EDT(-0400)] <colinclark> elicochran: We haven't picked a release manager yet
[16:56:48 EDT(-0400)] <colinclark> We're each just picking up release manager tasks here and there
[16:56:59 EDT(-0400)] <colinclark> I'm kind of hoping fj4000 might do it again;.
[16:57:04 EDT(-0400)] <colinclark> He did well last time.
[16:57:11 EDT(-0400)] <elicochran> colinclark: laurel was asking me some release-y questions so I though she might be doing it
[16:57:23 EDT(-0400)] <colinclark> yeah, she's just picked up a few of those release-y tasks
[16:57:38 EDT(-0400)] <elicochran> colinclark: yes, fj4000 did an excellent job from what I heard
[16:57:43 EDT(-0400)] <elicochran>
[16:57:49 EDT(-0400)] <colinclark>
[16:57:52 EDT(-0400)] <fj4000> lol - i barely knew my left hand from my right
[16:58:11 EDT(-0400)] <fj4000> i think you guys are just buttering me up
[16:58:24 EDT(-0400)] <elicochran> left foot, left foot.... no, that's the break~
[16:58:49 EDT(-0400)] <fj4000> you guys are terrible
[16:58:51 EDT(-0400)] <elicochran> brake
[17:17:43 EDT(-0400)] * clown (n=clown@142.150.154.101) has left #fluid-work
[17:26:08 EDT(-0400)] * jayshao_ (n=jayshao@69.115.19.12) has joined #fluid-work
[18:37:33 EDT(-0400)] * athena (n=athena@64.198.210.170) has joined #fluid-work
[19:18:10 EDT(-0400)] * colinclark (n=colin@bas2-toronto09-1176130646.dsl.bell.ca) has joined #fluid-work
[19:22:24 EDT(-0400)] <athena> hey colinclark, how's the release looking?
[19:22:34 EDT(-0400)] <athena> think i'm closing in on fixing uportal's internal mobile support
[19:22:40 EDT(-0400)] <colinclark> athena: So far, so good for 1.1.2.
[19:22:45 EDT(-0400)] <colinclark> Great news!
[19:22:45 EDT(-0400)] <athena> awesome
[19:22:50 EDT(-0400)] <colinclark> That's so awesome.
[19:22:58 EDT(-0400)] <athena> so we've had some interesting conversation the last few days
[19:23:09 EDT(-0400)] <athena> getting lots done
[19:23:25 EDT(-0400)] <colinclark> I wish I was there.
[19:23:28 EDT(-0400)] <colinclark> Sounds like it's going really well.
[19:23:30 EDT(-0400)] <athena> yeah we do too
[19:23:37 EDT(-0400)] <athena> fluid definitely gets mentioned!
[19:23:44 EDT(-0400)] <colinclark> Oh, cool
[19:23:55 EDT(-0400)] <athena> we had a user interface discussion session
[19:24:07 EDT(-0400)] <athena> and there was a moment of confusion cuz there was like, no one to facilitate it
[19:24:07 EDT(-0400)] <athena> lol
[19:24:11 EDT(-0400)] <athena> so they got me
[19:27:52 EDT(-0400)] <athena> ok, off to dinner
[19:28:07 EDT(-0400)] <athena> we'll have to get you all in the loop after we're done conferencing and you're done releasing
[19:55:21 EDT(-0400)] <colinclark> athena: I bet you were great at facilitating the UI session! Can't wait to hear about it all.