TestWiki:Community portal/Archive 1: Difference between revisions

From TestWiki
Content added Content deleted
(OneClickArchiver adding [[TestWiki:Community portal/Archive 1#Becoming a Consul member [Closed]|Becoming a Consul member [Closed]]])
Line 45: Line 45:
::{{Support|weakly|weakly}} As per what NDKilla said I really don't think there is a need for another consul, seeing that there is not a lot of community here. If the community will grow and there will be a real need then you can re-request. [[User:Reception123|Reception123]] ([[User talk:Reception123|talk]]) 18:41, 7 January 2016 (UTC)
::{{Support|weakly|weakly}} As per what NDKilla said I really don't think there is a need for another consul, seeing that there is not a lot of community here. If the community will grow and there will be a real need then you can re-request. [[User:Reception123|Reception123]] ([[User talk:Reception123|talk]]) 18:41, 7 January 2016 (UTC)
{{Discussion bottom}}
{{Discussion bottom}}

{{Clear}}
== Bot policy ==
Per [[TestWiki:Bots]] and [[TestWiki:Bot approval requests‎]], I've gone ahead and pushed a configuration change. '''Effective immediately''', [[TestWiki:Bureaucrats|Bureaucrats]] may no longer assign the bot flag. For now, all bot requests must be made directly through a [[TestWiki:Consuls|Consul]]. Operating a bot without the bot flag (or contacting us asking for authorization to test the bot without the flag) will be '''grounds for an immediate, indefinite block''' against the bot, and possible sanctions against the bot operator.

I apologize for what I'm well aware are harsh measures, but bot's (even without flag/permission) can cause a lot of damage quickly, that even with certain tools, can be hard to undo. A more in depth bot policy will be created in the near future.

In general:
* '''NEVER GIVE THE BOT FLAG TO AN ACCOUNT YOU HAVE ACCESS TO, OR AN ACCOUNT USED BY A BOT YOU OPERATE''' This will be grounds for removal of your permissions (up to discretion of [[TestWiki:Consuls|Consuls]])
* Never operate a bot without authorization
** For testing a bot, this involves asking a Consul directly for permission to run the bot without the flag
** For tested, working bots, this involves acquiring the bot flags via appropriate means
* Try to document what the bot does, how it works, etc
** Although you are free to use a bot for whatever reasons, and you may test whatever on this wiki:
*** Consuls, Stewards, and System Administrator's may request source code for your bot. '''IT MUST BE PROVIDED UPON A VALID REQUEST'''
*** Additionally, even if source code isn't requested, '''you are required to make a public note about the bots tasks'''. This will allow users who wish to do so the ability to monitor your bot and make sure it is not malfunctioning
*** Bots are recommended but not required to have their "power" based on an on-wiki page. This page, if needed, can be protected to logged in users, autoconfirmed, sysop, crat, or consul only.
*** '''Bots failing to abide by on-wiki toggle switches may be indefinitely blocked at any hint of malfunction or operation outside of authorized scope'''

Revision as of 06:17, 1 May 2018

Archive 1 Archive 2 Archive 3 Archive 4

We need to work on

For anyone that wants to help here is a list of stuff that needs to be done :

  • Import useful templates (and files)
  • Create main page (maybe wait for Meta first)
  • Develop policies
  • Fix request template (permission)
  • Backup

Please add anything that you think is relevant to the list.--Reception123 (talk) 02:12, 8 August 2015 (EDT)

Proposal for NDKilla as consul

Mediawiki:Common.css

New comment on MediaWiki:Common.css

Currently editing the interface page to test making my name (and mine alone) red, but also trying to get links to other pages working (my talk page etc). Any sysop who feels this is disruptive is welcome to delete the page. -- Cheers, NDKilla ( TalkContribs ) 17:44, 17 December 2015 (UTC)

I think that it is every user's choice if they want to change their name color. Everyone is free to edit their own name. Reception123 (talk) 18:08, 17 December 2015 (UTC)

Becoming a Consul member [Closed]

Bot policy

Per TestWiki:Bots and TestWiki:Bot approval requests‎, I've gone ahead and pushed a configuration change. Effective immediately, Bureaucrats may no longer assign the bot flag. For now, all bot requests must be made directly through a Consul. Operating a bot without the bot flag (or contacting us asking for authorization to test the bot without the flag) will be grounds for an immediate, indefinite block against the bot, and possible sanctions against the bot operator.

I apologize for what I'm well aware are harsh measures, but bot's (even without flag/permission) can cause a lot of damage quickly, that even with certain tools, can be hard to undo. A more in depth bot policy will be created in the near future.

In general:

  • NEVER GIVE THE BOT FLAG TO AN ACCOUNT YOU HAVE ACCESS TO, OR AN ACCOUNT USED BY A BOT YOU OPERATE This will be grounds for removal of your permissions (up to discretion of Consuls)
  • Never operate a bot without authorization
    • For testing a bot, this involves asking a Consul directly for permission to run the bot without the flag
    • For tested, working bots, this involves acquiring the bot flags via appropriate means
  • Try to document what the bot does, how it works, etc
    • Although you are free to use a bot for whatever reasons, and you may test whatever on this wiki:
      • Consuls, Stewards, and System Administrator's may request source code for your bot. IT MUST BE PROVIDED UPON A VALID REQUEST
      • Additionally, even if source code isn't requested, you are required to make a public note about the bots tasks. This will allow users who wish to do so the ability to monitor your bot and make sure it is not malfunctioning
      • Bots are recommended but not required to have their "power" based on an on-wiki page. This page, if needed, can be protected to logged in users, autoconfirmed, sysop, crat, or consul only.
      • Bots failing to abide by on-wiki toggle switches may be indefinitely blocked at any hint of malfunction or operation outside of authorized scope