fluid-work IRC Logs-2010-02-08

[04:32:55 EST(-0500)] * sveto (~sveto@62.44.108.2) has joined #fluid-work
[08:18:43 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[08:31:18 EST(-0500)] * jessm (~Jess@c-71-232-3-151.hsd1.ma.comcast.net) has joined #fluid-work
[08:50:17 EST(-0500)] * athena (~athena@adsl-76-250-193-123.dsl.wlfrct.sbcglobal.net) has joined #fluid-work
[08:53:49 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[09:16:45 EST(-0500)] * yura (~yura@user145-4.wireless.utoronto.ca) has joined #fluid-work
[09:30:39 EST(-0500)] * anastasiac (~team@142.150.154.193) has joined #fluid-work
[09:53:11 EST(-0500)] * clown (~clown@142.150.154.101) has joined #fluid-work
[09:56:07 EST(-0500)] * EricDalquist (~dalquist@2607:f388:e:0:221:9bff:fe37:e768) has joined #fluid-work
[10:18:06 EST(-0500)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[10:32:35 EST(-0500)] * alisonbenjamin (~alisonben@dsl-173-206-255-58.tor.primus.ca) has joined #fluid-work
[10:39:53 EST(-0500)] <colinclark> sveto: Just a heads up that I had some trouble merging your My Collection branch over the weekend. I'm looking at it now; sorry for the delay in getting it in.
[10:40:04 EST(-0500)] <colinclark> What was the issue you noticed regarding Object Code Entry?
[10:47:29 EST(-0500)] <sveto> colinclark: it is working fine, just throwing some FileNotFound exceptions when the code entry screen is accessed - it tries to find codeEntry.html under browse/html and artifactView/html, I noticed that those two services have the same target for their producer - artifacts/
[10:49:15 EST(-0500)] <colinclark> sveto: Yeah, that may be related to a change I made after I committed your patch...
[10:49:43 EST(-0500)] <colinclark> As we had discussed during code review for code entry, I think both the markup and data feed should be mounted relative to artifacts/
[10:49:52 EST(-0500)] <colinclark> Since they are directly about artifacts
[10:51:16 EST(-0500)] <colinclark> But I may well have made a half-complete change
[10:52:11 EST(-0500)] <sveto> colinclark: I wasn't able to find the reason for this exceptions, but I'll look more carefully
[10:52:16 EST(-0500)] <colinclark> Ok, thanks
[10:52:57 EST(-0500)] <sveto> about couchdb views for My Collection - there is the problem that it is hard to do a multiple key request to a couch view
[10:53:54 EST(-0500)] <sveto> so one solution will be to use the all_docs view and add an include_docs parameter to the query, all_docs supports POSTs with parameters the document ids
[10:54:40 EST(-0500)] <sveto> that will perfectly do, another solution short of using Lucene is to make individual queries for each artifact, but I prefer the all_docs way
[10:55:05 EST(-0500)] <colinclark> Seems like this might be a case where a Lucene view is simpler
[10:55:33 EST(-0500)] <colinclark> My goal was just to replace unnecessary Lucene views with plain old Couch view. But we should only do that where it makes sense.
[10:56:42 EST(-0500)] <sveto> well Lucene allows us to "or" search keys, so this will be the byId view that is doing that
[10:57:49 EST(-0500)] <colinclark> yep, that makes sense
[11:03:53 EST(-0500)] * sveto (~sveto@62.44.108.2) has left #fluid-work
[11:21:07 EST(-0500)] * jamon (jamon@mantis.openject.com) has joined #fluid-work
[11:33:21 EST(-0500)] * elicochran (~elicochra@dhcp-169-229-212-70.LIPS.Berkeley.EDU) has joined #fluid-work
[11:42:36 EST(-0500)] <jessm> justin_o: is ENGAGE-287 closed then? i just saw your commit for 286,287
[12:03:54 EST(-0500)] * yura (~yura@142.150.154.101) has joined #fluid-work
[12:13:43 EST(-0500)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[12:32:35 EST(-0500)] <jessm> hey everyone, i'm mucking around in JIRA on the release, so let me know if you're changing things around: http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10128
[12:35:22 EST(-0500)] <colinclark> jessm: Sure
[12:43:17 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[13:35:27 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[13:37:14 EST(-0500)] <justin_o> jessm: sorry got part way through a response and forgot to send it
[13:37:57 EST(-0500)] <jessm> justin_o: no worries – we'll have plenty of time to get to it
[13:37:59 EST(-0500)] <justin_o> basically what i was going to say was that I left it open since i think Artifact view may still need to get some translations done for it
[14:02:11 EST(-0500)] * Bosmon4 (~a@68.92.57.2) has joined #fluid-work
[14:02:16 EST(-0500)] <Bosmon4> Hi - I am here now
[14:02:25 EST(-0500)] <Bosmon4> In unprecedented multplicity....
[14:03:00 EST(-0500)] <Bosmon4> colinclark
[14:03:19 EST(-0500)] <colinclark> Bosmon4: You are multiplying daily!
[14:03:48 EST(-0500)] <colinclark> So, a question about your excellent Kettle-y changes, out curiosity
[14:04:16 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[14:04:51 EST(-0500)] <colinclark> You have modified several of the fluid.engage.mountXyz() functions to take an additional argument...
[14:04:57 EST(-0500)] <Bosmon4> yes, that is right
[14:05:08 EST(-0500)] <Bosmon4> I noticed that they used to be responsing indiscriminately to ALL HTTP methods
[14:05:16 EST(-0500)] <colinclark> Yes, good catch
[14:05:32 EST(-0500)] <Bosmon4> Which meant that it was impossible, for example, to have an acceptor which was capable of expressing interest in just GETs or POSTs
[14:05:39 EST(-0500)] <colinclark> Yeah
[14:05:48 EST(-0500)] <Bosmon4> Another collateral change was in the overall acceptor logic for determining when to return 405s
[14:05:48 EST(-0500)] <colinclark> So where can I see an example of how protoExp is defined?
[14:05:54 EST(-0500)] <colinclark> ah, cool
[14:06:10 EST(-0500)] <Bosmon4> So protoExp is a string which will be used as a regular expression
[14:06:22 EST(-0500)] <Bosmon4> You can see an example in the dataSpout and markupSpout registrars etc.
[14:06:27 EST(-0500)] <colinclark> Cool, I'll take a look
[14:06:28 EST(-0500)] <Bosmon4> The latter just registers against "GET"
[14:06:37 EST(-0500)] <colinclark> I'll run past you the strategy Justin and I are taking to fixing My Collection
[14:06:52 EST(-0500)] <colinclark> So, you might remember that Sveto has the only example of resource-oriented URLs in the system
[14:06:55 EST(-0500)] <Bosmon4> Whereas the former will register against either GET or GET|PUT|POST depending on the capabilities it determines in the underlying dataSource
[14:06:57 EST(-0500)] <Bosmon4> Yes
[14:07:13 EST(-0500)] <colinclark> And, it's clear that the new dataSpout() is not yet ready to handle paths deeper than two segments, which is perfectly fine for now
[14:07:23 EST(-0500)] <colinclark> So we're going to have to go a little bit lower level...
[14:07:23 EST(-0500)] <Bosmon4> There's clearly a lot more work to be done in this area, but at least we are now even within rock-heaving distance of responding to HTTP grammar appropriately
[14:07:35 EST(-0500)] <colinclark> We'l write an acceptor that is, for now, hard-coded to My Collections needs
[14:07:40 EST(-0500)] <colinclark> URLs look like this:
[14:07:41 EST(-0500)] <Bosmon4> Yes, I imagined that Sveto's stuff would need to be rejigged a bit to work with the new model
[14:08:05 EST(-0500)] <Bosmon4> But he already had a hard-coded acceptor, right?
[14:08:10 EST(-0500)] <colinclark> No
[14:08:14 EST(-0500)] <Bosmon4> But it was just one that actually responded to all requests....
[14:08:16 EST(-0500)] <Bosmon4> ah
[14:08:32 EST(-0500)] <colinclark> He tried to patch fluid.engage.makeAcceptorForResource()
[14:08:38 EST(-0500)] <Bosmon4> oh
[14:08:48 EST(-0500)] <Bosmon4> I remember now
[14:08:50 EST(-0500)] <colinclark> Which, when merged with your changes, caused the spout code to break
[14:09:00 EST(-0500)] <colinclark> So, anyway, we'll write our own hard-coded acceptor
[14:09:12 EST(-0500)] <Bosmon4> Yes well, that is left "largely" untouched... as part of the remaining EngageApp.js material
[14:09:17 EST(-0500)] <Bosmon4> But I guess it does have the extra argument
[14:09:31 EST(-0500)] <colinclark> For sure, there's even a comment saying that stuff is brittle and should be deprecated
[14:09:35 EST(-0500)] <Bosmon4> I'd like to look at what the conflict looks like but we are boarding in about 5 minutes...
[14:09:43 EST(-0500)] <colinclark> No worries
[14:10:01 EST(-0500)] <colinclark> We'll implement something and you can take a look whenever you land
[14:10:19 EST(-0500)] <colinclark> As long as it doesn't seem insane, this approach will at least get us to the point where we can merge My Collection
[14:10:24 EST(-0500)] <colinclark> Integration is the key over the next day or two
[14:10:35 EST(-0500)] <colinclark> My Collection, Artifact View and Goose book are still outstanding
[14:10:40 EST(-0500)] <colinclark> Then we can go onto a bug parade
[14:10:48 EST(-0500)] <Bosmon4> But yeah, for ENGAGE-335 I think I can declare that the remaining diffs are cruft
[14:10:56 EST(-0500)] <Bosmon4> The version of those two files in trunk should be the one we accept
[14:11:27 EST(-0500)] <Bosmon4> But for the makeAcceptorResource changes... is there a JIRA with those diffs too?
[14:11:42 EST(-0500)] <colinclark> No, I didn't create a JIRA for it.
[14:11:45 EST(-0500)] <Bosmon4> ok
[14:12:03 EST(-0500)] <colinclark> I think, in the end, we'll just find that the approach wasn't sufficiently general
[14:12:29 EST(-0500)] <Bosmon4> Well, as I highlighted in my commit message, there is actually a fundamental error in the basic Acceptor algorithm
[14:12:37 EST(-0500)] <Bosmon4> But it is not sensible to try to fix it before the pilot
[14:12:45 EST(-0500)] <colinclark> Bosmon4: Remind me of the error?
[14:12:53 EST(-0500)] <Bosmon4> Well, I didn't explain what it was yet
[14:13:09 EST(-0500)] <Bosmon4> But it explains the phenomenona, I think from Yura's JIRA ENGAGE-214 (not sure about the number)
[14:13:37 EST(-0500)] <Bosmon4> THe problem is that when mounting filesystem resources, if the acceptor reports the resource is not found, this does not actually terminate the acceptor chain
[14:13:52 EST(-0500)] <Bosmon4> It then goes on to anything at the next directory level... which seems to often include the SAME acceptor again
[14:14:07 EST(-0500)] <Bosmon4> And so actually a mounted file will be found at any of the "shortened" versions of the path it is mounted at
[14:14:13 EST(-0500)] <Bosmon4> As well as at the single intended path
[14:14:26 EST(-0500)] <Bosmon4> I was baffled for a long time when he talked about the "fallback" behaviour
[14:14:33 EST(-0500)] <Bosmon4> Since I couldn't see anywhere where this was implemented
[14:14:46 EST(-0500)] <Bosmon4> But in fact it is "implemented" as a sideeffect of the acceptor search algorithm
[14:14:48 EST(-0500)] <colinclark> Ah!
[14:14:55 EST(-0500)] <colinclark> Sveto, I think, stumbled across this issue today
[14:14:59 EST(-0500)] <colinclark> Mentioned it on the list
[14:15:13 EST(-0500)] <Bosmon4> This has already been improved "a bit" to have some kind of intelligent approach to 405s
[14:15:22 EST(-0500)] <colinclark> I had tweaked his object code entry service to be mounted at artifacts/codeEntry
[14:15:34 EST(-0500)] <colinclark> and it was walking the directory tree weirdly, he said
[14:15:36 EST(-0500)] <Bosmon4> Since you need to "pool up" a set of responses from all the acceptors at a particular path before you can finally decide you need to send a 405
[14:16:00 EST(-0500)] <Bosmon4> Basically if ANY acceptor declares it wants to return a 405, and none of them has decided on an "accept", THEN a 405 is the right thing
[14:16:18 EST(-0500)] <Bosmon4> And this kind of "non-local acceptance" is something we need a bit more of, to deal with this unhelpful "fallback" behaviour
[14:17:03 EST(-0500)] <Bosmon4> A failure to meet acceptance in a file-mounted URL space should lead to a 404 immediately....
[14:17:12 EST(-0500)] <Bosmon4> OK, boarding now - see you in a couple of hours
[14:29:51 EST(-0500)] * Bosmon5 (~AndChat@245.sub-97-27-145.myvzw.com) has joined #fluid-work
[14:30:15 EST(-0500)] <Bosmon5> DROIDDD
[14:34:16 EST(-0500)] * EverettZ (~chatzilla@bas4-toronto06-1279277691.dsl.bell.ca) has joined #fluid-work
[14:34:42 EST(-0500)] <EverettZ> colinclark: anything that I can do to help you guys out this afternoon?
[14:35:59 EST(-0500)] <colinclark> EverettZ: Another cruise through the Engage 0.3 app would be of great help.
[14:36:17 EST(-0500)] <colinclark> EverettZ: It's not quite fully integrated yet, but we've got several new screens in place
[14:36:50 EST(-0500)] <colinclark> EverettZ: Would love your feedback. Bug parade starts tomorrow, so we probably haven't squashed many of the issues you reported last time yet, but still, it'd be good to get your thoughts.
[14:37:16 EST(-0500)] <EverettZ> colinclark: should I be looking at, or for, anything in particular?
[14:37:19 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[14:37:52 EST(-0500)] <colinclark> EverettZ: The navigation bar is new, so I'd be curious to hear how that is. The Home Screen and Language Selection pages are new as well.
[14:38:25 EST(-0500)] <colinclark> EverettZ: You'll find a couple of dead ends: object code isn't quite implemented (I've just got to commit a patch to fix it) and the Artifact View page itself is in shambles a bit
[14:39:18 EST(-0500)] <EverettZ> colinclark: I'll take a look this afternoon.
[14:39:29 EST(-0500)] <colinclark> EverettZ: You rule. Thanks so much!
[14:39:48 EST(-0500)] <EverettZ> colinclark: I actually enjoy it, no altruism here, lol
[14:40:01 EST(-0500)] <colinclark> EverettZ: If you find yourself with more time later in the week, I think we'll have the app nicely integrated and will be in the midst of squashing bugs. So it'll be hugely helpful to hear from you then.
[14:41:34 EST(-0500)] <EverettZ> colinclark: I'll see how things look later in the week, should be a bit of time. I'll likely still be waiting for Xcode to download then... very very slow.
[14:41:56 EST(-0500)] <colinclark> EverettZ: Yep, it can be pretty slow. Are you doing some Cocoa development?
[14:42:19 EST(-0500)] <EverettZ> colinclark: Xcode 3.2 is the first theoretically completely accessible version, even interface builder is suppose to be accessible with VO.
[14:42:33 EST(-0500)] <colinclark> EverettZ: Ah, I hadn't heard that! Even Interface Builder?
[14:43:08 EST(-0500)] <EverettZ> colinclark: Well, I'm trusting Marco Zehe who claims interface builder is accessible, if not difficult to use, with VoiceOver.
[16:06:19 EST(-0500)] <jessm> colinclark: should we consider listing only parent jiras and taking the kids off the parade?
[16:06:43 EST(-0500)] <colinclark> jessm: I think, in general, it may be time for the kids to leave the nest
[16:07:03 EST(-0500)] <colinclark> Our goal here, ideally, is to ensure that each issue on the bug parade is clear and fine-grained. Something someone can do and then check off the list
[16:12:47 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[16:30:38 EST(-0500)] <jessm> colinclark: are justin_o and yura going to join?
[16:30:43 EST(-0500)] <colinclark> they are
[16:30:53 EST(-0500)] <colinclark> on their way
[16:30:57 EST(-0500)] <jessm> great
[16:31:13 EST(-0500)] <colinclark> I just have one my issue to file, and then My Collection's issues will be looking shiny for bug parade.
[16:31:28 EST(-0500)] <jessm> awesome
[16:31:28 EST(-0500)] <yura> colinclark: jessm hi everyone
[16:31:51 EST(-0500)] <jessm> hey there, you're here, but invisible!
[16:31:52 EST(-0500)] <jessm> tricky
[16:31:54 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[16:32:14 EST(-0500)] <jessm> colinclark: does it make the most sense to sort by components?
[16:32:23 EST(-0500)] <jessm> and then go through systematically?
[16:32:28 EST(-0500)] <colinclark> jessm: Probably, yes
[16:32:31 EST(-0500)] <jessm> k
[16:32:56 EST(-0500)] <jessm> everyone here? http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10128
[16:33:23 EST(-0500)] <jessm> so, first thing I see is we can take the kids off bug parade and put parents only – does that sound ok?
[16:33:31 EST(-0500)] <jessm> colinclark: yura justin_o ^
[16:33:59 EST(-0500)] <justin_o> jessm: maybe the reverse
[16:34:00 EST(-0500)] <colinclark> jessm: gimme one second
[16:35:16 EST(-0500)] <colinclark> ok, i'm ready
[16:35:41 EST(-0500)] <colinclark> So jessm, I just completely reworked the list of My Collection issues
[16:35:54 EST(-0500)] <colinclark> I'm not sure if they're in your list, though I did add them to the Bug Parade Engage 0.3 filter
[16:35:55 EST(-0500)] <colinclark> I think
[16:35:57 EST(-0500)] <colinclark>
[16:36:15 EST(-0500)] <jessm> k, so seems like three things that smell like housekeeping need to happen
[16:36:22 EST(-0500)] <jessm> and unfortunately i can't do them (yet)
[16:36:36 EST(-0500)] <jessm> 1. issues that are bug paradable need to be tagged with bug parade
[16:36:55 EST(-0500)] <jessm> 2. issues that are irrelevant need to be taken off bug parade and replaced by more meaningful ones
[16:37:12 EST(-0500)] <jessm> with a level of detail
[16:37:28 EST(-0500)] <jessm> 3. i don't know that i have a 3
[16:37:40 EST(-0500)] <jessm> yura, justin_o colinclark can we do that by end of day today?
[16:38:04 EST(-0500)] <jessm> the hope is we'll get through phase 1 of bug parade by wed – and i'd like to send out an email with the phase 1 on it including:
[16:38:37 EST(-0500)] <jessm> 1. Integrate My Collection
[16:38:37 EST(-0500)] <jessm> 2. Update Artifact View to match the latest wireframes
[16:38:38 EST(-0500)] <jessm> 3. Implement and integrate Guest book 4. Hook Object Entry up with database
[16:38:41 EST(-0500)] <colinclark> jessm: Yep, that's sounds about right.
[16:38:50 EST(-0500)] <colinclark> I've tried to do this in the specific for My Collection
[16:39:16 EST(-0500)] <jessm> ah, #3 is a priority level...
[16:39:20 EST(-0500)] <colinclark> http://issues.fluidproject.org/secure/IssueNavigator.jspa?reset=true&amp;mode=hide&amp;pid=10020&amp;sorter/order=DESC&amp;sorter/field=priority&amp;resolution=-1&amp;component=10142
[16:39:49 EST(-0500)] <jessm> so, we're going to be doing a 3-part bug parade: phase 1 is big ticket items (the 4 listed above), phase 2 is styling, and phase 3 is bugginess
[16:39:51 EST(-0500)] <colinclark> Yura and I talked through Artifact View. I believe everything you had on the list for it is correct
[16:39:57 EST(-0500)] <jessm> ah, ok
[16:40:18 EST(-0500)] <jessm> for priority within the phases we'll be using the blocker, critical, major designations in jira
[16:40:35 EST(-0500)] <jessm> james and tona are going to help prioritize phase 2, styling issues
[16:40:56 EST(-0500)] <jessm> colinclark: are you translating me locally or is this making sense globally?
[16:41:08 EST(-0500)] <colinclark> Wait, I thought phase 2 was Interaction/Behavioural bugs and Phase 3 is Styling.
[16:41:10 EST(-0500)] <colinclark> Am I just confused?
[16:41:20 EST(-0500)] <jessm> ah, ok, i might have been confused
[16:41:27 EST(-0500)] <colinclark> I'm not translating... they're still reading
[16:41:32 EST(-0500)] <jessm> i thought by wed we'd be done with phase 1 and then onto phase 2
[16:41:36 EST(-0500)] <colinclark> Actually, I'm ordering them to agree.
[16:41:39 EST(-0500)] <colinclark>
[16:41:48 EST(-0500)] <jessm> nice!
[16:41:51 EST(-0500)] <justin_o> jessm: sorry... i was taking a long time reading
[16:41:57 EST(-0500)] <justin_o> but i agree with the process
[16:41:58 EST(-0500)] <jessm> justin_o: no worries
[16:41:59 EST(-0500)] <yura> yes, agreed with Colin
[16:42:02 EST(-0500)] <jessm> oh good!
[16:42:04 EST(-0500)] <colinclark> very credible, huh?
[16:42:05 EST(-0500)] <colinclark>
[16:42:40 EST(-0500)] <jessm> ok, 3 phases, 3 priorities within those phases, do some gardening tonight so that we can start fresh tomorrow a.m. and i can send out a parade email with the phase 1 bugs in it
[16:42:44 EST(-0500)] <jessm> that's my summation!
[16:43:13 EST(-0500)] <colinclark> So, in short...
[16:43:28 EST(-0500)] <colinclark> By early tomorrow morning, we want to go through each of the major components
[16:43:47 EST(-0500)] <colinclark> And ensure that there are clear, fine-grained tasks that someone can easily do and then check off their list...
[16:43:55 EST(-0500)] <colinclark> all filed in JIRA for the Phase 1 tasks
[16:43:57 EST(-0500)] <colinclark> Right, jessm?
[16:44:05 EST(-0500)] <jessm> colinclark: roger that colonel
[16:44:09 EST(-0500)] <colinclark> lol
[16:44:19 EST(-0500)] <colinclark> So I think My Collection is done
[16:44:34 EST(-0500)] <colinclark> yura, can you double check the priority for your Artifact View issues?
[16:44:41 EST(-0500)] <colinclark> They should essentially all be blockers, I think
[16:44:56 EST(-0500)] <jessm> justin_o: can you update the 283 family?
[16:45:16 EST(-0500)] <justin_o> jessm: sure, can do
[16:45:19 EST(-0500)] <jessm> and we don't seem to have any tasks for the Guestbook
[16:45:26 EST(-0500)] <yura> colinclark: i will go through the artifact view issues
[16:45:37 EST(-0500)] <justin_o> so just a bit of clarification, are we organizing all 1, 2, 3 type issues now
[16:45:37 EST(-0500)] <colinclark> jessm: I think for now we can probably file a handful of issues for Boz
[16:45:55 EST(-0500)] <jessm> colinclark: exhibitions isn't in Phase 1 but it has a ton of tasks, what should we do about that?
[16:46:07 EST(-0500)] <jessm> are they mostly phase 3?
[16:46:45 EST(-0500)] <colinclark> Exhibitions probably should be only in phase 2 and 3
[16:46:52 EST(-0500)] <colinclark> I think justin_o may know of one that needs to be a phase 1
[16:47:05 EST(-0500)] <colinclark> justin_o: The one about the Exhibition Browse data spout?
[16:47:20 EST(-0500)] <jessm> so, it does feel like we've got to spend a bit of time going through these...
[16:47:31 EST(-0500)] <justin_o> colinclark, jessm: yes, that one has to do with the way the spout is resolving the location of the message bundle
[16:47:36 EST(-0500)] <justin_o> so it break i18n
[16:47:54 EST(-0500)] <colinclark> jessm: If there are blatant "this doesn't do what it should" issues under Exhibitions-or anywhere else-they should percolate at least up to Phase 2, if not Phase 1
[16:48:03 EST(-0500)] <colinclark> jessm: yes, re: a lot of time
[16:48:10 EST(-0500)] <colinclark> I think it's the nature of this kind of bug parade
[16:48:20 EST(-0500)] <colinclark> We've got tons of issues, all at varying levels of detail
[16:48:23 EST(-0500)] <colinclark> and some are pretty crusty
[16:48:34 EST(-0500)] <colinclark> We're all here to help with the workload
[16:48:49 EST(-0500)] <jessm> once we get phase 1 under control we'll be well on our way
[16:49:02 EST(-0500)] <colinclark> makes sense
[16:49:18 EST(-0500)] <colinclark> justin_o: So you'll file that i18n issue in the right spot
[16:49:24 EST(-0500)] <colinclark> Phase 1 is Blocker
[16:49:46 EST(-0500)] <justin_o> colinclark: sounds like it
[16:50:51 EST(-0500)] <colinclark> what else, jessm?
[16:51:03 EST(-0500)] <colinclark> I'll tweak object code entry's list, too
[16:51:40 EST(-0500)] <jessm> if it's phase 1 we've got to have a good jira representation of it today/first thing tomorrow
[16:52:21 EST(-0500)] <jessm> yura, justin_o colinclark i think that's it from me – is it clear what we're doing?
[16:53:01 EST(-0500)] <jessm> jameswy: you're going to file jiras with names that start with something like "styling in..." so it's clear that they're a phase 3 bug
[16:53:10 EST(-0500)] <justin_o> jessm: yep... i'm starting in on fixing up the 283 set of jiras now
[16:53:19 EST(-0500)] <jameswy> jessm: Correct.
[16:53:23 EST(-0500)] <jessm> great!
[16:53:23 EST(-0500)] <jessm> thanks guys
[16:53:28 EST(-0500)] <colinclark> jessm: You rule!
[16:53:31 EST(-0500)] <justin_o> jessm: thank you
[16:53:32 EST(-0500)] <yura> jessm: yes, i m going through the artifact view
[16:53:37 EST(-0500)] <jessm> sweet
[16:53:38 EST(-0500)] <colinclark> there's so much here, and you're making sense of it all!
[16:53:55 EST(-0500)] <jessm> my rule is short-lived and sour, but we'll make it through!
[16:54:22 EST(-0500)] <jessm> then we can check in tomorrow a.m. in the channel about who is doing what
[16:57:02 EST(-0500)] <colinclark> short-lived and sour!
[16:57:04 EST(-0500)] <colinclark> sweet!
[17:08:07 EST(-0500)] <colinclark> jessm: I've filed a handful of subtasks for the performance issue
[17:08:12 EST(-0500)] <colinclark> I'm not quite sure what to do with them.
[17:08:31 EST(-0500)] <jessm> colinclark: i figured you would put your ideas in there
[17:08:49 EST(-0500)] <colinclark> I just haven't had time to think about the best plan of attack. In the meantime, I guess the umbrella issue can stay as the blocker on Bug Parade
[17:08:50 EST(-0500)] <colinclark> http://issues.fluidproject.org/browse/ENGAGE-342
[17:09:34 EST(-0500)] <jessm> colinclark: nice
[17:09:43 EST(-0500)] <colinclark> jessm: Any chance you could sort the Bug Parade 0.3 filter by Priority?
[17:09:54 EST(-0500)] <colinclark> in JIRA, I mean.
[17:10:54 EST(-0500)] <jessm> surely
[17:11:00 EST(-0500)] <colinclark> Thanks, boss
[17:13:33 EST(-0500)] <jessm> colinclark: take that back, looks like justin_o needs to save it as sorted by priority
[17:13:42 EST(-0500)] <colinclark> yack
[17:13:44 EST(-0500)] <colinclark> justin_o: ^
[17:13:46 EST(-0500)] <jessm> justin_o: can you do that to bug parade all or give me perms to do that?
[17:14:17 EST(-0500)] <justin_o> jessm: sure i can do it... i have no idea how to give perms to specific filters
[17:14:52 EST(-0500)] <jessm> justin_o: nor do i!
[17:17:35 EST(-0500)] <justin_o> jessm: just so you know... this is the filter for only the open isssues... which may be helpful once we start knocking some of them off http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10129
[17:18:11 EST(-0500)] <jessm> justin_o: thanks, i noticed that one – a testament to your kingliness
[17:18:21 EST(-0500)] <justin_o>
[17:19:24 EST(-0500)] * clown_afk (~clown@142.150.154.101) has left #fluid-work
[17:27:46 EST(-0500)] <colinclark> jessm: I've filed a handful of Comments related issues for Boz. That should be done.
[17:27:54 EST(-0500)] <colinclark> Similarly, object entry issues are filed for Sveto
[17:27:56 EST(-0500)] <jessm> great
[17:28:01 EST(-0500)] <colinclark> I'm gonna take one more pass through My Collection
[17:28:07 EST(-0500)] <jessm> yura, justin_o just so you know there's now a "comments" component
[17:28:28 EST(-0500)] <jessm> colinclark: should we have a more hands-on approach to dealing with Guestbook?
[17:28:34 EST(-0500)] <jessm> what can we do there?
[17:29:13 EST(-0500)] <yura> jessm: thanks
[17:29:14 EST(-0500)] <colinclark> in JIRA, that is
[17:29:26 EST(-0500)] <colinclark> jessm: Hands on in terms of ensuring it gets done?
[17:30:35 EST(-0500)] <jessm> colinclark: do we have any bugs filed against it?
[17:30:58 EST(-0500)] * Bosmon5 (~AndChat@207.sub-97-151-153.myvzw.com) has joined #fluid-work
[17:31:23 EST(-0500)] <colinclark> Ah, I see
[17:31:33 EST(-0500)] <colinclark> Look, the fifth incarnation of Bosmon has arrived!
[17:31:37 EST(-0500)] <colinclark> jessm: I'll check
[17:31:50 EST(-0500)] <colinclark> I had just done a search in JIRA for "guestbook" and didn't stumble across anything notable
[17:31:54 EST(-0500)] <colinclark> but let me take a look
[17:34:49 EST(-0500)] <Bosmon5> Each incarnation smaller than the last
[17:35:01 EST(-0500)] <colinclark>
[17:35:12 EST(-0500)] <colinclark> And younger, like the Doctor?
[17:35:28 EST(-0500)] <Bosmon5> You are looking for some Goosebook-related thing?
[17:35:31 EST(-0500)] <Bosmon5> If only...
[17:38:34 EST(-0500)] <colinclark> Bosmon5: Mostly we're just filing JIRA issues wildly
[17:38:42 EST(-0500)] <colinclark> I'm corralling all Goosebook and Comments related issues for you
[17:38:55 EST(-0500)] <Bosmon5> Ok
[17:39:18 EST(-0500)] <jessm> colinclark: the priority reflects the phase 1 bugs?
[17:39:33 EST(-0500)] <jessm> no, i see they're overall priority
[17:39:59 EST(-0500)] <Bosmon5> Let me know of any Goosey Gander ones
[17:39:59 EST(-0500)] <Bosmon5> Cheers
[17:41:12 EST(-0500)] <colinclark> Bosmon5: At the moment they're super general. Basically just "build a Comments component" and "integrate it with Exhibitions and Artifacts"
[17:41:27 EST(-0500)] <Bosmon5> Yes
[17:41:38 EST(-0500)] <colinclark> I'll leave you to file more specific issues as the come up. But since we're in Bug Parade time, having a slightly general set of JIRAs is probably in your favour.
[17:41:49 EST(-0500)] <colinclark> jessm: yep. Blockers are phase 1
[17:42:02 EST(-0500)] <justin_o> jessm: The 283 family of jiras has been touched up
[17:42:04 EST(-0500)] <jessm> colinclark: but that's mixed in with other blockers, that's fine
[17:42:12 EST(-0500)] <jessm> justin_o: thanks much
[17:42:16 EST(-0500)] <colinclark> jessm: Huh?
[17:42:19 EST(-0500)] <colinclark> Sorry, I'm confused
[17:42:25 EST(-0500)] <Bosmon5> Well, I guess until there is any testable functionality, it will be harder to have more specific JIRAs
[17:42:31 EST(-0500)] <jessm> the readme is not a phase 1, is it?
[17:43:23 EST(-0500)] <justin_o> jessm: it probably is a blocker but we'll have more time to get to it
[17:43:40 EST(-0500)] <jessm> justin_o: yes, it is a blocker for sure
[17:43:54 EST(-0500)] <jessm> just trying to say, those things that are blockers are not all phase 1
[17:44:23 EST(-0500)] <jessm> in other words, searching for blockers isn't going to reveal the phase 1 stuff
[17:45:21 EST(-0500)] <justin_o> jessm: actually for the pilot we may not have a readme
[17:46:10 EST(-0500)] <justin_o> jessm: also did you want me to try to change the version name from 0.3 to 0.3 beta or something
[17:46:11 EST(-0500)] <justin_o> like that
[17:46:34 EST(-0500)] <jessm> justin_o: yes, actually i was calling it 0.3b in the email i haven't sent out yet
[17:46:43 EST(-0500)] <jessm> and no readme sounds fine too
[17:46:59 EST(-0500)] <justin_o> jessm: okay... i'll try to change it without breaking everything
[17:47:09 EST(-0500)] <jessm> justin_o: much appreciated
[17:47:12 EST(-0500)] <colinclark> 0.3b sounds great
[17:47:37 EST(-0500)] <Bosmon5> Date? Monday?
[17:47:47 EST(-0500)] <justin_o> jessm: it should all be updated in jira to 0.3b now
[17:48:01 EST(-0500)] <jessm> yay, thanks guys
[17:48:33 EST(-0500)] <colinclark> jessm, Bosmon5: All comments and guest book related stuff has been consolidated down to three JIRAs now
[17:48:43 EST(-0500)] <colinclark> Bosmon5: Date?
[17:48:49 EST(-0500)] <Bosmon5> Cool, thanks
[17:48:59 EST(-0500)] <Bosmon5> For 0.3b
[17:49:11 EST(-0500)] <jessm> 15th
[17:49:12 EST(-0500)] <colinclark> Ah. Bug parade starts tomorrow.
[17:49:16 EST(-0500)] <colinclark> QA next week
[17:49:39 EST(-0500)] <colinclark> Bosmon5: We won't actually ship a release artifact for the beta, except to Hugues
[17:49:48 EST(-0500)] <Bosmon5> Ok
[17:49:49 EST(-0500)] <colinclark> So this is a "soft" release; super-informal
[17:50:06 EST(-0500)] <Bosmon5> Which is Pilot Day?
[17:50:08 EST(-0500)] <colinclark> As soon as Hugues is happy, we'll cycle back around to get rid of anything that was hard-baked for McCord
[17:50:21 EST(-0500)] <colinclark> And do a formal release of Engage 0.3 final
[17:50:32 EST(-0500)] <colinclark> Bosmon5: Hugues iPod touches arrive on the 15th
[17:50:45 EST(-0500)] <colinclark> User testing and evaluation starts in earnest on the 22nd
[17:50:48 EST(-0500)] <colinclark> Here we go!
[17:53:22 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[17:55:48 EST(-0500)] <colinclark> Really nice feedback from Everett on list... he took a tour through today's daily
[17:57:56 EST(-0500)] <justin_o> colinclark, jessm: i've added back in a 0.3 version (for our 0.3 final) i'll move the readme to that one
[17:58:00 EST(-0500)] <justin_o> does that seam reasonable
[17:58:07 EST(-0500)] <colinclark> justin_o: Makes sense
[17:58:27 EST(-0500)] <jessm> justin_o: perfect
[17:59:11 EST(-0500)] <jessm> thanks guys, i'll have to catch back up after a dog walk...
[17:59:18 EST(-0500)] <colinclark> jessm: So I'm cool on the My Collection JIRAs
[17:59:22 EST(-0500)] <colinclark> and am going back to code now
[17:59:25 EST(-0500)] <colinclark> have a good walk
[17:59:35 EST(-0500)] <jessm> colinclark: thanks for doign all that jira madness
[18:03:31 EST(-0500)] * anastasiac (~team@142.150.154.193) has left #fluid-work
[18:19:30 EST(-0500)] * elicochran (~elicochra@dhcp-169-229-212-70.LIPS.Berkeley.EDU) has joined #fluid-work
[21:43:18 EST(-0500)] * yura (~yura@bas3-toronto06-2925097429.dsl.bell.ca) has joined #fluid-work