Questions and Answers :
Wish list :
Team Captain Woes...
Message board moderation
Author | Message |
---|---|
Patrick Blanchard Send message Joined: 10 Jun 99 Posts: 6 Credit: 472,210 RAC: 0 |
I am the team manager for Seti-Quebec on classic Seti@Home. (http://setiathome.berkeley.edu/stats/team/team_1007.html) I need the same privileges on SetiBoinc. (http://setiboinc.ssl.berkeley.edu/sah/team_display.php?teamid=30243) Who do I talk to? I am member 42272. -Patrick http://seti-quebec.org http://boinc-quebec.org |
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 |
Since you can activate your old S@H account, I would assume that this would also re-instate your team leader status. But then again, this feature might not be fully operational until project launch. There are many things not yet ready for public consumption. Give it a few weeks. |
Patrick Blanchard Send message Joined: 10 Jun 99 Posts: 6 Credit: 472,210 RAC: 0 |
I am not the team founder. So I didn't get the privileges he has. He stopped crunching and never came back. He is now un-reachable. Am I/we out of luck? I'd like it if an admin would contact me. We could sort this out together. -Patrick > Since you can activate your old S@H account, I would assume that this would > also re-instate your team leader status. > > But then again, this feature might not be fully operational until project > launch. > > There are many things not yet ready for public consumption. Give it a few > weeks. > |
Doris and Jens Send message Joined: 21 Nov 99 Posts: 362 Credit: 3,539,386 RAC: 13 |
> Am I/we out of luck? I did't believe. We had the same problem two years ago and Berkeley staff help our team. But it is a critical doing to take over a team and I would think that this is not the right time to check it. They are very busy at the moment. You should write a mail to them when the when the situation is a little bit more stable, some time after the public launch. Greetings from Bremen/Germany Jens Seidler [url=http://www.boinc.de/] |
Patrick Blanchard Send message Joined: 10 Jun 99 Posts: 6 Credit: 472,210 RAC: 0 |
Thanks, I will. |
Team AUSTRALIA (AlexD) Send message Joined: 1 Jun 99 Posts: 54 Credit: 66,602 RAC: 0 |
-- Posting appeared twice for some reason -- |
Team AUSTRALIA (AlexD) Send message Joined: 1 Jun 99 Posts: 54 Credit: 66,602 RAC: 0 |
This I suspect is not an uncommon problem, the team founder of my team ( Team AUSTRALIA = http://setiweb.ssl.berkeley.edu/team_display.php?teamid=30463 ) has also gone MIA (since Feb 2003). I would be happy to take on the role, but again, not being the founder I am unable to e-mail our missing founder. I could easily see a SETI admin spending alot of time hand-editted (ugh!), if we're talking wish lists, perhaps some sort of "vote for me" process could be implemented (post-launch workload "spike"). Thinking along the lines of a team member can put themselves forward, this would be shown on the team-stats page. Then other members can either add their vote to that member or put themselves forward. Votes have a time limit (either hard set to say 8 weeks or user selected), and only if a memeber recieves 60% of the votes would "founder-ship" transfer. Also, have a limit on the number of times a member can put themselves forward in any one year (to discouage abuse or "vote wars" developing between two or more members). Once in place, the SETI admin would only need to get involved as an arbitrator in the event of a dispute. Would this be implementable? Is there a fairer way to do this? |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
> This I suspect is not an uncommon problem, the team founder of my team ( Team > AUSTRALIA = http://setiweb.ssl.berkeley.edu/team_display.php?teamid=30463 ) > has also gone MIA (since Feb 2003). I would be happy to take on the role, but > again, not being the founder I am unable to e-mail our missing founder. > > I could easily see a SETI admin spending alot of time hand-editted (ugh!), if > we're talking wish lists, perhaps some sort of "vote for me" process could be > implemented (post-launch workload "spike"). > > Thinking along the lines of a team member can put themselves forward, this > would be shown on the team-stats page. Then other members can either add > their vote to that member or put themselves forward. Votes have a time limit > (either hard set to say 8 weeks or user selected), and only if a memeber > recieves 60% of the votes would "founder-ship" transfer. Also, have a limit > on the number of times a member can put themselves forward in any one year (to > discouage abuse or "vote wars" developing between two or more members). Once > in place, the SETI admin would only need to get involved as an arbitrator in > the event of a dispute. > > Would this be implementable? Is there a fairer way to do this? > First step would be to send an email to the current founder/manager and ask if that person wanted to continue the role. If no response within X time, or a no answer, then institute the process of polling for volunteers, and voting. This reduces the turnover to something manageable. |
Team AUSTRALIA (AlexD) Send message Joined: 1 Jun 99 Posts: 54 Credit: 66,602 RAC: 0 |
> First step would be to send an email to the current founder/manager and ask if > that person wanted to continue the role. If no response within X time, or a > no answer, then institute the process of polling for volunteers, and voting. > This reduces the turnover to something manageable. That works and at least gives the founder a heads up. Would need to define what triggers a founder-ship dissolution e-mail. Perhaps have some sort of regular process which queries the appropriate database for (a) members who are team founders and (b) no activity for 3 (6?) months and (c) not already awaiting reponse to an e-mail, for the records that come back, send an e-mail and mark in their account details that an e-mail has been sent (for part-c above, so founder isn't flooded). (Possibly need some sort of re-send after 14 days counter to allow for SMTPs non guaranteed delivery nature, in case the founder doesn't receive the first message). Then if the e-mail returns as failed due to address no longer exists, or no response is recieved after 6 (8?) weeks, triggers the voting mechanism. |
Patrick Blanchard Send message Joined: 10 Jun 99 Posts: 6 Credit: 472,210 RAC: 0 |
|
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.