Just posted THIS over at Einstein BTW.

Another team has been successfully recovered at SIMAP

There are lots more still though.

Have a look at this at PREDICTOR BTW guys.

And THIS

TEAM MOVEMENTS

Unbelievable the amount of members of the original team that got thrown out by the "Space Family" on the same day.

This guy really is a "piece of work". I'll assume this has been called for more than once already, but I suggest Barbar be banned from any and all BOINC projects and this parasitic team of his as well. His antics are causing nothing but anger and frustration on every project he touches, and it seems pretty obvious to me that he has no regard at all for what we as a community are trying to achieve. ie the betterment of all mankind through sharing computer resources.

---

Team Bitbendertech

I have a couple of possibilities for permanent solution.

1) Allow projects to easily require admin permission for a team founder transfer that is not done by the current team founder.

2) Send an email to the team founder on a weekly basis to remind of the pending foundership transfer. This solves the upgrade problem as well.

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.

4) Send an email to any user that is kicked off a team.

5) Do not allow these emails to be turned off.

I talked with David A and he indicated that he did not see the need for a complete revamping of the foundership change mechanism, but he would entertain a check in from a volunteer.

Is there any discussion about what should be done?

---

BOINC WIKI

6) Place a note on the team page that a founder change is pending, including the account of the person who requested it.

7) Make it all this stuff a lot easier and faster, when the current founder is not in the team anymore _OR_ (for the founder) deny leaving a team without having choosen a new founder first


I'm not sure how this is handled at the moment ... but there might be the need for :

8) Cancel the foundership request from a person, who leaves the team

9) Allow only one foundership request per person per year

Those 8) and 9) will not allow people to jump from team to team and request founderships everywhere, hoping that at least one founder is sleepy


... plus this one maybe :

10) Allow team admins to deny a founder change too and include them (CC:) in the change request notification

Dont allow accounts to be created that do not have any computers registered with that account, as these type of accounts do not show up in the stats and will never show any credit and can be used as placeholders to highjack multiple teams on the same project.

Dont allow accounts to be created that do not have any computers registered with that account, as these type of accounts do not show up in the stats and will never show any credit and can be used as placeholders to highjack multiple teams on the same project.

I often create accounts on projects with no Linux application yet, so no need to attach a computer, but I will still found our team if it's not there already.
I think I'm more then once the founder of SETI.Germany n some smaller projects without an attached computer and without a single WU crunched.

On some mor dubious looking projects it's fine to first ask some questions on the forum before attaching your computer to the project in the BM, as you first want to be sure not to get some trojans installed via BOINC.

Every account created via the (for me) normal way on the home page (project.url/create_accout_form.php) direct or via boinc wide teams will start without a computer attached.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Good point Saenger.

Maybe not allowing accounts with no computers attached to apply to change an already existing foundership.

Now to the earlier proposals of JM7 and Ananas:

1) Allow projects to easily require admin permission for a team founder transfer that is not done by the current team founder.

So project admins need to engage in this actively?
Dunno how often it's nedded, but looks quite OK if they have the time and don't click on "OK" without looking.

2) Send an email to the team founder on a weekly basis to remind of the pending foundership transfer. This solves the upgrade problem as well.

Two-weekly should be sufficient, not too much mails please.
And include direct links to the deny function.

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.

4) Send an email to any user that is kicked off a team.

Fine with me.

5) Do not allow these emails to be turned off.

I could agree with it. I don't see any spammer lurking in the backyard here.

6) Place a note on the team page that a founder change is pending, including the account of the person who requested it.

Good idea.

7) Make it all this stuff a lot easier and faster, when the current founder is not in the team anymore _OR_ (for the founder) deny leaving a team without having choosen a new founder first

I have used this ability once @malaria, where I was the founder and crunched for the memorial team of Dogbytes for two month. I could easily have changed the foundership to someone else, not much hassle.

8) Cancel the foundership request from a person, who leaves the team

Definitely!

9) Allow only one foundership request per person per year

Good idea, dunno how to implement it, and of course it has to be done per project ;)

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Good point Saenger.

Maybe not allowing accounts with no computers attached to apply to change an already existing foundership.

It's a good idea.
If I could not ask for founder transfer without a puter attached it's fine, as long as the founder could make me founder in every case on his doing. Actions of the (real) founder should not be restricted by this, just the ability of rough members to get this status illigitimate.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Seems good to me Saenger.

Make it more difficult to change a team name, as Scribe suggested elsewhere, while still keeping it as automated as possible for the sake of the project admins and give those admins a history of all founder change applications, actual founder changes, and team name changes etc, that they can quickly and easily check incase of disputes.

Maybe a few more ideas, mentioned elsewhere:

11) Create a team subpage, which would list a history of team's previous names and its founders' (their ID + (historical, not recent) names in text form) and dates of the changes. Legitimate team members might find this annoying, but I believe that public availability of this data might block future hi-jackers from their business. And I believe that on most cultivated and legitimate projects there would be just one to a few of entries.

12) Don't allow (placeholder) users with no credit to request team foundership - such cases might rarely happen on starting alpha/beta projects or those without regular work available, but I believe would be realy rare and could be solved by project admins. This would not restrict team founders doing foundership transfers on their will, even on projects with no work at all.

Peter

Can't we integrate BOINC Wide Teams into this somehow?

It's not used by any projects at this moment, or at least, I've not found any new projects lately that were using it. I always have to make my team afresh. Only Orbit used it thus far, afaik.

So isn't there a check that can be done through BWT that active team founders have to react on, while afterwards projects pick up this latest data again? Just brain storming.

---

Can't we integrate BOINC Wide Teams into this somehow?

It's not used by any projects at this moment, or at least, I've not found any new projects lately that were using it. I always have to make my team afresh. Only Orbit used it thus far, afaik.

There were some at 10 projects, which created me and my BWT. At least I have 5 notification emails available and there were some more, which sent no notification about.

Peter

Can't we integrate BOINC Wide Teams into this somehow?

It's not used by any projects at this moment, or at least, I've not found any new projects lately that were using it. I always have to make my team afresh. Only Orbit used it thus far, afaik.

So isn't there a check that can be done through BWT that active team founders have to react on, while afterwards projects pick up this latest data again? Just brain storming.

I've got 14 mails with a header like:
"Team created on IBERCIVIS - public alpha version"
and the content:

An instance of the BOINC-wide team 'Saenger Sein Super-ATA Team'
has been created on the project:
name: IBERCIVIS - public alpha version
URL: http://registro.ibercivis.es/

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

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.

---

BOINC WIKI

Do we have a volunteer to program this? My knowledge of PHP is nil.

---

BOINC WIKI

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

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.

Well, I can only speak for my team (L'Alliance Francophone) : we're close to 10 K members ;)
OK, all members do not participate to all projects. But there would be thousands of mails to be sent on many projects. Projects admins would need to seriously work to overcome spam filters....

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.

---

BOINC WIKI