Posts by LoCatus

1) Message boards : Questions and problems : Stolen Team. (Message 18582) Posted 17 Jul 2008 by LoCatus Post: So what should TA's be able to do? This is what they can do now: You can select team members as 'Team Admins'. Team Admins can: * Edit team information (name, URL, description, country). * View the team's join/quit history. * Moderate the team forum, if any (admins get emails notification of moderation events and red X reports). Team Admins cannot: * Change the team founder. * Remove members. * Add or remove Team Admins. If a Team Admin quits the team, they cease to be a Team Admin. I like the idea of a project specific description, but the URL, Name, and Country should be founder only options. Also there should be only one admin for the team at a project. (Founder should also have admin control at the project level) Just how automated is the current founder change system? Because the way I see it, Founder / TA changes should not need to be automated anymore. As under this idea, only the founder can boot a ta, and only the ta's can approve a "forced" founder change. A Boinc admin (or designated person) will still be required to make the actual change. If neither the current founder or any of the project TA's can be contacted, then there can be no change. (Hijacker go start your own team) OT, I like your avatar. Original. :-) HeHe.. LoCatus? I created him as a joke a few years back during a StarTrek conversation at the now gone grid.org forums. (I was using the cat with the lime for a helmet for an avatar... he got assimilated) And so far, as far as I know, if you see him about, It'll be me typing.
2) Message boards : Questions and problems : Stolen Team. (Message 18579) Posted 17 Jul 2008 by LoCatus Post: Joining a team would still be possible through any individual project. Just changing of the team founder needs to be done through BWT. (Right?) That's the idea.. Also by Boinc only needing to notify the current founder and various project team managers, it greatly reduces the number of emails needing to be sent while still trying to inform members of a possible hostile takeover bid. Of course if BWT founder and all the team managers are the same person, It would kinda defeat the purpose. So we would have to make sure we have other peeps doing the manager bit at the projects. [edit] It could also speed up the founder change if a few of the manages reply approving of the change.
3) Message boards : Questions and problems : Stolen Team. (Message 18576) Posted 17 Jul 2008 by LoCatus Post: BOINC wide teams still do not really solve the problem. Let's not forget this is not only a Boinc problem, but a community problem as well. The various teams also have some responsibility in keeping things current in regards to who is team founder and trying to keep track at the various projects. By utilizing the BWT founder and project manager scheme, This makes it easier for the team to keep an eye on things across numerous projects even if they are not actively working at them. The BWT founder has the responsibility that if he/she leaves the team, getting a replacement on the way out the door. Only the team founder should be allowed to change the team name since it will affect the team across ALL the projects. (Quick indicator to the rest of the members that something's up) BWT founder should also be the only one able to boot/fire/force replace a team manager. (Managers should have the ability to resign their position giving it to another member) Will it completely rid us of the possibility of our teams being hijacked? Probably not. But it will make it MUCH harder for these cheaters to do so.
4) Message boards : Questions and problems : Stolen Team. (Message 18528) Posted 16 Jul 2008 by LoCatus Post: 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.

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.