SmashWiki talk:Requests for adminship/Archive 1: Difference between revisions
SmashWiki talk:Requests for adminship/Archive 1 (view source)
Revision as of 19:41, September 16, 2008
, 16 years ago→Arbitrary page break
Line 184: | Line 184: | ||
I have a few things that I feel must be added to this discussion simply to clarify some of my previous points. First, I only said to contact the wikia staff because continuing the argument here means absolutely nothing. I did not and still do not support this policy in any way, shape, or form. Secondly, I understand that there are certain concerns about sysops having seemingly unlimited power. However, giving the community at large (and especially editors who have not contributed a single main-space edit to this wiki) the ability to recall ''all'' sysops at any time for the actions of one seems not only silly, but potentially suicidal for the wiki. As Kirby King rightfully said, there are and always will be some ill-will felt against sysops even when their powers are used correctly. Contrary to what DE said earlier in this discussion, the sysops' primary concern cannot always be what is the most popular decision, but what is the best decision for the wiki. Obviously, sysops cannot have ivory tower views that they and they alone know what is best for the wiki and that everyone else just exists to do their bidding, but sometimes the unpopular choices have to be made. For example, about two months ago, if we had let the popular decision of all the users stand, this would no longer be an encyclopedia, but another chat room and social networking service. Obviously, that is not the purpose (or primary purpose) of wikia. As sysops, we had to step in and make the unpopular decision that was best for the wiki. This is true of all leadership/management/administrator roles. If sysops could be expelled simply because the users didn't like a single decision that they made, we would not have any sysops left. Third, I again agree with Kirby King that a reelection system that begins by removing all current sysops powers and treating all RfAs the makes no sense. As even the proponents of this measure have indicated, there is really only one problematic sysop ''at most''. To recall all sysops and make them reapply is not only unfair, but completely baseless. Also, to clump all the sysops in with other users trying to get RfAs would take forever. Who's going to manage the wiki while it all gets sorted out? And who is going to arbitrate this? Two editors who have done nothing to improve the content of this wiki? Finally, do you really think that we have not at all tried to quell this problem internally. As SC said, it appears that you have not even bothered to read all of the conversations that have been happening, nor have you bothered to look at the surrounding events. And there is no way you could possible know everything seeing as you do not have access to my IM or e-mail conversations. Trust me, if you still want to go down this road and (on the off chance) Angela goes along with it, I'm ready. I just hope everyone (except DE and Warwick as they are already convinced they are right) understands that it is uncalled for, dumb, and potentially suicidal to this wiki. [[User:Clarinet Hawk|Clarinet Hawk]] <small>([[User talk:Clarinet Hawk|talk]] · [[Special:Contributions/Clarinet Hawk|contributions]])</small> 16:16, 23 August 2008 (UTC) | I have a few things that I feel must be added to this discussion simply to clarify some of my previous points. First, I only said to contact the wikia staff because continuing the argument here means absolutely nothing. I did not and still do not support this policy in any way, shape, or form. Secondly, I understand that there are certain concerns about sysops having seemingly unlimited power. However, giving the community at large (and especially editors who have not contributed a single main-space edit to this wiki) the ability to recall ''all'' sysops at any time for the actions of one seems not only silly, but potentially suicidal for the wiki. As Kirby King rightfully said, there are and always will be some ill-will felt against sysops even when their powers are used correctly. Contrary to what DE said earlier in this discussion, the sysops' primary concern cannot always be what is the most popular decision, but what is the best decision for the wiki. Obviously, sysops cannot have ivory tower views that they and they alone know what is best for the wiki and that everyone else just exists to do their bidding, but sometimes the unpopular choices have to be made. For example, about two months ago, if we had let the popular decision of all the users stand, this would no longer be an encyclopedia, but another chat room and social networking service. Obviously, that is not the purpose (or primary purpose) of wikia. As sysops, we had to step in and make the unpopular decision that was best for the wiki. This is true of all leadership/management/administrator roles. If sysops could be expelled simply because the users didn't like a single decision that they made, we would not have any sysops left. Third, I again agree with Kirby King that a reelection system that begins by removing all current sysops powers and treating all RfAs the makes no sense. As even the proponents of this measure have indicated, there is really only one problematic sysop ''at most''. To recall all sysops and make them reapply is not only unfair, but completely baseless. Also, to clump all the sysops in with other users trying to get RfAs would take forever. Who's going to manage the wiki while it all gets sorted out? And who is going to arbitrate this? Two editors who have done nothing to improve the content of this wiki? Finally, do you really think that we have not at all tried to quell this problem internally. As SC said, it appears that you have not even bothered to read all of the conversations that have been happening, nor have you bothered to look at the surrounding events. And there is no way you could possible know everything seeing as you do not have access to my IM or e-mail conversations. Trust me, if you still want to go down this road and (on the off chance) Angela goes along with it, I'm ready. I just hope everyone (except DE and Warwick as they are already convinced they are right) understands that it is uncalled for, dumb, and potentially suicidal to this wiki. [[User:Clarinet Hawk|Clarinet Hawk]] <small>([[User talk:Clarinet Hawk|talk]] · [[Special:Contributions/Clarinet Hawk|contributions]])</small> 16:16, 23 August 2008 (UTC) | ||
:Of course "the sysops' primary concern cannot always be what is the most popular decision, but what is the best decision for the wiki," I never said otherwise; all I said was that consensus > ''policy.'' As I mentioned on the Community Portal talk page, one look at PvXwiki's ADMIN page (which I wrote) should be more than enough to convince you that I am absolutely a proponent of nigh complete autonomy for Sysops; however, that autonomy does not make Sysops infallible, and there ''should'' be a way for the community-at-large to express dissent, even if the final decision were to fall to, say, a Bureaucrat alone as it probably would on, say, PvXwiki. I can keep arguing the point... particularly that there is a middle ground between giving the community zero authority over the Sysops and giving them complete authority... but I can see I'm getting nowhere, so I'm gonna change gears. A recall, even if it were to occur, but not likely begin by stripping all of the Sysops of their authority and having them re-undergo an identical RfA process; for instance, this is the reconfirmation policy on GWW: [http://wiki.guildwars.com/wiki/GWW:RFA#Reconfirmation GWW:RFA#Reconfirmation]. (Please note that I'm not suggesting that you implement that policy, I'm merely attempting to give you a sense of what a reconfirmation might potentially look like.) That said, however, the Sysops would still, likely, be able to administrate during the period unless you chose a radically different tact; who knows, you could even disallow new RfAs until the reconfirmations are done with. And why in the world would I (or anyone from GuildWiki, etc.) arbitrate this? When have I even remotely suggested that? Honestly? The whole purpose of the "Bureaucrat" technical position is that it allows a user with that designation to alter user rights. Granted, that's not entirely the case on this Wiki because of Wikia, but the point stands. I realize that there may not be enough Bureaucrats at the moment to handle the arbitration, but that problem is only tangentially related to the merits of this suggestion. Anywho, I tend to agree with Angela that, regardless of the decision, it's best to wait awhile before taking any action (and, since the initial proposal was to implement this after the RfA policy was revamped, that should be that). On a side note, you should only believe that reconfirmations would be suicidal if you believe that Sysops wouldn't be confirmed. Ta. – [[User:Defiant Elements|<font color="black">Defiant Elements</font>]] 21:47, 24 August 2008 (UTC) | :Of course "the sysops' primary concern cannot always be what is the most popular decision, but what is the best decision for the wiki," I never said otherwise; all I said was that consensus > ''policy.'' As I mentioned on the Community Portal talk page, one look at PvXwiki's ADMIN page (which I wrote) should be more than enough to convince you that I am absolutely a proponent of nigh complete autonomy for Sysops; however, that autonomy does not make Sysops infallible, and there ''should'' be a way for the community-at-large to express dissent, even if the final decision were to fall to, say, a Bureaucrat alone as it probably would on, say, PvXwiki. I can keep arguing the point... particularly that there is a middle ground between giving the community zero authority over the Sysops and giving them complete authority... but I can see I'm getting nowhere, so I'm gonna change gears. A recall, even if it were to occur, but not likely begin by stripping all of the Sysops of their authority and having them re-undergo an identical RfA process; for instance, this is the reconfirmation policy on GWW: [http://wiki.guildwars.com/wiki/GWW:RFA#Reconfirmation GWW:RFA#Reconfirmation]. (Please note that I'm not suggesting that you implement that policy, I'm merely attempting to give you a sense of what a reconfirmation might potentially look like.) That said, however, the Sysops would still, likely, be able to administrate during the period unless you chose a radically different tact; who knows, you could even disallow new RfAs until the reconfirmations are done with. And why in the world would I (or anyone from GuildWiki, etc.) arbitrate this? When have I even remotely suggested that? Honestly? The whole purpose of the "Bureaucrat" technical position is that it allows a user with that designation to alter user rights. Granted, that's not entirely the case on this Wiki because of Wikia, but the point stands. I realize that there may not be enough Bureaucrats at the moment to handle the arbitration, but that problem is only tangentially related to the merits of this suggestion. Anywho, I tend to agree with Angela that, regardless of the decision, it's best to wait awhile before taking any action (and, since the initial proposal was to implement this after the RfA policy was revamped, that should be that). On a side note, you should only believe that reconfirmations would be suicidal if you believe that Sysops wouldn't be confirmed. Ta. – [[User:Defiant Elements|<font color="black">Defiant Elements</font>]] 21:47, 24 August 2008 (UTC) | ||
A little off subject here, but gargomon & oxico were dangerously close to becoming sysops before they closed, shouldnt they be considered? [[User:Kperfekt722|KP317]] ([[User talk:Kperfekt722|talk]]) 23:41, 16 September 2008 (UTC) |