Hey, Unfortunately I've been out of town the last three days, but I can't remember that I gave any promises helping out on the testing, anyway, my bad. As I see it my task is to do the work with Jonas for a good experience report, I'll do my best there. If I can be of any help for the rest of the coding tell me (as mentioned I just started my course in java programming and therefore my experience on that is quite limited). Jonas, I will finish my draft for bullet one during this weekend and do some more check up, would be fine if we can see each other soon to talk more about the doc (I guess monday, otherwise later). See you guys on monday Martin ------------------- > Hej guys, > > I write this email, because i'm really disappointed by the behaviour of > some guys. Am i always obliged to give orders for people to get started > with work? > We all have a lot to do, and it's gonna be even worse soon. I don't > understand why people didn't come to help Joachim for the testing, > today? > Martin you said that you would come and help Joachim for teh testing and > didn't do anything. This is even more surprising to see that big 50 > hours in the middle of an empty row in the number of hours that you > work. Is it an error? I really don't think that you worked 50 hours on > the project plan, and since the project is almost finished, when will do > you think you will do the rest of your hours?? > Yusuf, i appreciate what you did for the experience report, but you also > said that you would come and help Joachim with the testing. Why were you > not there? > Once again, as i already said, some of us invest a lot in the project > and try to make things good, whereas some others seem to have completely > forgot about it. > I really hope that things will get better, because now comes the worst > part of the project, so listen carefully to the plans for next week: > > -the testing report will be handed in today. And in contrast with what i > thought, the testing is really useful, because Joachim found many things > that go wrong in our code (not very surprising!). We all have to read it > and recode what goes wring > > -on monday i will have a meeting with the customer and the other project > leaders to decide which things will be implemented or not. As you > probably noticed, the requirements set are too high compared to what is > in possible to do for us. So we will lower the level a bit, and decide > which main requirements have to be done. > > -on monday we willalso have a meeting with Andreas (i'll tell you the > exact time later), to tell him about what is going on and maybe have a > feedback on the testing report. > > -The main problem will be to finish the coding: now our component works > quite bad: some functions don't work at all, some are unnecessary > slow... so we'll have to redo some coding. Many people already worked on > it, so why don't the others just read the code and the testing report > and try to repair what is wrong? Next week we'll have to finish with the > coding. > > -Jonas i read through the report. It's good, i think. But it may need > more content and technical description of our problems. The rest is > good. I remind you that everyone has to write a personal experience > report until the 3rd of December. So do it as quickly as possible. > > -let's finish with the project as soon as possible so that we can work > for our exams, what do you think? for this we need much more > motivation!!! > > See ya all on monday > > Alex > > -- > -------- > Alexei Kounine > Email: > <alexei.kounine@xxxxxxx> > <aleko379@xxxxxxxxxxxxxx> > Site: > http://anciensdeferney.free.fr/intouch > >