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.

That's it !
But better than a CPID (how to synchronize ?), you first run the BWT software, you gather all the team accounts on the existing projects (same mail with password check), and you have your BWT ready. Then, it just needs to be automatically created by new projects. You can eventually make it double-checked with a mail send by each project to the team account to confirm the move.

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

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

The man hours to program something like that...

---

Kathryn :o)

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...

Hum, as far as I know, the man hours have already been spent on it as the solution exists.
The only problem so far (to my knowledge) is that the BWT has not been made mandatory on project side.

As the subject is really hot and could even get hotter in the next days, it could be wise to urge the matter.

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.

uh ?
And the discussion leads to what ?

Possibly one more SF/CBT team revealed on Predictor.

Peter

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

The man hours to program something like that...

Hum, as far as I know, the man hours have already been spent on it as the solution exists.
The only problem so far (to my knowledge) is that the BWT has not been made mandatory on project side.

As the subject is really hot and could even get hotter in the next days, it could be wise to urge the matter.

No, the solution doesn't exist. These were just proposals. Having a CPID for the team does NOT solve the problems.

---

BOINC WIKI

One more SF/CBT team revealed on Pirates.

Peter

I will not speak for my team as a whole, but I think most will agree:
We (That's SETI.Germany) have different founders in different projects and like it this way.
We have definitely different team descriptions in every projects and think this is a must, no way to make them all the same.
We have a team in BOINC wide teams as well of course, with an email somehow connected to our URL afaik, but I'm not sure. It's of course just a start, as we prefer real people as founders over dummy accounts.

One of the minus points of BWT is the free distribution of valid email addresses, if BWT will become mandatory this will become even worse. BWT will be a spammers wet dream. So this valid emails have to be something else but the ordinary ones, some account that can be ditched if too flooded.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

BWT is a good idea IMO, just few details...

One of the minus points of BWT is the free distribution of valid email addresses, if BWT will become mandatory this will become even worse. BWT will be a spammers wet dream. So this valid emails have to be something else but the ordinary ones, some account that can be ditched if too flooded.

During the talks about BWT, there was one good idea (I'm not going to look for its exact text now, but may later) about storing these emails just on the BWT server (where the teams and their founders are defined) and newly created projects, which imported the teams, would just ask the BWT server to notify all initial team founders about this event. This step would be pretty simple, email adresses would no be spread around and the founders had trusted the BWT server anyway to store their email adresses there.

It is getting tough with (initial) authentification. As the new project's server has no idea about founder's email address, it would have to communicate with user (e.g. the initial account keys) through BWT server, until the user would store his email address in his new project's user acount.

Peter

Hmmm... Boinc Wide Teams. I like the concept.

But.. How about. Founder is the initial creator of the BWT.
Now, instead of automatically attaching the team to every new project.
Why not this.

I decide I want to start my team off at another project. so I sign up and attach one of my rigs..
I go in to Create the team name there.
Punch in the name. BitBenderTech.
Now the project goes and polls the Boinc DB and finds my team.
Comes up and asks me to verify that Yes this is my team and Dark Angel is the current bossman.
I accept this info as correct and thereby become the "Project Team Manager"
I can now enjoy all the admin privileges for the team at that particular project.
Pretty much do anything the founders can now with the exception of renaming the team.

If the Founder listed on the BWT database leaves and becomes inactive, ONLY one of the managers should be allowed to apply to Boinc Admin to take the foundership of the team. When the request is received, only the Current listed BWT founder and the various project managers need be notified. And they can answer up as to yea or nae on the request.
Now as far as the team manager position, Notify the BWT founder of the "forced change" request or give BWT founder the ability to change (request change) of the project manager.

Two more SF/CBT teams revealed on Rosetta.

Peter

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

Currently, it is especially terrible: at least 3 requests to hand over the privileges and responsibilities of team founder of L'Alliance Francophone (projects SETI, Rosetta and Superlink) during the only latest night for example!

---

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

Currently, it is especially terrible: at least 3 requests to hand over the privileges and responsibilities of team founder of L'Alliance Francophone (projects SETI, Rosetta and Superlink) during the only latest night for example!

It is supposed to be once every 6 months per project at the most. If it isn't, then the project either has old code running, or the code is broken.

---

BOINC WIKI

Hmmm... Boinc Wide Teams. I like the concept.

But.. How about. Founder is the initial creator of the BWT.
Now, instead of automatically attaching the team to every new project.
Why not this.

I decide I want to start my team off at another project. so I sign up and attach one of my rigs..
I go in to Create the team name there.
Punch in the name. BitBenderTech.
Now the project goes and polls the Boinc DB and finds my team.
Comes up and asks me to verify that Yes this is my team and Dark Angel is the current bossman.
I accept this info as correct and thereby become the "Project Team Manager"
I can now enjoy all the admin privileges for the team at that particular project.
Pretty much do anything the founders can now with the exception of renaming the team.

If the Founder listed on the BWT database leaves and becomes inactive, ONLY one of the managers should be allowed to apply to Boinc Admin to take the foundership of the team. When the request is received, only the Current listed BWT founder and the various project managers need be notified. And they can answer up as to yea or nae on the request.
Now as far as the team manager position, Notify the BWT founder of the "forced change" request or give BWT founder the ability to change (request change) of the project manager.

BOINC wide teams still do not really solve the problem.

---

BOINC WIKI

One question:

Is this guy doing this to more than one team per project?

---

BOINC WIKI

One question:

Is this guy doing this to more than one team per project?

Yes, John, he(they) did. (Imagine, would you personally try just one team and had to wait 60 days for another attempt?)

Just follow my links to corresponding projects' threads. (More to come in next days.)

Peter

David Braun has partially fixed team Meisterkuehler.de on Predictor.
The team has its name back, but is waiting to get its original founder back. At the moment of typing it has Michela Taufer as placeholder founder.

---

Both Meisterkuehler.de and Claremont High School Science Department have been fully restored on Predictor.

With thanks to David.

---

One question:

Is this guy doing this to more than one team per project?

Yes, John, he(they) did. (Imagine, would you personally try just one team and had to wait 60 days for another attempt?)

Just follow my links to corresponding projects' threads. (More to come in next days.)

Peter

Did they all get the same name?

---

BOINC WIKI