SmashWiki:Requests for adminship: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
No edit summary
(resolving)
 
(562 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
This is the page for '''nominating sysops''' for SmashWiki. If you don't know what a sysop is, the [[Help:FAQ|FAQ]] has some information about the job, and you can also find a [[Special:Listusers/sysop|full list of current sysops]].
{{policy}}
{{shortcut|[[SW:RFA]]}}
This is the page for '''requesting [[SmashWiki:Administrators|adminship]]''' for SmashWiki.  


Here are the rules for nominating sysops:
==Rules and regulations==
* Only self-nominations are allowed. If you think that another member would make a good sysop, then you can convince them to nominate themselves. You cannot, however, make a nomination on behalf of another user.
* Only self-nominations are allowed. If you think that another user would make a good administrator, then you can try convincing them to nominate themselves. You cannot make a nomination on behalf of another user.
* All new nominees should post their name below as a new page header (i.e. <nowiki>==Username==</nowiki>). Underneath, the user should state why he would like to become a sysop, and why he thinks he would be fit for the job. Posting examples of notable work that the nominee has contributed is highly encouraged. The nominee should be sure to sign this post.
* Candidates should describe why the wiki should want them to be administrators, not why they want to be administrators on the wiki. Users who wish to be promoted should demonstrate a steady commitment to this wiki, and be able to point to reasons that the sysop tools would allow them to better contribute to the wiki beyond banal janitorial work.
* Users who wish to support, oppose, or comment on the nomination may do so by using bullet points underneath the original post (newer bullets toward the bottom). To be clear, ''this is not a vote, and this is not a democratic process.'' Although the views of the user community are important and will be taken into account in the final decision, the decision will ultimately be up to the current sysop team and Smash World leadership.
* After sufficient time has passed to allow all users who wish to express an opinion the chance to do so, a decision will be made based on community consensus as to whether or not the request will succeed. Once a decision has been made, the discussion will be archived.
* After sufficient time has passed to allow all sysops who wish to express an opinion the chance to do so, a decision will be made among the sysops as to whether or not the nomination will succeed. If the nomination succeeds, a bureaucrat will make the nominee a sysop. If not, a sysop will close discussion on the nominee. Once a decision has been made, the discussion will be archived and moved to an appropriate subpage.
* Selections of administrators are not a simple vote count, or majority opinion. Indeed, a bureaucrat may decide against the "popular vote" if they believe the opposing side has provided more convincing arguments, or that the candidate has failed to satisfactorily respond to questions about their merits, and RfAs have been failed in the past that technically had a majority of the "votes" being supportive.
* Nominations will be open on an ongoing basis for the time being. In the future, however, nominations may only be open for prescribed periods of time. This page will be protected if nominations are not being accepted.
* When supporting or opposing a candidate, provide good and well-written reasons as to why you support or oppose the candidate. Comments that describe in detail why the candidate should/should not become an administrator carry far more weight than a simple support/oppose. Additionally, attaching intensifiers to your support/oppose (e.g. saying you ''strongly support'' the candidate) will not make your "vote" carry any more weight.
* The candidate, or any other user, are allowed to respond to any other user's "vote", and are encouraged to, if a user has stated something factually incorrect in their reasoning or has otherwise said anything else refutable. Such replies should be written in the comments section, rather than directly replying to the user's "vote", so that the "voting" sections can be kept clean. Additionally, while the candidate and other users are encouraged to refute another user's reasoning when applicable, it should be within reason; a candidate or staunch supporter who tries shoddily refuting everyone that opposes will likely just worsen their case and bolster the opposition.
* [[SW:RB|Rollback status]] is not required for a successful RfA, and a candidate having rollback will not make their case for adminship any stronger. Users who do not have rollback and only want sysop tools for quick reverts of vandalism will be directed towards the [[SW:RFR|appropriate request]].
* [[SW:EST|Established status]] is also not required for a successful RfA, but users who haven't been around long enough or haven't contributed enough to be established will likely have little support unless they have quickly proven themselves extraordinary.
** [[SW:AUTO|Autoconfirmed status]], however, ''is required'', and a user will not even be able to create an RfA if they are not autoconfirmed.
* Upon request, a prospective administrator may be given a scenario and asked his/her opinion on how s/he would handle it.
* Users that have been blocked in the past, or who have previously made an RfA and failed, are no less eligible for adminship. However, such users should be able to demonstrate how they have improved since the block/previous RfA, lest their RfA find serious opposition.
* Former administrators that have been [[SW:RFD|formally demoted by a RfD]] are similarly no less eligible for adminship, but will certainly face stalwart opposition to their RfA if they are unable to demonstrate serious reformation since their demotion. Former administrators that were demoted for [[SW:ADMIN#Retired|inactivity or formally retiring]] but wish to regain sysop powers are also eligible for adminship, but may be able to skip the RfA process entirely if the current active administration feels they are still clearly well-suited for the role.


<big><center>''' Place new nominations below, newer nominations at the bottom of the page. '''</center></big>
==Past nominations==
----
*For a list of all previous requests for adminship that ended with the candidate's promotion, please see [[:Category:Accepted RfAs|this category]].
*For a list of all previous requests for adminship wherein the candidate was not promoted, please see [[:Category:Failed RfAs|this category]].


==F8AL==
==How to nominate==
Hello, I would like to become a sysop because I browse SmashBoards and SmashWiki daily and I tend to make alot of edits to existing pages (i.e. adding information, deleting spam/unneccessary information etc.).  I am also quite knowledgable on Smash Bros. and plenty of other games. I think that I would be fit for this job because I get along with everyone and I'm friendly and open to critism and suggestions.  I would not become "power-hungry" if I became a sysop because I want everyone to contribute to SmashWiki and that everyone should be heard.  Thank you for your time and for reading this. - F8AL
If you have not had a request for adminship page before, follow this two-step process.
*I support F8AL, he had been posting on Smash Boards for quite awhile, and he keeps a number of pages up to date. [[User:JohnCurriSuxAtSmash|JohnCurriSuxAtSmash]] 16:55, November 22, 2007 (EST)


*I'll also gladly support F8AL. He seems to make good posts on SWF, and does decent edits to this site. I can't see him being a bad choice for Sysop...ness at all.
#Go to the end of the [[#Current requests|requests]] section below, and add the following text:<br><code><nowiki>{{{{subst:FULLPAGENAME}}/Username}}</nowiki></code> Where "Username" is the name of the user being nominated.
#Click on the created red link, and add:<br><code><nowiki>{{subst:rfa|Username|Comment explaining your nomination. ~~~~}}</nowiki></code>


- [[User:Blackadder|Blackadder]]
However, if you have had a previous request for adminship, follow this process instead.


*I also support F8AL. I know him personally and he is not someone who will be biased towards someone. Therefore, his opinion in this matter is based on the facts.
#Go to the end of the [[#Current requests|requests]] section below, and add the following text:<br><code><nowiki>{{{{subst:FULLPAGENAME}}/Username (#)}}</nowiki></code><br>Where "Username" is the name of the user being nominated, and where # is 2 for the second RfA, 3 for the third, and so on.
#Click on the created red link, and add:<br><code><nowiki>{{subst:rfa|Username|Comment explaining your nomination. ~~~~}}</nowiki></code>


- [[User:Cyber | Cyber]]
==Current requests==
''none''


==[[User:Randall00|Randall00]]==
[[Category:SmashWiki]]
 
[[Category:Administration]]
Within the local regional smash community, and to some extent a little bit beyond, I am known as an individual who will get the things done that everyone else only talks about doing. 13 months ago today, the city of Calgary went from having no competitive smash community at all to hosting our first [[Pro Impact BI-WEEKLY Smash]] event which would ultimately grow into the most popular bi-weekly tournament in western Canada, as well as expanding out to rural areas of the province and further into the country forming the [[Central Canada Smash Circuit]]. A big part of what has made this possible rests with the continued enthusiasm for competition from the community members, but I'd be lying to myself if I said that it would be as popular as it is without my help. I have a very objective, community-oriented mindset and am obviously capable of handling administrative and organizational duties--all bits and pieces of a skill set that is equally well-suited to a <u>community</u>-authored encyclopedia. Though I never sought out to be the boss of anything, I still ended up learning how a community responds to someone in a position of "power" and how important the clarity of your communication becomes when saying the same thing to a lot of people. This applies doubly so within the SmashWiki branch of Smash World because we are rarely afforded the opportunity to meet those we work with in person and are left only with text. Text-based communication is something that I definitely have a lot of experience with and it is very important to me that what I write is understood as clearly as possible by as many people as possible--to the extent that I'm a bit of an obsessive-compulsive perfectionist with my writing. Although I may waste time in that regard, it has thankfully yet to steer me wrong.
 
I've been running a little personal home page called '''[http://www.et-cet-era.ca Et cetera]''' for close to ten years now (when I was thirteen years old and everyone had [http://www.angelfire.com Angelfire] sites). The page has undergone some pretty serious transformation since then and as I began to learn more about how media presentation really works, it ultimately grew as a creative project to the point that I purchased a domain name at www.et-cet-era.ca.
 
Most recently, I've converted the once-relatively-simple HTML-based Et cetera into a MediaWiki structure. It was a challenging port and I learned a lot about the behaviour of the software from the Bureaucrat-side in the process. I additionally spent a great deal of time just preparing my existing server for the software and now, after many tedious difficulties with my shoddy web host, I have a pretty firm understanding of how to install the whole thing from scratch in my sleep if I wanted to. Although I recognize that a lot of these skills are not necessarily useful on a day-to-day basis for a SysOp, the fact is that it represents a better applied knowledge of how the MediaWiki platform is designed to operate. With that knowledge combined with the power to use it, the core elements of what makes a wiki successful can be fleshed out at SmashWiki and make it a place where people ''want'' to write good articles, participate in the backend community and improve the entire presentation as a collective body of writers.
 
On the subject of applying MediaWiki's capabilities here, I've done some comparatively light work in the [[Special:Specialpages|Special Pages]] department in terms of cleaning up double re-directs, loosely working out the branches of the [[:Category:Smashers|smasher]] [[Special:Categories|Category]] tree and the various functions that build the foundation for an encyclopedia that can be written by anyone without having to explain the whole thing to each new author. This hasn't been the focus of my work, but I think my contributions in what little existing back-end there is here is again representative of my confidence in understanding how it was made to work at its best.
 
More significant to most members who know who I am is my contributions on the authoring side; as a user, I've used all the tools I have as well as I can to not only spiff up my own articles and those of my tournament-goers and friends, but also taking a keen interest in other regional smash communities, character articles, overall presentation and most importantly, providing the tools to pass those values on to other authors. For instance:
 
*[[SmashWiki:Smasher Project]] - It's been a long time since I did the math, but at one point, I had written about 40% of ''all'' the existing [[smasher]] articles (though curiously, I haven't touched [[Smasher]] itself hardly at all) and when I began doing significant work on them, the marked inconsistency between what I was doing and what others were doing was so pronounced that I knew it would grow to be a problem as more and more authors came in.
 
:The solution was the project page: a set of streamlined instructions and guidelines on how to write a proper smasher article. They were based on how I had been writing them at the time but credit for the format really goes to the [http://en.wikipedia.org Wikipedia] itself. I modelled the structure of my writing on that of Wikipedia's community because it represented the largest diverse number of people who could agree on a format. Recognizing that smashers and those interested in smash come in many shapes and sizes, I felt adopting their way right off the bat would help avoid some of the time-consuming bureaucracy associated with arriving at the same conclusion on our own talk pages months and months down the road. I believe this was the second project page on SmashWiki, after [[SmashWiki:Character Project]] and in fact, I've always meant to add more to it and probably will in the coming months.
 
*[[Template:Smasherbeta]] - This was only a slightly modified version of the already-existing [[Template:Smasher]] when I first came around, but the changes I made were subtle and well-suited for a quality presentation. Knowing what was required to make it look as pretty as possible and how to achieve that stems from my experience building websites like Et cetera and [http://www.proimpact.ca ProImpact.ca], which houses data for the Central Canada Smash Circuit. I understand how a website is supposed to operate and what makes them look sleek and professional. Probably the niftiest switch to the template was the inclusion of small national flags for each competing country which helps to give some regional identity to players in a visually-appealing way.
 
*[[Template:Ccsc]] - This was something I made that is just another example of my understanding of MediaWiki software and what can be done with it. Again, it helps to unite community smashers to others in their competitive region and encourages competition between them. Additionally, the page itself contains instructions on how to copy the template and use it for your own smash circuit which has been applied with [[Template:Sgsc]] in South Germany and [[CAOTIC]]'s [[Template:Aussmash]]. Seeing this occur is a tangible example of how a community-written website can feed off of its own members when a proper backend is in place.
 
I also wrote a few power rankings articles like [[Washington Power Rankings]] and [[CCSC Power Rankings]] and I dabble around making things like [[Template:Speculation]] and participating in wholesome community discussions--most notably [[Talk:Professionals#Pro_vs._Pro-Am:_New.2C_Hip_Lingo_to_Define_.22Pro.22_Within_the_Microcosm...|this one about defining a professional]].
 
I know that I probably could've waltzed in here and said nothing other than "[[Special:Contributions/Randall00]]" and still gotten two or three cries for support as a SysOp, but I think it's important that I break down what I have to offer in addition to what I've already done. It should be clear from my contributions that my intentions are community-oriented and I know this to be a necessary administrative functionality of a successful wiki. As a user, I am limited only by the lack of responsibility that the average user carries. As a SysOp, I would inherit that sense of responsibility and with it, herald in some positive changes around here. I promise.
 
--<font color="000023">'''[[User:Randall00|RJM]]'''</font> <sup>''[[User talk:Randall00|Talk]]''</sup> 01:33, November 23, 2007 (EST)
 
 
==Silverdragon706==
 
Hello, I'm known as FyreNWater around the site. While I'm fairly new to the SmashWiki, I think I've made quite a few contributions to the site. I haven't done anything fancy like make templates, categories, or even make many new pages. However, I revert vandalism, clean up poorly-written articles, contribute to stubs, tag bad pages for deletion, and notify administrators of vandals. I've only been around for a few months, but I can see that there is a great need for authority to do something about vandals and the problems they cause. I'm on almost daily and see problems that I wish I could solve, like deleting joke/spam pages and banning individuals who have done nothing but vandalize. Now, all I can really do is notify the current sysops about vandals and tag bad pages for deletion. I personally have a list of bad users and pages. They've been untouched for at least a month as no sysop seems to have been around to do much.
 
While I haven't done any advanced things like templates, nearly all of my contributions have been reverting vandalism, tagging pages for deletion/clean-up, removing speculation, and rewriting articles to have a more professional tone. The most notable thing I did was nearly single-handedly revert about 200 spam edits Zoomer555 made using a bot.
 
I feel that if I were a sysop, I could clean up the junk that pops up around the site. My almost-daily visits mean that problems could be attended to soon after they arise. With the small number of sysops and the growing amount of junk showing up on SmashWiki, I feel that my contributions can help keep the site as vandalism-free as possible. '''[[User:Silverdragon706|FyreNWater]]''' -  <small>([[User talk:Silverdragon706|Talk]] • [[Special:Contributions/FyreNWater|Contributions]] )</small> 02:50, November 23, 2007 (EST)

Latest revision as of 19:02, August 16, 2023

Policy.png This page documents an official SmashWiki policy, a widely accepted standard that all users should follow. When editing this page, please ensure that your revision reflects consensus. If in doubt, consider discussing changes on the talk page.
Shortcut:
SW:RFA

This is the page for requesting adminship for SmashWiki.

Rules and regulations

  • Only self-nominations are allowed. If you think that another user would make a good administrator, then you can try convincing them to nominate themselves. You cannot make a nomination on behalf of another user.
  • Candidates should describe why the wiki should want them to be administrators, not why they want to be administrators on the wiki. Users who wish to be promoted should demonstrate a steady commitment to this wiki, and be able to point to reasons that the sysop tools would allow them to better contribute to the wiki beyond banal janitorial work.
  • After sufficient time has passed to allow all users who wish to express an opinion the chance to do so, a decision will be made based on community consensus as to whether or not the request will succeed. Once a decision has been made, the discussion will be archived.
  • Selections of administrators are not a simple vote count, or majority opinion. Indeed, a bureaucrat may decide against the "popular vote" if they believe the opposing side has provided more convincing arguments, or that the candidate has failed to satisfactorily respond to questions about their merits, and RfAs have been failed in the past that technically had a majority of the "votes" being supportive.
  • When supporting or opposing a candidate, provide good and well-written reasons as to why you support or oppose the candidate. Comments that describe in detail why the candidate should/should not become an administrator carry far more weight than a simple support/oppose. Additionally, attaching intensifiers to your support/oppose (e.g. saying you strongly support the candidate) will not make your "vote" carry any more weight.
  • The candidate, or any other user, are allowed to respond to any other user's "vote", and are encouraged to, if a user has stated something factually incorrect in their reasoning or has otherwise said anything else refutable. Such replies should be written in the comments section, rather than directly replying to the user's "vote", so that the "voting" sections can be kept clean. Additionally, while the candidate and other users are encouraged to refute another user's reasoning when applicable, it should be within reason; a candidate or staunch supporter who tries shoddily refuting everyone that opposes will likely just worsen their case and bolster the opposition.
  • Rollback status is not required for a successful RfA, and a candidate having rollback will not make their case for adminship any stronger. Users who do not have rollback and only want sysop tools for quick reverts of vandalism will be directed towards the appropriate request.
  • Established status is also not required for a successful RfA, but users who haven't been around long enough or haven't contributed enough to be established will likely have little support unless they have quickly proven themselves extraordinary.
    • Autoconfirmed status, however, is required, and a user will not even be able to create an RfA if they are not autoconfirmed.
  • Upon request, a prospective administrator may be given a scenario and asked his/her opinion on how s/he would handle it.
  • Users that have been blocked in the past, or who have previously made an RfA and failed, are no less eligible for adminship. However, such users should be able to demonstrate how they have improved since the block/previous RfA, lest their RfA find serious opposition.
  • Former administrators that have been formally demoted by a RfD are similarly no less eligible for adminship, but will certainly face stalwart opposition to their RfA if they are unable to demonstrate serious reformation since their demotion. Former administrators that were demoted for inactivity or formally retiring but wish to regain sysop powers are also eligible for adminship, but may be able to skip the RfA process entirely if the current active administration feels they are still clearly well-suited for the role.

Past nominations

  • For a list of all previous requests for adminship that ended with the candidate's promotion, please see this category.
  • For a list of all previous requests for adminship wherein the candidate was not promoted, please see this category.

How to nominate

If you have not had a request for adminship page before, follow this two-step process.

  1. Go to the end of the requests section below, and add the following text:
    {{{{subst:FULLPAGENAME}}/Username}} Where "Username" is the name of the user being nominated.
  2. Click on the created red link, and add:
    {{subst:rfa|Username|Comment explaining your nomination. ~~~~}}

However, if you have had a previous request for adminship, follow this process instead.

  1. Go to the end of the requests section below, and add the following text:
    {{{{subst:FULLPAGENAME}}/Username (#)}}
    Where "Username" is the name of the user being nominated, and where # is 2 for the second RfA, 3 for the third, and so on.
  2. Click on the created red link, and add:
    {{subst:rfa|Username|Comment explaining your nomination. ~~~~}}

Current requests

none