You have just entered room "Chat 32815820260972796367."
Abhi327 has entered the room.
x V DoGG x: hey abhi
Abhi327: hi vivek.
x V DoGG x: after looking at your ui class diagram in more detail
x V DoGG x: it seems pretty complete
Abhi327: cool.
x V DoGG x: i was hoping to put together some stub code and comment up each of the classes for todays meeting, so i would have some java docs up on the web.... didn't get around to that though... soon
Abhi327: vivek
Abhi327: let me know when & kabe want to get together
Abhi327: so that we can work out our interface
Abhi327: it should be very simple
x V DoGG x: yeah
Abhi327: vivek, i have a question
Abhi327: you need to refresh my memory
x V DoGG x: sure
Abhi327: do we have a tracker ?
x V DoGG x: hmm, i am sure we assigned one
x V DoGG x: a while ago
x V DoGG x: back when we were XP
x V DoGG x: lemme check the logs
Abhi327: i checked the roles from the logs once we moved to RUP
x V DoGG x: yep
Abhi327: but no tracker there
x V DoGG x: we did back on 10/7/2002
x V DoGG x: it was Isaac & Dave
x V DoGG x: i can assume the tracker role now
x V DoGG x: since the use case responsiblitiy
x V DoGG x: is pretty much done
x V DoGG x: as far as i can tell
Abhi327: that would be great. that is what i had in mind:-)
x V DoGG x: not much "customer" or "use case" work should be done after this point in RUP, right?
Abhi327: unless we get new use cases. but yeah as long as our use cases are specified for the timebeing. we are ok.
x V DoGG x: i will go back and put it on that page and make note we decided today
Abhi327: thanks.
x V DoGG x: abhi - is the "blue diagram" supposed to be the services layer?
Abhi327: We also need to define the role of a Doc. Mgr for the project. He'll be responsible for posting doc., logs, whatever doc. we come up with.
Abhi327: yes that is the services layer.
Abhi327: i put that in our agenda for tonight
Abhi327: let me add u to our developers list.
Abhi327: i'll add you as the designated tracker.
Eceguru has entered the room.
kabev1 has entered the room.
x V DoGG x: ok
kabev1: Hey all
Eceguru: hi
x V DoGG x: hey whats up
starkiller76 has entered the room.
kabev1: I must apologize for life's inconvienences, I wasn't able to do the CM stuff due to a family emergency
starkiller76: no prob
Abhi327: no problem kave.
Eceguru: that's ok, let's wait a few minutes for anyone else to join
x V DoGG x: abhi and i were just talking and we realized after we reassigned roles, we didn't have a tracker... so i volunteered, since my responsibility as the "system analyst" - use case specifier is pretty much completed
Eceguru: ok
Abhi327: vivek
Abhi327: i added u to the developers list
Abhi327: check if you can see urself added to the project
kabev1: Abhi, can u send me that CM stuff?
Abhi327: yes kabe
kabev1: Thanks
sudigh has entered the room.
Abhi327: guys i have a long distance call from my parents. i'll be back in 5 minutes.
Abhi327: i've added everyone who sent me their sourceforge id.
sudigh: hello
Abhi327: to our project
x V DoGG x: yep i see me
kabev1: Hey what's the dns?
x V DoGG x: dns?
kabev1: sorry, of the project
kabev1: urlo
kabev1: url
x V DoGG x: http://sourceforge.net/project/memberlist.php?group_id=66492
kabev1: nah, the easy one
x V DoGG x: http://sourceforge.net/projects/linux-p2p-wifi
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Agenda-11-11-02
x V DoGG x: did i cover you?
x V DoGG x: he he :-)
x V DoGG x: i guess we can start
kabev1: What.sourceforge.net
x V DoGG x: abhi will get back with us later
x V DoGG x: #1 - make sure you send your sourceforge info to abhi
Eceguru: ok
x V DoGG x: looks like a few are still missing
Eceguru: yeah, i just sent him my login
x V DoGG x: #2 - Kabe was attending to a family emergency, so i assume we will wait to hear from him...
x V DoGG x: an eta?
kabev1: Correct
x V DoGG x: do we have an ETA?
sudigh: hwta is ETA ?
sudigh: hwta = what
x V DoGG x: since i am the newly designated "tracker" i guess i should get this info.....
x V DoGG x: when you will be done with it
x V DoGG x: a date
x V DoGG x: so i can put it down
x V DoGG x: basically when you will have posted a strategy, for us...
kabev1: Friday
x V DoGG x: cool
x V DoGG x: #3) Class diagrams: Lets start with the applications layer (UI): Vivek & Kabe
x V DoGG x: Well, the diagram that abhi had was pretty complete
x V DoGG x: as i was telling him earlier.....
x V DoGG x: so kabe and i are planning to put up some stub code for the UI
x V DoGG x: and define its' interface in javadoc format
x V DoGG x: so everyone can browse the web
x V DoGG x: and see their associated calls....
x V DoGG x: we should be able to get this up by tuesday or wed....
Eceguru: sounds good
x V DoGG x: and we can begin discussions from there
x V DoGG x: on negotiating what doesn't fit together correctly
kabev1: Side question... Should we always plan on Wed. meetings as well as Mon
x V DoGG x: hmmm, the semester is winding down
x V DoGG x: i think that is a good idea
Eceguru: think we'll need them
x V DoGG x: short and sweet
Eceguru: we don't have much time and we had a slow start
kabev1: Mon are most important but Wed are good for updates
x V DoGG x: like i plan to run this one as.....
kabev1: ok so let's just plan on Mon and wed,
kabev1: continue
x V DoGG x: that was in terms of "short"
x V DoGG x: lets plan for 2 half hour meetings.... instead of one long 1.5 hour one....
Eceguru: ok
starkiller76: ok
Eceguru: lets keep moving then
x V DoGG x: ok
x V DoGG x: next one
x V DoGG x: core layer update:
x V DoGG x: david, isaac and sudipta
sudigh: I'll get something up on Wed
x V DoGG x: ok
Eceguru: dave, you want to discuss what you setup?
x V DoGG x: an api?
sudigh: I'm in the process.
sudigh: No, class diag
x V DoGG x: ok
x V DoGG x: that one isn't covered in the abhi docs, right?
sudigh: yes\
x V DoGG x: or is it?
x V DoGG x: what is considered "core layer"?
sudigh: no, it is not covered by Abhishek
x V DoGG x: just curious
Abhi327: i am back.
sudigh: The protocol layer basically
x V DoGG x: ok..... so you will mainly interface with the services layer?
sudigh: deals with peer discovery etc ..
starkiller76: I have set up a wireless network at home
sudigh: yes
x V DoGG x: and the services layer will interface directly with the UI
sudigh: core layer has no interfaces with UI.
Abhi327: the way i had it distributed, the core layer is ur basic underlying protocol layer.
starkiller76: I have tested the peer discovery with JXTA as well as group creation and discovery
x V DoGG x: sweet
Abhi327: cool.
x V DoGG x: ok.....
x V DoGG x: so we can move to the "services layer"
x V DoGG x: abhi & kevin:
x V DoGG x: abhi - we are taking status on eachitem
Abhi327: i am working on a more detailed class diagram for services.
Abhi327: myself and kevin need to
Abhi327: get together and finalize it.
Abhi327: we can then present it to the group.
Abhi327: yes that was the idea. to kinda summarize where we are
x V DoGG x: ok
x V DoGG x: abhi - kabe & i plan to have a draft api with java docs up by wed.
x V DoGG x: we can setup a meeting for friday if that works for you or during the day on thursday
Eceguru: dave was able to get two computers running jxta to discover each other
x V DoGG x: kabe - what works for you?
Eceguru: didn't really seem to matter that it was wireless or running linux at all
x V DoGG x: makes sense! it is java and ethernet
Eceguru: yup
x V DoGG x: as far as the application is concerned, OS and network independant
starkiller76: no it should compile fine on any O/S that supporths JVM
starkiller76: I mean yes
Abhi327: that is good news.
x V DoGG x: but, the question is that do we want to support browsing files on files restrainted by physical location
x V DoGG x: ???
Abhi327: i am not sure what the question is ?
x V DoGG x: basically, does it matter if you can get to files on a computer that is wirelessly linked to the internet on the otherside of the world?
kabev1: My understanding is we are interested in Adhoc
x V DoGG x: exactly.....
sudigh: lets just stick to browsing within a peer group.
starkiller76: there is code in the CM service that allows you to specify what directories to sharew
starkiller76: sharew=share
x V DoGG x: essentially that implies that isaac's solution may need to be extended to make sure we are 'only' searching peer groups located physically on the same wifi network (ie. same essid) vs. on any accessible network
starkiller76: I have not been able to get that to work
starkiller76: JXTA is really setup to use rendevous peers, that relay requests
Abhi327: if ur implementing a policy whereby letting only the peergroup members participate in file sharing, does it matter what the physical location is ?
starkiller76: no
Eceguru: i think we can address limiting access later and just concentrate on getting more of the application level running
Abhi327: i agree with issac.
starkiller76: so do i
x V DoGG x: ok
Eceguru: i'm just wondering what we have to do at the protocol lever
Eceguru: level
starkiller76: nothing
x V DoGG x: ok
x V DoGG x: next item
x V DoGG x: #4
sudigh: The protocol level seems pretty much borrowing from jxta right ?
Eceguru: yes
starkiller76: right
x V DoGG x: are there any doc changes so far that need to be discussed?
Abhi327: any changes to project plan, requirements doc.
Abhi327: if anyone
x V DoGG x: did someone update our project plan?
x V DoGG x: i haven't looked
starkiller76: Sudipta and I will be creating a more detailed iteration plan soon.
x V DoGG x: i know we did assign that job
x V DoGG x: ok
sudigh: We can put up the class diags on our project site.
Abhi327: yes
Abhi327: i am starting to use a tool
Eceguru: how are the requirements doc coming
Abhi327: to draw class diagrams.
x V DoGG x: It would be nice to follow the java doc strategy to make sure that we have access to each other's interfacews
sudigh: what tool is it Abhishek ?
x V DoGG x: who was in crage of requirements?
Abhi327: if u have changes, please let me know.
Abhi327: kevin.
x V DoGG x: crage = charge
Abhi327: agro UML.
Abhi327: he is not here.
Abhi327: i'll shoot off an email to him. i need to talk to him about the services layer as well.
x V DoGG x: ok
x V DoGG x: then we can move to #5
Abhi327: we need to
Abhi327: have a doc. manager.
Abhi327: i think thats #5 on the agenda
Abhi327: sorry vivek, go ahead.
x V DoGG x: cool
x V DoGG x: yes
x V DoGG x: i believe you had some recommendations
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Summary-10-28-02
x V DoGG x: there are some people who don't have any responsibilities
Abhi327: the link basically talks about the
Abhi327: services offered by sourceforge
x V DoGG x: perhaps we should start assign them some....
Abhi327: yes we definitely need someone to maintain our documentation.
x V DoGG x: i htink that leaves kevin, issac, and guru
x V DoGG x: any volunteers or did i miss someone
Abhi327: guru has volunteered
x V DoGG x: ?
x V DoGG x: ok
Eceguru: ok
x V DoGG x: cool
Abhi327: to serve as a project admin
Eceguru: i was going to work on test documentation
Eceguru: and bug tracking
Abhi327: yes.
x V DoGG x: ok
x V DoGG x: lemme add you to the official list
sudigh: what are we using for bug tracking ?
Abhi327: issac, vivek, how do you guys want to split up the tracking responsibilities. it seems like both of you will be performing tracking
Abhi327: bugzilla i belive
Abhi327: or a part of the tracking.
Eceguru: vivek will be doing more project tracking
sudigh: ok
x V DoGG x: yeah, that is what i assumed
Abhi327: cool. vivek can you make that explicit.
starkiller76: wait
Eceguru: i just want to focus on the defect tracking and maybe summarize some root cause analysis for doc purposes
starkiller76: Sudipta and I are project managers
x V DoGG x: sure
starkiller76: we do project tracking
sudigh: we set the milestones in the project plan.
sudigh: Dave and I
x V DoGG x: that makes sense
x V DoGG x: upon abhi's comment earlier i was assuming that you would set the schedule and i would monitor and track everyone's progress relative to the plan that you set forth to balance the load across everyone
starkiller76: yes
Abhi327: there are also a bunch of things such as tasks, feature requests to track
sudigh: yes.
Abhi327: that is in addition to bug tracking and the project planning.
Abhi327: i was thinking vivek could track at a more lower level. the project manager is not going to worry too much about feature request tracking or tasks. Is that correct ?
sudigh: Vivek is our project lead sort of :-)
x V DoGG x: sure
x V DoGG x: ok.... so is everything taken care of then?
x V DoGG x: next meeting wed @ 8:30pm
x V DoGG x: summary will be up in a few minutes
Eceguru: ok
kabev1: cool
Abhi327: i'll ask kevin to head documentation manager role.
Abhi327: thanks vivek.
sudigh: and Isaac is our bug manager :-)
x V DoGG x: ok
x V DoGG x: cool
kabev1: out
x V DoGG x: i will put him up there as tentative
sudigh: anything else ?
x V DoGG x: everyone be ready to update progress and class diagrams on wed
sudigh: ok
x V DoGG x: we should have semi finalized class diagrams on wed
x V DoGG x: so we can move forward and begin coding this
x V DoGG x: application
Abhi327: yes
x V DoGG x: i would expect that we will have *some* stub code written by next monday
Eceguru: sounds good
x V DoGG x: interfaces should be finalized at the end of this week
Abhi327: sounds good.
x V DoGG x: at the latest
sudigh: I'll update the project plan with the latest done and to be done items.
x V DoGG x: cool
x V DoGG x: thanks
x V DoGG x: good bye
sudigh: good night and bye everybody.
Eceguru: bye all
Eceguru has left the room.
kabev1 has left the room.
Abhi327 has left the room.