Nice Mockup. Both have been asked for before.

1) CPU/OS info in addition to the client version [which was also a member request], adds to help the DIY diagnoses wihout compromising the anonymity of the quorum members.

2) You forget to amend the text in the ''If there is ..." to read as tertiary choice. Coupled to that, there was the proposition of not sending 2nd and backup work unless the cache was getting empty. This way, should a project temporarily go off line, the client would not start fetching the alternates... in my case, had enough GFAM to easily bridge yesterdays 7+ hour interruption. Of course this would only work if crunching only for WCG. As it is, old, new and upcoming clients just always try to fill the cache [the unhappy way of how backup projects with zero resource / project weight is currently functioning... to me they too are not to be called on until the systems threatens to go idle, and only ask for 1 per core, being kept outside the debt system]

edit: (not wishing for this forum to become an extension of the BOINC forum where this discussion may better belong)

--//--

i wish there were badges after blue

The blue will be along before you know it, but it's a long time between 1 year and 2 years. If you have more than one CPU, you can throw multiple cores at one project to get a badge faster.
(At the moment, I am doing that with HCC to flip it from green to blue.)

The time needed until the next badge can be derived from the statistics display, if you know the requirements for each badge.
http://wcg.wikia.com/wiki/Project_badges

All are the same except for the completed AfricanClimate@home

14 days = bronze
45 days = silver
90 days = gold
180 days = ruby
1 year = emerald
2 years = sapphire

Higher badges have been asked for, but the priority to deal with it is lower.

There have been a lot of projects activated and running simultaneously, which isn't bad either, from the science viewpoint. The group has spent most of their time dealing with the data requirements and programs.

Would also be nice to see how much runtime is added to each project we contribute to. Example:

12 hours C4CW
5 days HFCC

Tomast, like your idea but instead of check marks, have a digit. 0 for do not crunch, 1 for your priority wu's you want to crunch , 2 if the priority is suspended for what ever reason. Would help out allot for folks concentrating on one particular project. Have ran dry a few times because a project went down and didn't know for a few days.