PLAIN TEXT

You have just entered room "Chat 17615141151508182966."
x V DoGG x: hey guys, sorry i am late
Eceguru: no prob
kabev1: Does anyone know if the others will make it?
x V DoGG x: can someone copy and paste the history so i can catch up, if there was anything useful
kabev1: Nope, just waiting
Eceguru: we only did intros so far
starkiller76: Abhishek picked the time, so I am assuming he will show up
Eceguru: i haven't heard anything from Gurusangappa Honawad since the project started
starkiller76: Ditto
Eceguru: i tried getting in touch with him several times
x V DoGG x: ok well, i am vivek and i work at Motorola, graduated from Purdue in 2001
starkiller76: I went to Iowa
Eceguru: i work at motorola as well and am from illiniois
sudigh: I work for Synopsys and I'm a Masters in Mathematics.
Eceguru: damm
Abhi327 has entered the room.
Eceguru: bears down 14
Abhi327: Hello everyone 
starkiller76: Damn
Eceguru: alright, turning game off now
kabev1: GOOD
starkiller76: probably for the best
kabev1: So, let's begin again with intros, who's who
Eceguru: i'm isaac
kabev1: I'm Kabe
x V DoGG x: ece - what mot are you at?
sudigh: i'm sudipta
x V DoGG x: i am vivek
Abhi327: I'm Abhi
Eceguru: schaumburg
x V DoGG x: kabe & I are too...
Abhi327: i am an ex-motorolan
starkiller76: Hey, I'm Dave Bowen.  I live in Bartlett, IL  and work downtown Chicago.
kabev1: ex by choice??
Abhi327: unfortunately no 
x V DoGG x: ok...
Eceguru: i'll save the chat log for records
sudigh: so looks like like we are 7 instead of 8.
x V DoGG x: So who still needs to pick up some of the use cases?
starkiller76: Seems so
Eceguru: me
Eceguru: i tried getting in touch with Honawad to work on them
starkiller76: I emailed Howard Sun about us only having seven, I am still waiting for a reply
x V DoGG x: how many use cases were there? i forget....
x V DoGG x: and i am going there now
sudigh: 8
x V DoGG x: ok... 
x V DoGG x: so are we gonna give up on Honawad?
Eceguru: use cases 1,2, 4, and 5 are covered right
x V DoGG x: and make a group of 3?
sudigh: yup
Abhi327: yes
Eceguru: i think we should
sudigh: I guess we can make a group of 3 we the #of members is odd.
Eceguru: who wants to take me in
starkiller76: I will
Eceguru: alright
starkiller76: Where do you live, BTW
Eceguru: i live in round lake, il
Eceguru: near gurnee
starkiller76: OK
Eceguru: my gf lives near bartlett, in bloomingdale
sudigh: one of the pairs/triplets has to take up 3 use cases.
starkiller76: We can do three, since we will have 3 people
Eceguru: ours can since we have 3 people
x V DoGG x: which pair does that leave?
sudigh: marshall hasn't joined us yet.
kabev1: Alright does everyone understand their use cases?
kabev1: I have an overall question, How does Wi-fi fit into this?
kabev1: I'm not bashing it, just curious
Eceguru: for use case #3, i assume we'll need to do the use case for both sides of the application right
Eceguru: we can receive or initiate a search right
sudigh: we are using wi-fi to make the whole application wireless, right ?
Abhi327: yes
Eceguru: sorry, yes to which question?
Abhi327: yes to sudipta's question
kabev1: We can come back to my question later... back to use cases
Eceguru: so vivek and kabe are doing #4,5
kabev1: right
starkiller76: How are the use cases broken up now?  I already have a full dress use case written up for #5
Abhi327: issac, could you clarify on what you mean by both sides of the application ?
starkiller76: Plus my group is doing extra work, by completing 4 use cases out of the 8
sudigh: cool.
Eceguru: well, this app is a peerless application
Eceguru: so it is both a server and client
Eceguru: am i correct so far
Abhi327: yes absolutely 
Eceguru: so when we do a search a few things must happen
Eceguru: the program will send a search request out
Eceguru: and the other machines will have to respond to it
Abhi327: from a use case standpoint, it shouldn't really matter if the server side or the client side of the application initiates the request 
Abhi327: it should be transparent enough 
Abhi327: does that make sense 
Abhi327: the actor would still be the application 
Eceguru: won't the use case be different depending if you receive or inititate a request
sudigh: isn't it a non-centralised system where the server and client are running at all the local nodes ?
Eceguru: yes
Abhi327: yes sudipta 
Abhi327: issac
Abhi327: could you tell us a little bit more about how you 
Abhi327: think the use case works when initiating or serving a request
Abhi327: lets make sure we all are on the same page. 
starkiller76: How are the use cases broken up between the group now?  I have a full dress use case already written up for #5.
Abhi327: 21 - 7 packers
Eceguru: first initiating a request: the user will be the promary actor.  the application will take the request and call other nodes as supporting actors
Abhi327: ok
x V DoGG x: makes sense
Eceguru: for serving a request: the primary actor is the request.  the application will search the files, which are like the supporting actor
x V DoGG x: i know kabe and I are doing 4 & 5
x V DoGG x: but we can give them up
x V DoGG x: since you are already prepared
Eceguru: then it will send back the response to the requesting node
x V DoGG x: and take 6&8 instead
starkiller76: Have you written up 5 yet?
sudigh: for serving a request, won't the application be the primary actor ?
x V DoGG x: nope
x V DoGG x: we just picked today
Eceguru: yeah, but on seperate machinces
x V DoGG x: btw: after reading the assignment it looks like it isn't due for us until sunday night... (or before sunrise on monday)
Eceguru: its the same app but on seperate nodes.  i think the other machines should be treated as seperate actors in this case
x V DoGG x: star killer - if you are in agreement, i can add a column to the wiki
x V DoGG x: with assignments
Abhi327: this is what i was thinking
Abhi327: the application could bebe initiating or receiving a request. 
starkiller76: That is fine with me
Abhi327: in both cases, it shall still search its node and then pass the request requesting a search at all other nodes available
sudigh: But the application on all nodes is the same isn't it, if yes then it is the same actor (application) on all the nodes.
Eceguru: ok, i'm not sure how peerless networking works completely
Abhi327: hence from the use case or for that matter an application standpoint
Eceguru: so the app will always pass the request on then?
Abhi327: receiving a search request from an outside node or from its own node will still be handled the same way
Eceguru: ok, i'm starting to understand now
x V DoGG x: ok, on the other hand... i would like to recommend that we use HTML written by hand on these WIKI pages....
Abhi327: i am thinking abotuthe use case as we talk
x V DoGG x: it looks impossible for me to add stuff to the html table for the use cases because there are a TON of tags all over it....
Abhi327: so let me know if it makes sense
sudigh: Do we need to modify the use cases to fully dressed on Wiki ?
starkiller76: I can add the stuff it to the Wiki page
kabev1: I don;t think so
sudigh: cool.
Eceguru: i think it makes sense
sudigh: that is way waste of time.
Abhi327: sudipta: i wouldn't think so. However, we need to build our project wiki page and this will be a good way to post our work including our team meeting logs.
sudigh: Ok.
Abhi327: Team, what do you say ?
x V DoGG x: good with me
Eceguru: maybe now is a good time to talk about how we'll keep track of the team work and build a record of evidence that shows we follow the process
x V DoGG x: By my count here is the use cases:
sudigh: Sure, lets do that.
Abhi327: yes lets talk about it 
Abhi327: i think we should all get together once a week.. It doesn't have to be a long meeting.
Eceguru: i don't know but what do we need to show we follow xp
Eceguru: what types of artifacts?
sudigh: I think we should exchange our fully dressed use cases among pairs/triplets to get a idea of the diagrams, what do you think about this ?
Eceguru: yes
starkiller76: BTW we don't know if we are using XP or RUP yet, do we?
x V DoGG x: sorry i meant... here are the use cases: 1&2 - Abhi & Sudipta; 6&8 - Vivek & Kabe; Dave,  Issac, & ????? - 5
Eceguru: add 3, 4, and 7 to ours
x V DoGG x: ok, i didn't want to assume
Abhi327: We put XP in our vision statement. 
x V DoGG x: and what was the third members' name?
sudigh: we are using XP dave.
Eceguru: that's fine right dave?
starkiller76: add 5 to ours also 
Abhi327: I think with a project like ours, we can't really plan too much. 
Eceguru: we should also assign the xp roles as well
Abhi327: We need to kinda get going, do a good risk assessment and start working towards our most important user stories
sudigh: yup, how about Abhi being our coach :-)
Eceguru: that's fine, i haven't done xp before
sudigh: I havn't done XP before either.
Abhi327: Do we need an XP coach ?:-)
Abhi327: I was thinking each one of us should serve as a coach 
sudigh: yes, it is mandatory
Abhi327: on the team for one week
Abhi327: this way 
Eceguru: i think we should have someone trying to educate the rest of the team on xp and try to make sure we follow it
sudigh: thats what the prof said in his last lecture.
Abhi327: it'll force everyone of us to think about the process and question if we are following the process
starkiller76: I will repeat, it has not been posted on the WIKI whether we are RUP or XP
Abhi327: i am ok with serving as an coach on the team if the team wants it.
Abhi327: as part of the vision document, we said we will be an XP project
x V DoGG x: i think it is at the bottom of the page
Eceguru: i read that as well
starkiller76: Thanks
Eceguru: i think we can rotate coach role later but i think we should have some stability at that position for a while
kabev1: I afree with ISAAC
sudigh: no one replied to my question of circulating thier respective fully dressed use cases, so that each pair/triplet can come up with the global diagrams.
x V DoGG x: does anyone know XP pretty well?
Abhi327: i've done an XP
Abhi327: project 
Abhi327: for a class project
Eceguru: i think we should circulate the use cases
kabev1: What do you mean circulate?
Abhi327: circulate the use cases ?
sudigh: we  have a look at the fully dressed use cases of all the pairs/triplets.
starkiller76: Actually, we are not suppose to work together on this assigment (per Johnson).  It is OK for the pairs to  have different diagrams.  He just wants us to cover all use cases
Eceguru: alright
Eceguru: lets pass them around after sunday then
sudigh: I meant only the use cases.
sudigh: Diagrams will be private to eachpair.
Abhi327: we should exchange our work right after the submission.
Eceguru: yes
Eceguru: till then keep them private to each group
starkiller76: I agree with Abhishek
Eceguru: ok, so we have a coach right
Abhi327: this way for the next team meeting, we know what kind of a system we have in mind
Eceguru: yeah
sudigh: Ok.
Abhi327: and we can work next meeting to outline our design
Abhi327: XP doesn't really have a design phase
Abhi327: but we should make this in to our informal design phase
Eceguru: i think we should for our initial iteration planning
x V DoGG x: ok
Abhi327: yeah. 
Eceguru: what other roles do we need to fill
Abhi327: we can't really exchange any ahomework 2 related work but this is the time
Abhi327: we can quickly run through our use cases if anyone has any questions
kabev1: I'm gonna bud in here, At the end of this meeting what should we have accomplished?
Eceguru: i think we should figure out what we'll be working on in the future
Eceguru: and determine who's doing what
x V DoGG x: i updated the wiki and added an "assigned to column" for the breifs
Abhi327: 1) Distribute use cases 2) Decide on a day, time for our weekly meetings, 3) Roles .... 4) Strategy. 
Eceguru: i think the use cases have been distributed
kabev1: ok, so 1 is done
Abhi327: ok off to 2nd 
Abhi327: on to second
Eceguru: is this time fine in the future
x V DoGG x: sure
Abhi327: fine with me
Eceguru: i'd ask for a different time on weeks that the bears play on mnf
Eceguru: its only 2 more times in the future
Abhi327: they won't play a monday night game anytime soon
Eceguru: no they won't
Eceguru: so this time is fine with me
Abhi327: :-)
sudigh: fine with me.
Abhi327: dave ?
Abhi327: kabe ?
starkiller76: Monday is fine with me
kabev1 has left the room.
x V DoGG x: i think kabe got disconnected
Abhi327: yeah. 
Eceguru: ok
Abhi327: but it looks like we can work on having this time for our team meetings
Eceguru: so on to #3
Eceguru: we have a customer already right
starkiller76: I hate to be a pain, but Johnson said in lecture last week that he had not picked which groups are doing XP vs. RUP.  Does anyone have information contrary to this?
Abhi327: yes 
Eceguru: i think we're supposed to do xp
Eceguru: i think he was refering to teams that didn't specify in their vision statement
Abhi327: I believe Dr. Johnson said that they will point out the groups that they don't think should follow a certain process
x V DoGG x: hmmm, did he say that?
x V DoGG x: i thought he said, he would pick for everyone
x V DoGG x: he might take the recommendation into consideration
Abhi327: that is what i got from the lecture
sudigh: In the project plan, there is no start date for starting coding. Any idea when we start coding ?
starkiller76: I heard the same thing as Vivek
Abhi327: however, he also said that if a team really believes they should follow XP, then he might just let them do it 
Abhi327: ok lets ask the team first
Eceguru: what would everyone prefer
Abhi327: yes what do we prefer
Abhi327: XP / RUP 
Abhi327: i vote for XP 
x V DoGG x: kabe just called me and told me he is having networking problems
x V DoGG x: but 8:30 is fine with him
Abhi327: great
x V DoGG x: XP
starkiller76: I am for XP.  I just wanted to make sure Johnson wasn't going to force us to do RUP>
Eceguru: xp sounds good to me
Eceguru: how about we assume we'll do xp and i'll email him to confirm
starkiller76: That is a good idea.
x V DoGG x: ok
x V DoGG x: sounds good
Abhi327: issace, you might want to email howard first 
Eceguru: alright
Abhi327: ok sounds good. 
Abhi327: haven't heard from sudipta ???
sudigh: xp, rup either is fine. how do we provide evidence that we followed xp ?
Eceguru: coach?
Abhi327: Work on interations
Abhi327: Have code to show
Eceguru: or should we finish assigning roles 1st
Abhi327: but more importantly
Abhi327: we'll show
starkiller76: We probably need to document how we performed pair programming
Abhi327: that we followed XP 
sudigh: I think we need to specify what technology we used to simulate XP, since not all of us can meet in person and sit and work together.
Abhi327: by following its practices such as programming in pairs, rotating pairs, spending some time to keep our code simple, doing the simplest thing first,......
Eceguru: how about we continue assigning roles and one of us can figure out what evidence is needed off-line
Abhi327: and most of all
Abhi327: unit tests 
Abhi327: even before we code
Abhi327: having fixed and short iterations
sudigh: yes, we need to scome up with automated unit tests, that is a must.
Abhi327: continous integration and internal milestones
kabev1 has entered the room.
sudigh: cool, sounds good. So off we are sailing on XP.
x V DoGG x: i don't think we had kabe's input
Eceguru: yeah
x V DoGG x: on XP
x V DoGG x: kabe so far everyone has voted XP
kabev1: Hmmmmm.......
x V DoGG x: i will copy and paste the history to your instant messenger window
kabev1: Xp is fine with me
kabev1: Have we decided roles?
Abhi327: No we haven't 
Eceguru: we're all developers 
Abhi327: yes.
sudigh: when do we start putting together the milestones ?
Eceguru: think we have to wait till after hw2 is complete
sudigh: after/before mid-sem ?
Eceguru: to make schedule
Abhi327: Once we put our user stories in to interations and basically plan our iterations. 
Abhi327: we can start working on our informal design and iteration plans from next week. 
Eceguru: yes
sudigh: next monday would be good.
starkiller76: I agree
Abhi327: Ok lets talk about roles
kabev1: OK, so our roles are "developers"
Abhi327: what roles are we talking about other than developers, and coach 
sudigh: customer.
x V DoGG x: when are we gonna do user stoires
kabev1: Whoa... one thing at a time
Abhi327: after homework 2
kabev1: Roles
Abhi327: We have a customer 
Eceguru: tracker, tester
Abhi327: on the team
Abhi327: He is my mananger 
sudigh: unit tests are developed by the respective developers.
sudigh: in XP.
Eceguru: are we all testers as well
kabev1: So, customer, tracker, tester
x V DoGG x: yeah....
Abhi327: I'll get him to sit in our meetings once every 2 weeks. 
sudigh: we are testers and developers.
Abhi327: yes all developers write unit tests
starkiller76: I agree with all of us being testers, but shouldn't one of us be a designated tracker
Eceguru: yeah, should we have a tracker
Eceguru: i can do it 
sudigh: ok,
Abhi327: Ok tracker sounds too vague 
starkiller76: i would do it also
Abhi327: lets define a concrete role
starkiller76: Tracker comes right out of XP book
Abhi327: how will the tracker really work within the process
Eceguru: track the team's progress on the iterations
starkiller76: Tracker keeps track of progress and keeps refining estimates
sudigh: we can rotate the role of tracker on a weekly basis.
x V DoGG x: so a tracker takes care of updating schedules and plans?
Abhi327: yes and the team's progress is evaluated at every team meetings correct ?
starkiller76: Correct
Eceguru: are our iterations going to be 1 week or longer
starkiller76: I say 2-3 weeks
Abhi327: i was going to propose a co-ordinator for the team meetings who will also put up an agenda before every team meeting and as part of agenda is the team progress. That person can serve as the tracker ont the team 
Eceguru: good idea
Abhi327: i say 3 weeks. 
kabev1: ok 3 week iterations
Eceguru: the trakcer isn't a full-time role
x V DoGG x: i can do that
Abhi327: agree issac
Abhi327: vivek ---- meeting co-ordinator and tracker ????
Eceguru: how about the tracker serves as the pseudo-boss for the meetings 
sudigh: ok.
Abhi327: there is no money involved
Eceguru: and sets the agenda
Eceguru: and stuff like that
Abhi327: what wold the role be for the boss ?
x V DoGG x: sure.... but did someone else volunteer to be tracker?
Eceguru: i volunteered
Eceguru: and so did dave
Eceguru: we can rotate
x V DoGG x: ohhh... ok....
x V DoGG x: thats cools
starkiller76: I am cool with rotating
x V DoGG x: i meant to just volunteer for having an agenda and moderating the meeting
x V DoGG x: but if we want to lump the roles together
x V DoGG x: thats fine....
Abhi327: sounds good 
starkiller76: Isaac and I can split up the tracking role 
Eceguru: ok
Abhi327: ok so vivek is the team meeting co-ordinator 
Abhi327: issac and dave = tracker
x V DoGG x: sounds good
Abhi327: for the timebeing 
Eceguru: ok
starkiller76: Agreed
Abhi327: sounds good 
sudigh: I can assume some role in some week later.
starkiller76: OK
x V DoGG x: abhi... i assume you are gonna continue moderating today's meeting
x V DoGG x: since you made the agenda
Eceguru: we can change roles after each iteration 
x V DoGG x: it was u wasn't it?
kabev1: I too will assumesome role in the future
Eceguru: i think we have the roles set now
kabev1: issac and dave = trackervivek = meeting coordinator
starkiller76: yep
sudigh: for the 1st interation.
Abhi327: Who did we say was maintaining the team meeting logs ?
sudigh: issac
Eceguru: yeah
Abhi327: should that go to vivek now ?
Eceguru: sure
x V DoGG x: yeah, i can take care of that
x V DoGG x: i will keep the agenda's and meeting logs on the WIKI
kabev1: I think it would be good to seperate the 2 for now
x V DoGG x: again, i just wanted to ask if there is anyone that disagrees that we should do the WIKI in simple html (by hand)
Abhi327: It'll be good if vivek can send out an agenda a day before the meeting. The rest of the members can basically append any other open issues to it. 
Eceguru: sounds good
kabev1: simple html!!
Abhi327: is it too much work ?
Eceguru: simple html
x V DoGG x: to keep from having a ton of junk placed in by things like microsoft frontpage, because it is very annoying to sift through all the tags to add one thing
x V DoGG x: abhi - are you saying that HTML by hand might be too much work?
Abhi327: yes vivek that is what i meant
kabev1: You can still use frontpage, just keep it simple
x V DoGG x: yeah, but is there a setting in frontpage that will
kabev1: on xml, etc
kabev1: no xml, etc
x V DoGG x: avoid having all the font tags and stuff that gets stuffed in
Abhi327: however, i agree that it is hard to edit the wifi pages when using forntpage
x V DoGG x: yes... 
Abhi327: wifi = wiki
x V DoGG x: is there anyone who doesn't know HTML here?
x V DoGG x: if not, then i think we all agree to stick to simple html...
kabev1: summarizing the roles, the others of us have no roles right now?
sudigh: I don't know XML, simple html is all i know.
Eceguru: well, developer role
starkiller76: I did the web pages.  I will redo them and maintain them if you guys want.
x V DoGG x: Ahh! great! yes, that would be very appreciated
x V DoGG x: i just added us to the 2002 fall project list
x V DoGG x: wiki
x V DoGG x: if you could make 'em simple html that would help a lot! that way we can all append to the pages as we are doing the project, very easily
Eceguru: yeah
starkiller76: That shouldn't be a problem
kabev1: OK.....  Next item
x V DoGG x: i think that your role as the maintainer shouldn't involve too much outside making sure that everyone is following the structure... cuz we can all help put our own content up there (test results, progress, uml diagrams, etc...)
Abhi327: developer and customer are the most important roles in XP and the rest of the roles we'll rotate as we get comfortable using the process and working the system
starkiller76: I put them up rather quickly, and always planned on redoing them
x V DoGG x: yep, no prob... they look nice ;-)
x V DoGG x: ahbi - what else is left?
Eceguru: so do we have a plan for what we'll do till next wekk
Abhi327: i have some other open issues, but i think i'll put it off till next time.
starkiller76: HW2
x V DoGG x: yep
Eceguru: we can't talk to much till that's over
x V DoGG x: and the names are up on the use case wiki
x V DoGG x: sure
starkiller76: thanks vivek
Abhi327: yeah lets not think too much in to the future
x V DoGG x: 8:30 next monday...
Eceguru: alright
starkiller76: That wouldn't be XP
Abhi327: lets think XP. 
Abhi327: absolutely dave
starkiller76: Agreed, talk to you all next monday
Eceguru: alright, bye
Abhi327: ok eveyone can send in their open issues
Abhi327: to 
Abhi327: vivek
Abhi327: Folks
kabev1: sounds good to me
x V DoGG x: yepo
Eceguru: vivek, you're saving the log right?
Abhi327: we need to decide on one person who'll serve as the official communicator for the group when talking to the course staff or the professor
x V DoGG x: i will grab it once we are done
sudigh: I can do that
Eceguru: who wants to be communicator
kabev1: Initially, I think one of the first 3 should
Eceguru: ok, try to confirm then the use of xp
Abhi327: yes
Abhi327: issac are you taking that up or would you like me to send an email
starkiller76: I already emailed Howard about our missing member
Eceguru: you can do it
kabev1: So Communicator is: who?
Abhi327: ok i'll send an email to howard on the group's behalf
Eceguru: abhi is right?
kabev1: Cool
x V DoGG x: Can we post everyone's contact information on the WIKI
x V DoGG x: ?
Abhi327: ok 
x V DoGG x: without the phone number
Abhi327: without the phone numbers
kabev1: I'll post the contact info
Eceguru: is that all?
x V DoGG x: yep
Eceguru has left the room.
Abhi327: yes 
kabev1: Abhi, anything left?
starkiller76: Bye
Abhi327: do we want to summarize our discussion
Abhi327: and send it to the group
Abhi327: especially people who've missed today's meeting
sudigh: sure, sounds good.
kabev1: I say summarize and post on the Wiki
Abhi327: we cna just sent out the log or a link to our log if we post them
kabev1: Who is summarizing?
starkiller76: We can all take turns
x V DoGG x: i don't know
Abhi327: i say summarize
Abhi327: and keep it very bried 
x V DoGG x: i think it isn't necessary
Abhi327: however, its ok if we don't just post the 
x V DoGG x: if someone misses the meeting
Abhi327: link to the team meeting log
x V DoGG x: they should take the time
x V DoGG x: to read the log
Abhi327: or send it out as an attachment
starkiller76: Vivek has a point
Abhi327: i agree vivek
kabev1: I don't
x V DoGG x: does anyone have a problem with posting the logs
starkiller76: No
Abhi327: kave
Abhi327: kabe 
Abhi327: what do you think 
sudigh: do you wanna post the whole log of this chat ?
kabev1: I do believe we should summarize
sudigh: I too believe we summarize.
kabev1: Even though I have been at the meeting I cannot tell you what all happened
kabev1: Vivek, since you're capturing why don't you summarize 
Abhi327: vivek i know its extra work. but can we summarize ? It makes sense we do.
starkiller76: OK, why don't we summarize the first couple of meetings, then take a poll to see if it is helpful?
x V DoGG x: how about if we post answers to each of the agenda items
Abhi327: yes that is exactly what the summary will look like
Abhi327: agree kabe ?
x V DoGG x: i can do that.... but i still think that it is every member's responsibility
kabev1: That is a summary to me ;-)
starkiller76: I think we should take turns summarizing.  We can set a shedule.
starkiller76: All the work should not fall on Vivek
kabev1: I'll summartize for now
sudigh: they have put up a bunch of points to follow for the XP followers.
sudigh: on wiki
sudigh: we'll try to follow them.
starkiller76: Thanks Kabe.  We can pick someone different next week
kabev1: Vivek, email the log to me
Abhi327: and vivek you still plan to post the meetings is that correct ?
starkiller76: I have to go.  I will talk to you guys next week.
kabev1: alright, any open items at this point?
starkiller76 has left the room.
Abhi327: i think we got most of it covered 
sudigh: so are we calling it a day now ?
Abhi327: it was a productive team emeting i would say 
sudigh: sure.
Abhi327: not bad for a first time 
x V DoGG x: ahbi - yes
kabev1: I agree, I'll have a summary up tomorrow
Abhi327: great. 
Abhi327: alrighty then
x V DoGG x: cool
x V DoGG x: i will have the log up in a few mintues
Abhi327: thanks everyone. 
kabev1: Talk to everyone next week
sudigh: Ok, bye then. thanks, it was a good one.
Abhi327: yup cya everyone next monday 
Abhi327: goodnight 
sudigh: goodnight.
Abhi327: signing off !! 
kabev1 has left the room.
Abhi327 has left the room.
sudigh has left the room.