That would be a really good idea, Martin.

I wonder how many problems, frustrations and finally halting paritipation are the direct result of faulty Boinc.

I know from my position here, the major reasons are the multiple and frustrating problems with Boinc and the inability of WCG servers to communicate seamlessly with Boinc. When updating the operating systems around here, Boinc gets automatically updated and then simply does not work. (Our Linux automatically updates the Boinc). Then there's the dash to the forum to determine, hopefully, what is going on and there is never anything of real value relative to Boinc problems. Worse, how many folks don't realize Boinc is the problem?

Often there is not time here to research the Boinc problem further and the easiest thing to do is simply turn the thing off. Unfortunately weeks or months can go by before there is time to work on it again -- and it's usually easy -- simply remove Boinc and go back to a version that works.

Also, there are never any notifications from WCG in email or Boinc when their servers are going down and outdated info is on the forum. Boinc messages usually make little sense in the hands-on end of things.

The new Boinc software should have been tested prior to putting it out there for public download and usage and tested not only for Windows but Linux and Mac. Projects important enough to garner the type of public volunteers for Medical research really should have technical backup to keep things going smoothly. It is a fact that everyone with a computer is not a Tech or Programmer and few have actually tested or written software. The other fact is these projects need those computers and those computer users. The computers, users AND tech support are all equally important.

I would also like to address the word salads that seem to accompany the problems with Boinc. People need to be taught how to report a problem. When software is tested, the technical data of your computer is automatically sent to the Programmers/Network -- if the software testing is done properly. There is no need to repeat this data over and over in forums, and worse it makes no sense whatsoever relative to the problem with software or servers, to those who are reading the forum. People simply want Boinc to work well.

All you have to do is state very simply what is happening in posting to the forums so others with the problem can see it, even if you don't realize Boinc is the problem. Those forums relating to problem issues are being read by folks who are experiencing problems and they are wondering what to do about all of it. Computers deal with and work on simple logic, not jargon. Then hopefully they will also see an answer that gives step by step instructions in simple English, what to do.

The fix is usually going back to an older version of Boinc, as I previously stated, that worked and this is significant for those who are doing research for projects and not testing the software. These two issues -- testing software and working projects of medical research should not be combined unless the volunteer is notified of the combination. Then they know to expect issues. If you don't want the issues that present when software testing you should have the right to say no to testing, and continue on with the projects. Testers can box different operating systems together on one machine and see instantly, for example, that the new Boinc works well with Windows but doesn't work at all with Linux.

I've tested a lot of software over the years and there seems to be way too many stumbles with Boinc that are way too long term at WCG. This is not being critical in a negative way but simply informative. It would be appropriate to reach out to volunteer Testers who understand testing, and halt this business of putting the cart before the horse so everything will run smoothly for everyone. World Community Grid is just too important not to do this. Others who use Boinc seem to be keeping up with their testing and aren't experiencing the difficulties with Boinc that WCG experiences. As is, WCG might just need a volunteer Help Desk as well as Testers.

That said, WCG has to deal with what is likely a Murphy's mix of other servers and magnificent problems that would either give the network people ulcers or lots of excitement. Not all network folks see such issues as great exciting challenges they can dig into with smiles and joy. I am very sure everyone is on their toes all the time, be it grim determination, great frustration, or the challenging joy some of those genius types choose to make it.

Others may not agree with me and I'm simply stating issues that have been presenting around here. It would be interesting to learn what others have to say.

Beth Wells