TAS-member thread: December 2005

[petrusbroder]

Bump - please do get your vote registred @ TAS!

 

[GLeeM]

Now that you've had time to think about it, it is time to vote!

We could use some new members also

 

[rise]

voted

 

[mrwizer]

Me too.

 

[BlackMountainCow]

Morning coffee bump

 

[petrusbroder]

The evening before Christmas Eve Bump - please vote if you are a TAS-member, please join if you want to have fun and crunch with TAS!
Links see above!

:beer:

 

[petrusbroder]

The Christmas Day bump - and some news:

The TAS-January-project-poll is just now very interesting indeed:

6 votes for DPAD
6 votes for Rosetta@Home

This needs resolution - please come and vote here at TAS!

All members young and old: come and join the fun!
All crunchers wanting to help the Team Anandtech Sentinels mini-team to place TA high in the list: Join TAS first and vote then!

 

[rise]

merry christmas all!! :beer:



(i may change my vote if i can out muscle the pollsters. not today of course, the day of good cheer, maybe tomorrow )

 

[GLeeM]

Look what I found!

Welcome to TAS - *TA Sentinel*

Thanx to all who have joined up to make this possible! Together we WILL make a difference!

The main goals of TAS will be to
1. Increase TeAm AnandTech's participation and production in projects.
2. Introduce people to projects they're not so familiar with.
3. Have LOTS of fun!
4. Establish TeAm AnandTech as a major player in all that is DC.

We'll do this by movin between projects, participating in each for 4 weeks at a time. After starting each new project, the next upcoming project is voted for by TAS members and added to the Rally Schedule.

This RallyTeAm is known as "TA Sentinel", but members will crunch under their own individual names.
We hope to keep this as exciting as possible and to bring the TeAm even closer together!
This can only be accomplished if there's enough interest and support.

 

[petrusbroder]

Thanks GLeeM for the quotation from sometime August 2004! I have missed that post:
Go TAS, Go! :thumbsup:

 

[Insidious]

Great rules post GleeM! glad you found it.

The thing about new projects is that they need a lot of coddling and support while they get through their growiing pains. If we can do that, it would be great. If not, maybe we should stay with safer projects.

I would be embarassed to go to a new project and see it ripped to shreds by TAS members if a flaw were found.

just my $.02

-Sid

 

[petrusbroder]

Originally posted by: Insidious
Great rules post GleeM! glad you found it.

The thing about new projects is that they need a lot of coddling and support while they get through their growiing pains. If we can do that, it would be great. If not, maybe we should stay with safer projects.

I would be embarassed to go to a new project and see it ripped to shreds by TAS members if a flaw were found.

just my $.02

-Sid

That is why we - you and me and the others - vote. The TAS-members look, test, read, check and vote. OTOH: Is not TAS very well qualified to check and test the projects? As a kind of scouts, testers, early adopters for TA - at the same time establishing TA in the rankings? Each members decides, there have always been enough members to put a projects through it's paces. It is better that a mini-team finds the problems before the whole TeAm gets committed.

Part of the fun are stats. For me (IMHO) the learning part is second most fun. It is also good for the cruncher: "been there, done that."

I myself have been with seti (under two different names) for 5 years. The last year I have tested 9 different projects, 7 of those I have run more than 1 month; one of them for only one week - I did not like that one ... I know quite a lot about these 9 projects and I have learned most in these forums, and from other sources on the net. Considering the hours I've spent at the computer - that has been well spent time: I think among others of SirUlli's news ... , Rattledagger's about BOINC, seti, and many other projects , GLeeM's and MDE's knowledge about F@H

, BMC's about Rosetta :thumbsup: :beer: :thumbsup:, mrwizers about Einsten and CPDN :sun: . That gives me joy!
Certainly a very good year crunching-wise!

 

[Insidious]

No one doubts the expertiese or experience of any TAS member.

I was pointing out that critique and review is a VERY different function from team building.

I like "team building", but want no part of critiquing projects and/or influencing membership especially in a negative way.

Many TAS participants are also major figures in other projects and are heavily involved in recruiting for those projects. When these figures are seen criticizing a project other than their home project it can appear a little 'self-serving' and hence... embarassing.

I believe TAS has an obligation (especilly seeing the "charter" GleeM posted) to either remain positive or else remain quiet as they travel from project to project.

but of course, opinions are a dime a dozen and mine is only one of many differing ones.

-Sid

 

[petrusbroder]

Originally posted by: Insidious
No one doubts the expertiese or experience of any TAS member.

I was pointing out that critique and review is a VERY different function from team building.

I like "team building", but want no part of critiquing projects and/or influencing membership especially in a negative way.

Many TAS participants are also major figures in other projects and are heavily involved in recruiting for those projects. When these figures are seen criticizing a project other than their home project it can appear a little 'self-serving' and hence... embarassing.

I believe TAS has an obligation (especilly seeing the "charter" GleeM posted) to either remain positive or else remain quiet as they travel from project to project.

but of course, opinions are a dime a dozen and mine is only one of many differing ones.

-Sid

