I am well aware of the current procedure for reporting bugs.

Personally, I would prefer to see a forum or some other much more simplistic means of reporting bugs for BOINC.

Such a means would likely help the average person in the following:

1. Searching to see if anyone else has already reported the issue
2. In general, reporting any bugs

---

I am well aware of the current procedure for reporting bugs.

Personally, I would prefer to see a forum or some other much more simplistic means of reporting bugs for BOINC.

Such a means would likely help the average person in the following:

1. Searching to see if anyone else has already reported the issue
2. In general, reporting any bugs

Agreed.

I would add

3. Having the best possible chance of the developers fixing said bug.

I am aware of four distinct methods of reporting bugs:

A: Posting on this board
achieves (1) and (2), fails (3)

B: Filing a trac ticket
achieves (1), poor results for (2) and (3)

C: Posting to boinc_alpha mailing list
fails (1), moderate results for (2) and (3)

D: Having a quiet word in Jord's ear
Best results for (3), fails (1) and (2) abysmally

:-)

Well, I'm glad that I did not post to the boinc_alpha list as it would have only added to my frustration. ;)

Its unfortunate that for whatever reason, there is no burning desire to fix some of the issues that many are reporting.

One of the other attitudes that I find extremely frustrating is that many projects are run with a we don't care if your computer is spending valuable wasted time on WUs and has problems with them. Some other computer will finish the task regardless.

IMHO - there's no respect for people who donate valuable electrical power and processing time. Then again, I guess I sound like Rodney Dangerfield. :O

---

Its unfortunate that for whatever reason, there is no burning desire to fix some of the issues that many are reporting.

The reason is simple: Too many problems, too little time, too few good men. May I remind you that the whole of the BOINC development team consists of 3 people, one of which is only part-time busy with BOINC. There are a couple volunteer developers as well, but nothing major.

There are plenty of bugs still open, while new ones are added every now and then. If not through Trac, then through the by you so despised alpha email list.

I know the to do list of one of the developers, it's really a wonder that he still has time free for other things than programming BOINC 24/7. But apparently, that's what you want them to do. Family, friends, pets, eating, sleeping, household, shopping, vacations.. should be abolished? For what? A piece of software that most of the time does exactly what it says on the tin?

Why not read up on its design for once? BOINC whitepaper (PDF).

---

Its unfortunate that for whatever reason, there is no burning desire to fix some of the issues that many are reporting.

The reason is simple: Too many problems, too little time, too few good men. May I remind you that the whole of the BOINC development team consists of 3 people, one of which is only part-time busy with BOINC. There are a couple volunteer developers as well, but nothing major.

There are plenty of bugs still open, while new ones are added every now and then. If not through Trac, then through the by you so despised alpha email list.

I know the to do list of one of the developers, it's really a wonder that he still has time free for other things than programming BOINC 24/7. But apparently, that's what you want them to do. Family, friends, pets, eating, sleeping, household, shopping, vacations.. should be abolished? For what? A piece of software that most of the time does exactly what it says on the tin?

Why not read up on its design for once? BOINC whitepaper (PDF).

Well, today I was doing something completly far from "Boincing" and gave Boinc a couple of thoughts...

I know you've let me know that doing Boincing should be easy for the user.
But the more I learn about how this functions the more I understand that with 70+ Projects and many hardware platforms, CPU and CPU(NCI) and Virtualmachine implement and differnt type of GPU's that are combined in alot of different users way of setting different projects different functions together and want to be part of this and make their own best volountering participation as good as it can be.

And you here let us know that there are 3 guys working their buts off in trying to get this to work. I thought that there where more of them doing this.

I can't do the programming so I will continue to do what I can and that is reporting any bug I find and give it the best discription I can.

Best of luck with version7 and everything it can accomplish in the future.
It has alot of potential I'd say if alot of the bugs gets fixed.

//TRuEQ

---

TRuEQ & TuVaLu