I think the only question is: what is Berkeley waiting for ???

Nobody is waiting for anything, they have been discussing a solution for a week in the mailing lists.

I think the only question is: what is Berkeley waiting for ???

The man hours to program something like that...

Hi all

Any team founder can attest there are several attempts a year on every project to take control of their team.

As new projects show up, it tends to become a full time job to control every founder account on all projects.

At the moment, when a new project shows up, anyone can found a team with the name he wants. I'm from the Alliance Francophone and I can create Seti.USA or Seti.Germany or any other team I want (which I would not). By doing this, I would either have the control over Susa or SG members, and/or make it impossible for these teams to participate to the project. As far as I know, this never occured ... so far. But it remains possible.

Boinc Wide Team is the response to this. A unified team account across all projects. So there is only one account to control, and the teams are automatically created on every new project that shows up.

There are over 60 projects out there and it is time Berkeley takes this into consideration before very serious damages occur.

Boinc Wide Team exists. It doesn't work so far. Make it work and make it mandatory to every existing project and new comers.

To conclude, the problem already exists and starts to cause damages. The solution already exists. So what is Berkeley waiting for ???

Hmm. An interesting idea. Each BOINC wide team has a team CPID. If it was created from the BOINC wide team it would be set from there automatically. If it was created as a local team, it could be set from a hash that is only available to the founder in some other project.

Now to the earlier proposals of JM7 and Ananas:
3) Send all users an email a short time (2 weeks) before the transfer is to become final due to an inactive founder. This should give enough time for the team members to appeal to the administrator to allow or disallow the foundership change.

No way.
May be OK for small teams up to 5 people, but for our team it would be impossible on a lot of projects. It would simply be spam if this would have happened, perhaps just because the mailing system whas not worked.

The largest team is still only a few thousand, so projects should be able to handle sending that number of emails. Some projects send a monthly newsletter successfully. Sending targeted information to interested users isn't SPAM, and it is only one email per user.