I do not think that we differ in our opinions about what TAS should do and not. However, lack of positive comments also denotes an opinion... What is needed is information - not opinions - to decide which project to vote for. TAS has never - AFAIK - ripped any project to shreds. That is not - and has never been - any aim of TAS'.

What I mean by TAS being "scouts, testers, early adopters" is to find the way for others to follow - to find all the small (or big) tricks, fixes and shortcuts so that a project can be successfully crunched. If you read the posts at TAS there is AFAIK no negative word or critique about any project. The comments there look like this:

"Is there a current info page (about outages, problems, bugs, etc)? No. " or
"For the moment the project is unable to bypass proxies" or
"I have not been able to upload WUs for the passed xx hours. This s...s"

That is not critique. That is current and accurate information. Or rather: it was accurate and current at the time of posting Based on such info the TAS-members can form their opinion and then vote. Unfortunately we have not been able to compile that much on the different projects, most info consists of links to the different sites. I think that helps too. What then individual members post is of course and as usual their own responsability. The moderating team does it's best to keep the worst language off the site.

 

[Insidious]

I couldn't agree more Peter.

Actually I was addressing what could potentially happen if we went to a new, imperfect project while actually doing that project... not the discussions that take place before hand.

I am concerned that if a flaw were to present itself in any developing (immature) project we chose, it might evoke reactions from TAS members that could be detrimental to the survival of that new project. Which could be embarassing as they could be misconstrued as 'self serving' if that reaction were to come from someone actively recruiting for some other project.

I've seen several posts of DCers who are not comfortable crunching for a project unless it is flawless.... with this being the case, I am suggesting TAS should either be prepared to bite their lips if we find a flaw in a new project or else stick with safer ones.

-Sid

 

[petrusbroder]

I prefer the "bite the lips" and find out what the potential is ... than to stick only to tried and known projects. But that is my attitude,
OTOH: If TAS-members find a problem with a project, communicate that to the project coordinators - developers - scientists, who then can remedy the problem, then all have gained ...
We are talking about feed-back to the developers, with potential for improvement; not about discouraging other crunchers.

 

[Crazee]

I think you both agree on a lot of things. What I think is important is the reaction of the project devs to that criticism. If a project does have problems and the devs don't react, I want to know. As a person who is arguing hard to have DC running in my production work environment, I can't afford to be made to look like an ass if there are problems that the devs don't have any intention of actually fixing. I can do it with my home machines, but I can't commit work resources to something that could get me fired.

Therefore if TAS can provide me with experiences and feedback on the devs of a project then :beer::beer:

 

[petrusbroder]

Hmmm, still only 12 votes in. And the poll is tied!

Come and have your say - vote in the January-project poll!!!

 

[BlackMountainCow]

It's actually hard to say if that's a tie or not:

Pro DPAD: 8
Pro non-BOINC: 7

Pro Bok's challenge (= Rosetta): 4
Pro BOINC: 2
Pro Rosetta: 6

Now, how do you calculate a tie Peter?

As the possibility exits, that people actually voted twice, e.g. Pro BOINC and then pro Rosetta, the Pro/contra BOINC votes don't seem to be significant. Others could have voted for a project but not pro/contra BOINC. That's actually the case: We have 14 project votes but only 9 platform votes.

So, do only the Rosetta / DPAD votes count? Because then it's DPAD right now by two votes.

But what to do with the Bok votes? Count them towards Rosetta? Exclude them because the challenge itself wasn't accepted by TAS?


You're the math guy, Peter!


In the future, maybe we shouldn't put up triple votes like that where people can actually vote more than once. Just a plain list of all projects TAS didn't do yet, regardless of the platform.

EDIT: Another vote came in, so I adjusted the numbers.

EDIT2: Now I see how you got a tie Peter. You only had 12 votes but by the time I took a look at the numbers there were 13 already. Now it's 14. DPAD leads by 2.

 

[petrusbroder]

When I posted it was only 12 votes.
When it was a total of 12 votes, the 6 were for DPAD and 6 were for Rosetta. That was the tie.
Out of the 6 for Rosetta 4 were for the Bok's challenge, 2 were for BOINC-projects.
Good that the tie is broken.

BTW I agree, next time it will be only only projects which TAS has not done yet. But even that will be hard: there are so many projects around that 20 options are not sufficient. We have to discuss that in the mod-team.

 

[rise]

Originally posted by: petrusbroder
BTW I agree, next time it will be only only projects which TAS has not done yet. But even that will be hard: there are so many projects around that 20 options are not sufficient. We have to discuss that in the mod-team.

simap?

 

[petrusbroder]

Will be on the poll ...

 

[petrusbroder]

The poll is now 8 for DPAD and 6 for Rosetta@Home. Please vote, if you have not before this!

 

[petrusbroder]

Do not forget to vote on the poll:
14 votes are in.
8 for DPAD, the other 6 for Rosetta.

The poll will close in about 26 hours - 18:00 UTC, so please vote! :thumbsup:

 

[Freewolf]

http://free-dc.org/forum/showthread.php?p=97292#post97292