| Date | Agenda | Log | Summary |
| 10/7/2002 | 1) Distribute use cases 2) Decide on a day, time for our weekly meetings 3) Roles .... 4) Strategy. | View | View |
| 10/14/2002 | 1) Discuss hw2 solutions among all team members. 2) Research current p2p projects to plan our strategy for the project. 3) Build on top of existing projects ? What protocol ? 4) Keep the meeting SHORT in view of the upcoming Midterm. 5) Course Staff: Discuss the initial response regarding the process choice. 6) Setting up the development platform. (Linux, wifi-enabled pair of computers, CVS) | View | View |
| 10/21/2002 | 1) Discuss hw2 solutions among all team members. 1.5) Come up with a good list of judging criteria for the options in #2. 2) Discuss the projects that were researched 3) Build on top of existing projects ? What protocol ? | View | View |
| 10/23/2002 | 1) General Q&A about jxta 2) Select the "jumping board" appication 3) Determin what services/components we are borrowing 4) Determine what services we are implementing 5) Find a good whiteboard application to use in the future during meetings 5) Come up with the module division 6) Pair up for intial iterations | View | View |
| 10/28/2002 | 1) Decide on target app. using component research undertaken by each group 2) XP vs RUP 3) Come up with the module division 4) Pair up for intial iterations 5) Find a good whiteboard application to use in the future during meetings 6) Discuss possible options for Guru to participate in team meetings 7) Setting up the tools/platform for the project | View | View |
| 11/4/2002 | View | View | View |
| 11/6/2002 | 1) Abhishek to deliver the first revision of our system class diagram. Divide the work for the first iteration amongst the team members. | View | View |
| 11/11/2002 | 1) Everyone should have created accounts for sourceforge and mail account information to Abhishek. Check if everyone is added properly to the project as developers with adequate permissions according to the role. 2) Review initial draft for the CM strategy - Kabe 3) Summarize progress with class diagrams by indiv. groups 4) Review any documentation changes at this point(project plan, req.) 5) Roles: Decide what doc. to move to the project website - Doc. Mgr. Guru and Abhi to serve as project admin ? | View | View |
| 11/13/2002 | View | View | View |
| 11/18/2002 | 1) Progress Defining API b/w UI, service, and core layers. 2) Abhi to distribute initial draft of design document defining API's and class details by Thursday NOON 3) Progress on Kevin's requirements doc. 4) Review any documentation changes at this point(project plan, req.) 5) Updates to sourceforge in terms of new doc, sample code, etc. 6) IMP: Decide on Deliverables by next meeting | View | View |
| 11/20/2002 | 1) Progress on Kevin's requirements doc. Vivek fired off an email to kevin last time 2) Review any documentation changes at this point(project plan, req.) 3) Updates to sourceforge in terms of new doc, sample code, etc. 4) IMP: Decide on Deliverables by next meeting | View | View |
| 11/26/2002 | View | View | View |
| 12/3/2002 | View | View | View |
| 12/16/2002 | View | View | View |
| 12/18/2002 | View | View | View |
| 1/29/2003 | View | View | View |
| 2/3/2003 | View | View | View |
| 2/10/2003 | View | View | View |
| 2/17/2003 | View | View | View |
| 2/24/2003 | 1) Discuss homework 2 - What metrics should we use going forward? 2) Progress report on the Search use case development 3) Assign teams for Homework 3 4) Future assigment of use case development | View | View |
| 3/3/2003 | 1) Discuss homework 3 - Split up into groups of 2, what to test, etc. 2) Progress report on the Search use case development 3) Discuss future coding assigments 4) Discuss project documentation - updates to, additional docs, format, etc. 5)Questions and Concerns | View | View |
| 3/10/2003 | View | View | View |
| 3/17/2003 | View | View | View |
| 3/31/2003 | View | View | View |
| 4/7/2003 | View | View | View |
| 4/14/2003 | View | View | View |
| 4/21/2003 | View | View | View |