You have just entered room "Chat 4235028133099437619."
x V DoGG x: shall we get started?
gorclon1: I haven't heard any mention of the paper in the lectures
x V DoGG x: ok
michaelwalsh327: definitley from last year; the comment was moved to the wiki in January, yes, but it was promoted from an earlier version (look at the hanges). The extension was granted in April, 2002.
x V DoGG x: dave won't be able to join us
x V DoGG x: shit... i don't know
Eceguru: i'm sure we can get the extra days since its cofusing
michaelwalsh327: I'd suggest planning to have it in on Thursday.
x V DoGG x: crapola
gorclon1: Which book you reading?
Eceguru: refactoring
x V DoGG x: microsoft secrets
x V DoGG x: agenda:
kabev1 has entered the room.
x V DoGG x: 1) Update from dave bown
michaelwalsh327: I'm doing refactoring; Isaac, you weren't doing that earlier in the semester...
Eceguru: yeah, i know
x V DoGG x: dave can't make it, but he called and gave me stuff he wanted to have mentioned
michaelwalsh327: did you get approval do double up within the roup? TOo late now, anyway. Souldn't be a big deal.
x V DoGG x: 2) Update from wed meeting
x V DoGG x: 3) task updates?
Eceguru: there are only like 5 books
michaelwalsh327: yea, I imagine it's fine.
Eceguru: we doubled up last semester without problem
Eceguru: doubt they care
salcs329: 4) I have question about integration of configinfo to main app/gui
kabev1: I am doing MS Secrets and so is Vivek
michaelwalsh327: Well, they do care, since they ask us not to do it, but again, too late now.
Eceguru: but the list of books is too small
gorclon1: I wouldn't worry about it at this point
kabev1: don't worry about it He's flexible.... let's get on witht the meeting
x V DoGG x: 1)
x V DoGG x: Danny update
x V DoGG x: he spoke with danny
x V DoGG x: it went well
x V DoGG x: he says that danny wasn't very concerned with documentation
michaelwalsh327: (til he bites us on the ass in May ;-))
x V DoGG x: but
x V DoGG x: he was very concerned with "focus on tests"
x V DoGG x: he was very concerned with "writing code"
x V DoGG x: and he wanted to see updates on the wiki
x V DoGG x: for what we are doing
x V DoGG x: and what is in progress
x V DoGG x: and we also need to get a current task list
x V DoGG x: he was really pushing to see a demo next week
x V DoGG x: but dave didn't promise anything
Eceguru: well, we're getting together this weekend to work right?
michaelwalsh327: (he's comin nextweek then?)
Eceguru: maybe we could have a demo ready after that
Eceguru: to demostrate what we have done
x V DoGG x: yes
x V DoGG x: yeah, but we haven't prmised anything
Eceguru: i agree, maybe we can see where we are after this weekend
Eceguru: to see what we can show him
Eceguru: did he say what lead time we need for the demo
Eceguru: like how much time we must give ahead of the demo
x V DoGG x: no
x V DoGG x: i don't think we have to
x V DoGG x: so i don't think we should mention anything
Eceguru: ok, he can't be too busy
x V DoGG x: until we are ready
x V DoGG x: ok
x V DoGG x: so
Eceguru: so a day or so should be fine
x V DoGG x: we need to assign people to start writing tests
Eceguru: so let's see after this weekend what we can see
Eceguru: what we can show i mean
x V DoGG x: and he wants to see everyone doing work every week
x V DoGG x: as far as the meeting on sunday
x V DoGG x: is everyone still on?
x V DoGG x: my cell is:
x V DoGG x: 847-514-2771
x V DoGG x: you should call it when you get here
x V DoGG x: if everyone arrives on time
michaelwalsh327: when did we schedule that meeting? I think this is the first I've heard of it.
gorclon1: ??
x V DoGG x: we won't have to make multiple trips (hike - 10 min)
x V DoGG x: to get to the door to let people in
x V DoGG x: it was during the last wed meeting
x V DoGG x: we were going together to integrate and solve the search problems
Eceguru: what time again?
x V DoGG x: all the folks on download/search
x V DoGG x: 5pm
michaelwalsh327: Why didn't you guys tell me about it?
x V DoGG x: mike - maybe it came up after you left
se2srini: not all right? vivek
x V DoGG x: i think we should try to all be in one room at once
x V DoGG x: all = download & search
x V DoGG x: that way we can get this thing done and moving
michaelwalsh327: yea, must have. Not sure; I'm thinking we'll hjave to devote a fair amoun of time to homework 4 this weekend.
Eceguru: i thought we discussed it in the meeting last wed.
x V DoGG x: yeah, i think mike dropped off
x V DoGG x: right at the end
michaelwalsh327: I can be available, but proally not there in person.
x V DoGG x: ok
kabev1: For those who cannot get to Mot, there are 2 phone lines to call into, and we should all be on IM as well
x V DoGG x: dave says that he is having issues integrating with your code mike
se2srini: ok so do u guys want me at 5PM online
x V DoGG x: primariliy because of his unfamiliarity
x V DoGG x: so you too will need to be together at some point
michaelwalsh327: ok
x V DoGG x: yes, that would be good
se2srini: ok
x V DoGG x: ok
x V DoGG x: ok
Eceguru: danny say anything else?
x V DoGG x: let me list the tasks that dave has identified for us
x V DoGG x: nope
x V DoGG x: 1) Integrate Search with Main Branch Code- Dave, Mike, Isaac
x V DoGG x: 2) Code Download (Manual and Automatic)- Vivek, Kabe, Srini
x V DoGG x: 3) Update WIKI to reflect our current project plan- any volunteers?? I can do it if no one else will. - should be able to use the updated project plan I have attached
x V DoGG x: 4) Fix any incompatibilities with the updated JXTA jar files (i.e. peer discovery, etc.) - Ryan
x V DoGG x: 5) Write Unit and System Tests a.) add more tests for search and download b.) combine our tests into one suite c.) make sure suite compiles and runs- anyone who has time, Download and Search guys will write their own unit tests
x V DoGG x: 6) User Config/XML Parser - Faisal
x V DoGG x: so any volunteers for #3
x V DoGG x: or #5
gorclon1: I can work on 3
michaelwalsh327: I don't think a single suiter is a great idea; maybe, though, an uber-suite that combines suites; this way individual sections can still be run in isolation.
salcs329: I have added a unit test to cvs for every class/file I have implemented so far
x V DoGG x: ok
x V DoGG x: perhaps we should follow that unit test model
x V DoGG x: and we can write some integration tests at the end?
x V DoGG x: isaac any progress with the test plan?
michaelwalsh327: I agree that they should be available as a unit, by the wya, I jut didn't think we should mash them all together into a single class.
Eceguru: nothing to report at this time
Eceguru: i agree with mike
x V DoGG x: me too
x V DoGG x: ok
x V DoGG x: well thats all for #1
x V DoGG x: any changes to the tasks dave has listed?
michaelwalsh327: I's like to append agenda item 5), Homework 4 pairings, only becaus eI don't think I have time to actually pair with anyone.
x V DoGG x: are we supposed to pair on this one?
x V DoGG x: i didn't see it in there
salcs329: pairing is optional..
x V DoGG x: ok
x V DoGG x: i am not sure i have time either.....
salcs329: I am going it alone on HW4
michaelwalsh327: well, that's good...as long as all 7 others weren't depnding on it. Those who want to pair up, feel free.
x V DoGG x: ok, well... i think we have covered most of the agenda... anything anyone wants to add?
michaelwalsh327: Sal had a question on integrating his stuff, I think.
salcs329: Yes..
salcs329: from where is the ConfigInfo object instantiated
salcs329: Is the gui for it complete..
x V DoGG x: did anyone complete it?
salcs329: who will be calling ConfigInfo.Save and ConfigINfo.Load
x V DoGG x: who is in charge of config stuff?
michaelwalsh327: assumed Sal was doig front-to-back config.
salcs329: I can work on the GUI part if it is not already done
x V DoGG x: yah it is sal listed
x V DoGG x: i thought it might have been someone else
x V DoGG x: sal - you are in charge of all of it
salcs329: Is it one of the panes on the main window
x V DoGG x: you can make it another tab
x V DoGG x: or whatever you want
salcs329: Is the configInfo object part of some main app object?
salcs329: i.e. where should it be instantiated
salcs329: I presume the app will read configinfo at startup
salcs329: Gui will update it when user wants to
salcs329: So where does the ConfigInfo object
salcs329: that gets updated at startup and gui save.. live
salcs329: I presume you will using it during search..
x V DoGG x: yeah, just add it to one of the classes
x V DoGG x: that is initially started
x V DoGG x: preferablly not in main
x V DoGG x: but that is fine too
salcs329: any preference to what class.. what c
salcs329: class is easily accessible to the search and other code
michaelwalsh327: Sal, I'd actually suggest having a separate Config class in the services package.
se2srini: after we are done with sals question, I've one about hw4
michaelwalsh327: with public methods; perhaps even static.
salcs329: Config class is a separate class.. it needs to be instantiated in one of the other class that lives while the app is running
salcs329: Config has state info that needs to retained... so it cannot only have static members.
michaelwalsh327: probably not awful if iut's created and used as needed; take a look in the code for seacrh within ServicesAPI; I believe it calls a dummy version of Config to get the local search directory.
salcs329: I will look around to find an appropriate location..
salcs329: I think I am done.. what's next
se2srini: HW4 says 4 teams should opt for this...is our team joining this proj?
michaelwalsh327: I don't intend to.
Eceguru: that's different than our teams
michaelwalsh327: but if there's someone in the group willing to join you, play on!
x V DoGG x: joining this proj?
x V DoGG x: huh?
Eceguru: he's looking for 4 teams to extand JMetrics
se2srini: this looks more like a team proj rather than an individual one
Eceguru: they don't have to do the regular homework
Eceguru: you need to know swing well it says
se2srini: yeah
michaelwalsh327: Don't think so, Srini, think it's teams of a couple/few people. Anyway, I don't have the Swing chops for it.
se2srini: I'm not a gui guy at all
se2srini: anyway looks like these teams are diff from ours
x V DoGG x: ok
x V DoGG x: anything else?
Eceguru: see you on sunday
se2srini: gd nt
michaelwalsh327: bye.
Eceguru: bye
michaelwalsh327 has left the room.
Eceguru has left the room.
salcs329: bye..
se2srini has left the room.
x V DoGG x has left the room.