You have just entered room "Chat 31060726221469070983."
michaelwalsh327: well, we should talk about project roles a bit, and perhaps begin to see wht the next iteratiois about.
x V DoGG x: hey guys
x V DoGG x: sorry i am late
michaelwalsh327: I thought we could also go over our Change Control plan from last night for the other group members.
michaelwalsh327: ANy other agenda points?
x V DoGG x: source forge info
kabev1: Is there a doc for the Change COntrol Plan?
michaelwalsh327: not yet.
gorclon1: we have as sourceforge account already
michaelwalsh327: will be later today, sourceforge's capabilities are different than we expected.
kabev1: Vivek and I put the code in cvs today
Eceguru: that's good
x V DoGG x: ok so to capture that:
x V DoGG x: 1) Change control plan
x V DoGG x: 2) Project roles
x V DoGG x: 3) Sourceforge - Code
x V DoGG x: 4) general q&a
kabev1: 5) website
x V DoGG x: 6) What we plan to do for next week
gorclon1: 6a)plan for semester
x V DoGG x: 0) quick intros
x V DoGG x: ok lets begin.....
salcs329 has entered the room.
kabev1: Vivek, you drive the meeting
x V DoGG x: 0) lets do a quick intro
kabev1: I am Kabe
Eceguru: i'm isaac
x V DoGG x: I am vivek, been with the group since last semester.
salcs329: hello everyone. This is Sal (Faisal Razzaq) from San Diego
x V DoGG x: chicago
kabev1: Chicago
Eceguru: chicago
gorclon1: Ryan in Kansas
starkiller76: I'm Dave from Chicago
michaelwalsh327: Michael Walsh from CHicago. Sal, Ryan, and I worked together last semester.
gorclon1: Used to be from near Chicago
salcs329: lived in Chicago for 10 years
x V DoGG x: onto #1) Change control plan
se2srini: Srini from Birmingham
x V DoGG x: walsh - do you want to lead?
michaelwalsh327: sure.
michaelwalsh327: (shuffle shufflke)
michaelwalsh327: OK, here's an overview. There are four points explicitly mentioned in the homework:
michaelwalsh327: 1) How bugs are registered
michaelwalsh327: 2) How feature requests/suggestions are registeres
michaelwalsh327: 3)How to decide what features/bug fixes will be implemened next
michaelwalsh327: 4) How to determinieif a feature/bug has been implemented, and in what version.
michaelwalsh327: Before addressing those, we present a pair of definitionsd:
michaelwalsh327: A defect, or bug, as a difference from the documented requirements.
michaelwalsh327: An enhancement request is a desire for something that is not explicitly covered in the requriments.
michaelwalsh327: These are handles in different ways, as follows:
michaelwalsh327: (We intended to use Bugzilla, which we thought was what sourceforge included, but it's not, so the process changes slightly)
michaelwalsh327: For bugs:
michaelwalsh327: There are four levels of severity:
michaelwalsh327: (using the Bugziolla terms for now)
michaelwalsh327: Blocker: work cannot continue until this issue is resolved
michaelwalsh327: Major: Work can continue in other areas, still an important bug
michaelwalsh327: Minor - a minor annmoyance, or an easy fix
michaelwalsh327: Scracth that, there will only be three now, we intented the fourth to be "enhancement" but they get their own category now.
michaelwalsh327: In addition to the severity, bug reports include the person who found the bug,
michaelwalsh327: detailed steps for reporduction,
michaelwalsh327: the failing requirment
michaelwalsh327: any supporting materials,
michaelwalsh327: (pause for comment - what other required fields)
michaelwalsh327: -v versoin, I suppose
michaelwalsh327: any other thoughts?
Eceguru: i think that sums up bug submission
michaelwalsh327: Well, tnhatb sums up what's in a report. Here's the process bugs go trhorgh:
salcs329: do we have subsystems in the project
x V DoGG x: sounds good
michaelwalsh327: 1) Unconfirmed - this bug has been found by one developer, but its existence is not yet confirmed by another team member
x V DoGG x: do we need to tie bug reports to version control?
michaelwalsh327: 2) new - thisis a confirmed bug
kabev1: subsystems -no not yet
michaelwalsh327: yes, we'll get to that.
x V DoGG x: ie. bug #102 was fixed in version #1.2 (documented in the bug and code)
salcs329: perhaps a subsystem/component field on bug report
michaelwalsh327: Good idea.
michaelwalsh327: 3) resolved - the repairer says this is fixed
michaelwalsh327: 4) verified - a second party agrees that this is fixed
michaelwalsh327: 5) closed - bug goes away
michaelwalsh327: Important point about that seuence - if you're in the middle of working, and you find a bug, you can go ahead and fix it
michaelwalsh327: BUT
michaelwalsh327: your change doesn't get merged until the problem and the fix are erified.
michaelwalsh327: All team members are authorized to confirm both problems and fixes, to minimize bottlenecks
michaelwalsh327: Anyone can work on a bug fix - buigs are provable different than the requirements, and thus bug fixes don't need to go through the CCB.
michaelwalsh327: That pretty mh sums up bugs. pause for comment...
michaelwalsh327: ...
x V DoGG x: cool
x V DoGG x: i didn't hear the answer to tieing code fixes and bugzilla entries together
michaelwalsh327: OK, moving on toi change requests.
michaelwalsh327: We';re not there yet, but will get there - it's the same for both.
x V DoGG x: ok
michaelwalsh327: Heck, I'll get to it now - you tie cvs and bugs together w/ comments as suggested in class./
michaelwalsh327: So, your cvs entry says what bug you fixed,
michaelwalsh327: amd your bug report says what version the fix is in.
salcs329: Are we going to have BUG_IDs
salcs329: We can put BUG_IDs in the comments
Eceguru: that sounds like a good idea
michaelwalsh327: Because sourceforge doesn't have a very customizable bug form, folks weigh in that a bug is confirmed a bug or confirmed fixed by adding a comment to the bug report.
kabev1: bug ids are autogenerated
se2srini: I think while checking in the fix for a bug, you specify the bug id. Similarly before you close the bug, you give the code version # that fixes the bug
salcs329: Even if auto gen that's ok.. just put in comment in CVS
michaelwalsh327: Yea, that's smart, hopefully bug IDs are inherent in sourceforge, otherwise we'll add them manually, also in the comments field.
salcs329: so we can trace to the bug
michaelwalsh327: (Still some pending investigation into Sourceforge's available functioanality)
michaelwalsh327: So, for Change requests, they go through the pretty much the same process after they've been approved, but before a change goes in, it goes by the CCB.
michaelwalsh327: This will be three team members, with 2/3 votes required for approval.
michaelwalsh327: There is a loophole:
michaelwalsh327: If your change request is denied, but you think it's really important to have in, you can bring your case before the group as a while in this meeting.
michaelwalsh327: (not that we expect any roblems getting through, or even many changes)
michaelwalsh327: There is a maximum one week turnaround time for change requests through the CCB.
kabev1: question--
michaelwalsh327: Note that the CCB does not actually scheuled change requrests.
michaelwalsh327: The CCB says ehat changes will be made, and the PM schedules fixes.
kabev1: "with 2/3 votes required for approval."-- 2/3 to be on the board or for approval of bug?
michaelwalsh327: The PM also can assign people to bugs that are lingering with no one working on them.
michaelwalsh327: no approval necessary for bugs, as bugs are demonstrably different from reqs.
michaelwalsh327: Only approbal required for change requests.
se2srini: approval of change requests need atleast 2 in favour of it
michaelwalsh327: (sorry I didnt see your question, my head was in my keyboard)
kabev1: np, got it now thanks :-)
michaelwalsh327: Right. 2/3 in board, or majority in group as a whole, in the event that the board vetoes the change.
michaelwalsh327: hat's pretty much iut, am I missing anything guys?
x V DoGG x: sounds good....
michaelwalsh327: (p.s. pls get the transcript up tonight, cause I want to refer to it and didnt save it)
x V DoGG x: if there is nothing else... lets move onto #2) project roles
x V DoGG x: transcript of last meeting?
kabev1: can we do 3 and 5, I need to get some sllep (sick)
se2srini: Just to calrify, even change requests should be identified with ids and tracked like bugs
michaelwalsh327: yes.
x V DoGG x: the transcript is already up
Eceguru: they are sumbited through sourceforge as well
michaelwalsh327: (to both of you, let's let Kabe sleep and make him the project doughboy while he's away)
x V DoGG x: (dave to thank
x V DoGG x: )
kabev1: :-)
x V DoGG x: ok lets skip to #3
x V DoGG x: kabe - go ahead
michaelwalsh327: ahh, I meant the t5ranscript from our meeting last night, sorry for confuision.
kabev1: Vivek and I put the code into cvs today
kabev1: Other than Dave is anyone working with CVS for HW1?
michaelwalsh327: just latest/current version?
kabev1: just latest
michaelwalsh327: cool. docs in as well?
gorclon1: I'm on group one, but haven't talked with dave
x V DoGG x: i believe ryan is on that team....
starkiller76: I will be sending a doc
starkiller76: early tomorrow
x V DoGG x: we should meet tomorrow night
starkiller76: to all on cvx
starkiller76: cvs
x V DoGG x: is 9pm good for everyone?
x V DoGG x: (cst)
starkiller76: fine
gorclon1: earlier is better
gorclon1: but 9 is ok
salcs329: We were think of putting everything including docs on CVS/sourceforge for easy accessibiliyt
michaelwalsh327: send doc to all, it'll be good to see your plan ahead of time.
kabev1: ok meet tomorrow at 9:00
x V DoGG x: mike - we will send it out wed morning
kabev1: continuing....
x V DoGG x: after it is discussed at least once within the group tomorrow night
michaelwalsh327: fine.
x V DoGG x: 9pm it is
x V DoGG x: ok....
kabev1: cont...
x V DoGG x: everyone
kabev1: we have placed everything in CVS for now
x V DoGG x: should checkout all the code
x V DoGG x: before our next meeting a
x V DoGG x: and contact others if you have trouble
x V DoGG x: we have checked it out and compiled it on windows
x V DoGG x: with the existing scripts
x V DoGG x: if you want to compile/run on linux, you will need to modify the install/compile scripts
x V DoGG x: ok onto #5
kabev1: we won't go into a lot of detail right now that will be in the doc
x V DoGG x: website
se2srini: guys, do you know how to add ourselves to this project team in sourceforge.
kabev1: an admin has to do it
Eceguru: are we admins
kabev1: send me your sf account names
kabev1: right now Mike and I are
x V DoGG x: ok
x V DoGG x: on the webpage
kabev1: #5
Eceguru: are we using the original sf account from last semester
x V DoGG x: yes
x V DoGG x: kabe - go ahead
kabev1: we have 3 websites currently
kabev1: We should come up with a plan to coordinate all 3 together nicely
x V DoGG x: yes....
salcs329: Can all be merged or linked from Source Forge
se2srini: what are the three?
x V DoGG x: and then put up messages on the others pointing to the central location
starkiller76: wiki, sourceforge, and ?
kabev1: the uiuc site, the sf site with cvs, and http://linux-p2p-wifi.sourceforge.net/
michaelwalsh327: wait, there are two sf sites now?
salcs329: We need a central place where we can access everything
kabev1: ok, hold on here
x V DoGG x: there is a docs section the sf website that needs to be linked up to the docs that are avialable in cvs
kabev1: ok
kabev1: ok
kabev1: ok
kabev1: hold
kabev1: on
x V DoGG x: (is that what kabe is saying)?
kabev1: We need to try to have a little order with the meetings, so they don't go on too long
kabev1: let me present the topic first then questions
kabev1: We have 3 sites and need to link them all together
kabev1: I suggest we use the http://linux-p2p-wifi.sourceforge.net/ site as our main site and link to the other sf site and uiuc
kabev1: thoughts?
se2srini: I agree
michaelwalsh327: what is the other sf site? Is it not the CVS page from the main project pager?
kabev1: go to home page from the sf page
kabev1: http://sourceforge.net/projects/linux-p2p-wifi/ then home page
x V DoGG x: ok
x V DoGG x: who wants to take the task of consolidatating all the websites?
kabev1: I'll put a page up on http://linux-p2p-wifi.sourceforge.net/
starkiller76: I agree with kabe also
kabev1: And we can then modify it as needed
x V DoGG x: i agree
x V DoGG x: ok, this kinda transitions directly to #2 - roles
kabev1: alright, I'm done
michaelwalsh327: Now, there's nothing on the "home page" no, right?
kabev1: right
michaelwalsh327: (sorry, still have lingering question)
x V DoGG x: ok
x V DoGG x: are we done with webpage?
michaelwalsh327: Might be easier to not use it, then, and give oursleves one less thing to keep track of.
michaelwalsh327: but I'm OK having that discussion later.
x V DoGG x: ok
x V DoGG x: lets table that one for now
x V DoGG x: lets move to agenda item #2) Roles
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Summary-1-29-03
x V DoGG x: i am starting to post a summary on this web page from our last meeting
x V DoGG x: you can see
x V DoGG x: the roles from previous semester
x V DoGG x: (i apologize for the missing updates from last meeting)
se2srini: May be some of you who had been in this proj last semester can tell us about your project role (#2)
kabev1: alright, I gotta go, talk to you guys later, Dave send me what you have tomorrow can you?
starkiller76: sure
x V DoGG x: please tell me what roles you guys would like
kabev1: CM
x V DoGG x: (check the webpage now)
kabev1 has left the room.
Eceguru: i'm doing testing stuff
Eceguru: write test cases
Eceguru: and test plan
x V DoGG x: issac are you still on bug tracking?
x V DoGG x: or would someone like that role
Eceguru: someone can do that
gorclon1: O
x V DoGG x: many roles were doubled up last semester because of some disappearing group memebers
gorclon1: I'll need a role
Eceguru: i think we have to split things up since we have more people now
x V DoGG x: ok....
x V DoGG x: Sal, Ryan, & Srini
x V DoGG x: and mike
Eceguru: i also was doing requirements docs at the end last semester as well
x V DoGG x: please tell me what roles to put you down for
salcs329: anything for me
salcs329: is ok
x V DoGG x: please pick one
gorclon1: bug track or website
x V DoGG x: from that web page
michaelwalsh327: well, I'm definitely going to want to go thorguth the existing docs and clean things up as much as possible.
x V DoGG x: and tell me if we need to add anything
se2srini: I see project admin, website admin, and Documentation Manager Role are open
salcs329: what is the URL for web page under discussion
x V DoGG x: ok... mike - do you want to do the website? and overall clean up as necessary?
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Summary-1-29-03
salcs329: thnx
michaelwalsh327: That summary, I notice that there are many RUP workers not on there. Perhaps we could put a more complete set up.
x V DoGG x: or would that be more doc manager?
x V DoGG x: i don't have a book in front of me
x V DoGG x: do you want to suggest some
michaelwalsh327: I've got one, give me a munte and I'll edit the page.
gorclon1: What about somebody for metrics?
x V DoGG x: mike - reload
x V DoGG x: now
x V DoGG x: so that you don't overwrite my changes
michaelwalsh327: ok, go tit.
michaelwalsh327: he hee. got it.
Eceguru: i'm off CCB now?
x V DoGG x: mike - please add things as they are mentioned
x V DoGG x: isaccc.... i am just going off of memory
x V DoGG x: sorry for the mistakes
x V DoGG x: i haven't finished reading the log
michaelwalsh327: well, I was thinking that folks might have a better idea of what they want to do if there was a more complete set to choose from, that's all.
x V DoGG x: yes
x V DoGG x: while mike is updating the page
x V DoGG x: we can move to general q&a for the new members
x V DoGG x: isaac, vivek, kabe, and dave are on this team from last semester
se2srini: my sf id is "Kattragadda", please add me in.
x V DoGG x: perhaps we can help answer these questions
x V DoGG x: srnini
x V DoGG x: please email kabe directly, as he may not follow the log close enough to see that line
se2srini: ok
michaelwalsh327: There's no database in this project, right?
starkiller76: right
x V DoGG x: correct
x V DoGG x: sal, srini, and ryan any querstions?
starkiller76: new members
se2srini: not that I can think of now...
starkiller76: become familiar with the following website
x V DoGG x: sal - are you still there?
salcs329: I need to read up once we get docs cleaned up
gorclon1: I've just downloaded you tar file from last semester
michaelwalsh327: I'd start reading now, actually.
x V DoGG x: actually....
salcs329: look forward to a unified site
x V DoGG x: i wuoldn't wait
starkiller76: Project JXTA
michaelwalsh327: read the studff in the current directory of the archive.
gorclon1: right
x V DoGG x: yes....
starkiller76: we are using JXTA technology as a basis for our system
x V DoGG x: everything is up on sourceforge so you can navigate the latest stuff
x V DoGG x: yes
salcs329: I will readup on JXTA.
x V DoGG x: the general proj. description is up on the wiki web page
se2srini: do we have any think more specific in JXTA
gorclon1: do we have to change the compileit.bat file?
x V DoGG x: for what?
x V DoGG x: ryan - change it for what?
x V DoGG x: walsh - is the website updated?
michaelwalsh327: yea, just finished.
gorclon1: so it works on our computers
starkiller76: on JXTA
michaelwalsh327: I didn't atatch names, but all official rup acrtos are up there.
se2srini: for jxta documentation, browsing the website takes too long
starkiller76: look at the programmers guide and
starkiller76: the tutorials
x V DoGG x: ryan - if you follow the installation doc
x V DoGG x: you should be fine
se2srini: :-) ok, what else!
x V DoGG x: no chagnes
starkiller76: you can reach them from the main page
x V DoGG x: the compile script is all relative
x V DoGG x: ok
x V DoGG x: the roles are updated
x V DoGG x: http://wiki.cs.uiuc.edu/SEcourse/Summary-1-29-03
x V DoGG x: please take a look
x V DoGG x: and start volunteering
x V DoGG x: mike will update it as we go a long
x V DoGG x: to keep everyone from overwriting changes
x V DoGG x: i will continue as architect....
michaelwalsh327: I think perhaps it would be good for dolks to look into these roles and indicatetheir interest in the next couple of days - their may be many unfamiliar roles.
salcs329: I will take bug tracking
x V DoGG x: ok
x V DoGG x: should we vote?
Eceguru: i can continue with doc management
starkiller76: I will keep project manager
michaelwalsh327: Like, for example - document management - what is that?
Eceguru: well, keep req. docs up to date and make sure traceability is current
x V DoGG x: lets do a first round of volunteering
x V DoGG x: and then there will still be many that remain
salcs329: I volunteer for bug tracking
x V DoGG x: we can fulfill over the next few days
x V DoGG x: Vivek for architect
se2srini: whats the diff between PM and Project Admin
michaelwalsh327: can we do this off line, though? It's a might big list.
x V DoGG x: ok....
x V DoGG x: lets update the wiki ourselves
x V DoGG x: over the next few days
Eceguru: alright
x V DoGG x: not everyone at once!
x V DoGG x: :-)
starkiller76: I think PM and proj. admin is the same thing
x V DoGG x: check back to make sure no one accidentally over writes your changes
x V DoGG x: yes
Eceguru: anything else?
x V DoGG x: i will compbine the two lists after the meeting
x V DoGG x: so there aren't any overlapping roles
x V DoGG x: ok
starkiller76: ok
michaelwalsh327: try top go by the RUP roles, and check with me/online RUP documentation if you don't know what something is. Obviuously,we all must play several roles. Some roles will probably be eliminated.
x V DoGG x: do we have any deliverables for next meeting?
se2srini: Looks like Document Manager is the only visible role left, I can take that. But I don't know what exactly I would have to do. Also a code reviewer.
x V DoGG x: #1) Check out all the code and compile it
x V DoGG x: (everyone)
x V DoGG x: #2) Everyone should be signed up to at least 2 roles
michaelwalsh327: #2) Indicate your RUP role preference on Wiki. (everyone)
michaelwalsh327: (sorry)
x V DoGG x: #3) Summary of this meeting (*vivek)
x V DoGG x: #4) HW1 submitted
starkiller76: keep these roles in perspective
starkiller76: most of the time we all with be coding and testing
x V DoGG x: i assume we don't need to meet on the topic of hw#1 before the submission
Eceguru: don't think so
x V DoGG x: ok
Eceguru: the submissions are seperate right
michaelwalsh327: no, but would be good for docs to circulate on Wednesday for group review.
michaelwalsh327: submissions are separate I assume.
se2srini: really!
x V DoGG x: so next meeting will be next week; same bat channel; same bat time....
se2srini: are submissions seperate?
x V DoGG x: yes.... everyone should send out there docs on wed morning
michaelwalsh327: srini - meaning one for group 1, one for group 2.
michaelwalsh327: not one for each of us.
x V DoGG x: mike is correct
se2srini: ok
x V DoGG x: anything else?
salcs329: mike are you putting doc for group 2
Eceguru: alright, see you next week
michaelwalsh327: yea.
salcs329: thnx
x V DoGG x: laters
starkiller76: goodnight
michaelwalsh327: bye.
se2srini: bye. goodnight.
Eceguru has left the room.
salcs329: bye
se2srini has left the room.
salcs329 has left the room.