verhaaltje van dave anderson
"I got a request to change the team credit policy:
A) (current policy in both SETI@home and BOINC)
A team's credit is the sum of its users'.
When a user changes teams, his total credit is moved also.
(proposed)
A team's credit is the total credit granted to users
while they belong(ed) to the team.
When a user changes team, the old team keeps his credit.
From a technical point of view, A) is a little easier.
To implement
we'd have to add a new field (teamid)
and a new index to the result table.
From a participant's point of view I'm not sure which is best.
If anyone has strong feelings, can you please email
(to me or the list) your reasoning?
Thanks -- David" (Anderson)
_____________________________
Update:
"After considering people's input on the team credit issue,
we've decided to use policy B.
In this policy, when a user belongs to a team and earns credit,
that credit is added to the team's total,
and the team keeps the credit even if the user leaves the team.
This provides a stronger and more meaningful form
of team identity and competition because "team-hopping" users
cannot cause team totals to suddenly decrease.
To implement this, we added a "team ID" field to the database result table; it records the team ID of the user at the time the result is reported.
This field will enable us, if necessary, to reconstruct the
team totals in case they get out of synch.
Team recent average credit is computed the same way as for users and hosts;
if a team becomes inactive, its recent average credit
will eventually decay to near zero.
Team credit accounting (to reiterate) is independent of user accounting.
A user't credit total includes all granted credit,
regardless of team membership.
-- David"
"I got a request to change the team credit policy:
A) (current policy in both SETI@home and BOINC)
A team's credit is the sum of its users'.
When a user changes teams, his total credit is moved also.
A team's credit is the total credit granted to users
while they belong(ed) to the team.
When a user changes team, the old team keeps his credit.
From a technical point of view, A) is a little easier.
To implement
and a new index to the result table.
From a participant's point of view I'm not sure which is best.
If anyone has strong feelings, can you please email
(to me or the list) your reasoning?
Thanks -- David" (Anderson)
_____________________________
Update:
"After considering people's input on the team credit issue,
we've decided to use policy B.
In this policy, when a user belongs to a team and earns credit,
that credit is added to the team's total,
and the team keeps the credit even if the user leaves the team.
This provides a stronger and more meaningful form
of team identity and competition because "team-hopping" users
cannot cause team totals to suddenly decrease.
To implement this, we added a "team ID" field to the database result table; it records the team ID of the user at the time the result is reported.
This field will enable us, if necessary, to reconstruct the
team totals in case they get out of synch.
Team recent average credit is computed the same way as for users and hosts;
if a team becomes inactive, its recent average credit
will eventually decay to near zero.
Team credit accounting (to reiterate) is independent of user accounting.
A user't credit total includes all granted credit,
regardless of team membership.
-- David"