設定変更の制限
 | これは方針ではありません。システム管理者が設定変更を処理する方法についてのみ説明しています。 |
場合によっては、技術的に実装可能なwikiの設定の変更をコミュニティが要求することができますが、MediaWikiの設定の最終権限を持つ システム管理者 によって拒否されることがあります。
This page serves to document how system administrators usually react to certain types of requests, and what the community should expect from them. As such, it doesn't need to contain all rejections from system administrators, just ones that are likely to be requested again. If you feel that a rejected request should (or should not) be listed here, please update this table as appropriate, even if you're not a system administrator. If you're not sure, leave a comment on the talk page.
禁止されている変更
このセクションにはすぐに断られるであろう変更がリストアップされています。 System administrators prohibit these changes to protect Wikimedia's founding principles and core values, as well as to protect the integrity of the projects in general. The Wikimedia Foundation's Legal department also prohibits some changes for legal reasons.
| 依頼の種類 | リクエストの例 | 理由 | 注記 |
|---|---|---|---|
| Wikiのオープン性を低下させる変更 | Remove a log from logged actions | Transparency is a non-negotiable principle of MediaWiki. Feature requests are recommended if a log is bothering the community and features to filter it out don't exist yet. | This doesn't include hiding a log by default from Special:Log, but only cases when the log would not exist at all. |
| Enable CAPTCHA for all edits of non-confirmed users permanently | This configuration places an undue restriction on new contributors, given CAPTCHAs are here to help with abuse and vandalism, not to serve any other purpose. System administrators deemed that this is incompatible with Wikimedia core values, and as such, prohibited this change. | Please note this is about enabling CAPTCHA for all edits permanently. If your wiki is experiencing immediate and unmanageable abuse/vandalism, please do reach out to the system administrators. This would be considered as a security incident report. As such, please use the security report form. This will create a task to be visible to the Wikimedia Foundation Security department, as well as relevant system administrators. They will jointly assess your issue, decide on potential restrictions and implement them. You do not need to recommend any solutions. | |
| Remove editing permission from a user group | "Anyone can edit" is a non-negotiable principle of Wikimedia projects. Full revocation of editing permissions from any user group will not be enabled. | Partial revocation of editing privileges, like enwiki's ACTRIAL, can happen from time to time, but those cases are extremely rare and are subject to careful consideration. See also "Disable non-autoconfirmed page creation" below. | |
| 技術的に不可能な変更 | タイムゾーンの名前の変更 | MediaWiki uses the PHP timezone database, which uses the IANA Time Zone Database. As such, it is technically and physically impossible to change the names of any timezone options. It's only possible to change which timezone is the default in your wiki via the $wgLocaltimezone variable. | |
| Proposed changes with security and/or legal liability issues | Allow non-admins to view deleted content | WMF Legal has barred non-admins not passing an RFA-comparable process from viewing deleted content; see Wikipedia:Viewing deleted content. | Creation of such a user group usually requires WMF Legal review. Small wikis will not likely be allowed to have such user groups. |
| Allow non-stewards to manage CheckUser/Oversight permissions | Only stewards are allowed to manage those highly restricted groups; local wikis are not allowed to customize this. This includes granting CheckUser/Oversight related permissions to additional groups. | CheckUsers and oversights are governed by global policies; stewards will ensure that the policies are correctly enforced. | |
| Add hideuser right to non-oversighters | By policy, it is the task of oversighters to hide things from the public. Oversighters sign confidentiality agreements and are legally required to keep the information private, while this is not true of administrators and others. | ||
| Grant Interface admins other permissions | The purpose of interface admins is to make fewer users able to edit CSS and JS pages. Granting other rights to this group may encourage wikis to grant this right when their intention is different. | Per discussion in T320752, this does not apply to editcontentmodel.
| |
| Allow administrators to grant bot, administrator or interface admin rights | Rejected because granting and removing those flags is a task for bureaucrats where present, or stewards. Interface administrators also have highly sensitive permissions (to edit CSS and JS pages) and requests for granting must be carefully considered. As such, it is necessary that only bureaucrats or stewards handle this task. | Wikis that currently don't have any bureaucrats and feel they are big enough to handle this themselves are recommended to elect bureaucrats instead. | |
| Allow bureaucrats to remove bureaucrat rights | プロジェクトの安全性を守るためのものです。 Since bureaucrat permissions are higher than those of administrators, only stewards are allowed to do this. | Bureaucrats on all private wikis can remove bureaucrat status, but that's because private wikis are managed by dedicated groups and serve special support purposes rather than host content. | |
| Changes to use unsupported technologies, or abuse them in unsupported ways | Installation of extensions/skins that are not well maintained | Some extensions are currently installed in some Wikimedia wikis, but have significant unresolved problems or bugs. So it is decided not to install these extensions to further wikis, though existing installations will be preserved. | 直近ではこれらを含みます： |
| トークページでビジュアルエディターを有効にする | The visual editor is not built to support editing talk pages. As such, enabling the visual editor in a talk page namespace is likely to not always work as expected by the community. To save developers from bug reports about something that's not supposed to work in the first place, enabling VisualEditor on talk pages has been prohibited. | StructuredDiscussions implemented some VisualEditor features; another alternative is the New Discussion Tool. | |
| Changing the default skin on any individual wiki | Wikimedia should have a standardized look globally across all our projects. It has been decided that Vector will remain the default skin on all Wikimedia Wikis. | Changing the default skin on all Wikimedia wikis is certainly not prohibited, but would be extremely difficult to accomplish, and would be centrally led. Not only would this require consultation with all affected communities before such a decision could be made, but a massive effort would also be required to make all the necessary changes "behind the scenes". |
特定の基準を満たす必要がある変更
| 依頼の種類 | 理由 |
|---|---|
| ローカルでのファイルのアップロード | According to Wikimedia's licensing policy, all projects are expected to host only content under a Free Content License. In limited circumstances, a project may adopt an Exemption Doctrine Policy (EDP), which defines (in accordance with both United States law as well as the law of countries where the project content is predominantly accessed) when copyrighted materials can be uploaded.
If your project may not accept non-free media (under an EDP), it is highly unlikely local file uploads will be enabled. Free media should go to Wikimedia Commons instead. 無料でないコンテンツも参照。 |
| どのウィキメディアプロジェクトにもインストールされた事のない拡張機能/スキンの導入 | ウィキメディア基盤システムの安全を守るため、稼働するすべての拡張機能、スキン、その他の構成要素は、セキュリティ、性能、その他の審査に合格しなければなりません。 少なくとも一つのウィキメディアプロジェクトに導入された事がない拡張機能は、そのような審査に合格するまで導入されません。 必要な手順についてはMediaWiki.orgの配置用の拡張機能の記述をご覧下さい。 |
拒否される可能性がある変更
This section lists changes that are not strictly prohibited, but are likely to be declined unless special evidence can be presented to convince system administrators that the changes are necessary.
| 依頼の種類 | 理由 |
|---|---|
| Disable non-autoconfirmed page creation | This configuration places an undue restriction on new contributors. Sysadmins will resist such a request unless the wiki in question (1) is prepared to handle drafts in a timely manner, (2) has a well developed editing and administrative community, and (3) has established an unusually broad consensus for the change. The first two points can be addressed by appealing to the wiki's size: the number of active editors, sysops, bureaucrats, and other functionaries should be similar to "big wikis", otherwise a very good explanation will need to be given as to why the request should be accepted. The third point can be satisfied by a carefully discussed on-wiki RFC, with the closing administrator explaining the consensus in the relevant Phabricator task; if the consensus does not look particularly strong on its face (note that there may not be any sysadmins who are able to read the local language of the wiki), the admin will have to explain why it nonetheless should be considered sufficiently broad. |
| ビューロクラットが管理者権限を削除できるようにする | While bureaucrats on some wikis can revoke the administrator flag, at most wikis this is the responsibility of stewards. In order for this kind of request to be accepted, the wiki should be large—with multiple active bureaucrats—and be able to demonstrate a real need for the change. In smaller wikis this ability is prone to abuse by bureaucrats wishing to usurp the power of the community to decide on issues of adminship. |
| 小規模wikiでの特別なグループ | System administrators may consider wiki size before adding a special user group. Such requests sometimes seem to be motivated by the mere desire to have something that bigger wikis have rather than an actual need. For example, members of the rollbacker group are given a tool that allows them to do with one click the same thing ordinary users can do in a series of steps (revert multiple edits by the same user); in small, low-traffic wikis this speed increase may not be necessary and must be weighed against the potential for abuse. Also, sometimes requests to create a custom group can instead be implemented with an existing user group (such as autopatrolled). In the interest of manageability, sysadmins will not create a new group if an alternative approach can be found. |
禁止ではないが議論停滞するであろう変更
This section lists changes that are of course not be declined per consensus, but due to very high technical matters, they won't be handled shortly.
| 依頼の種類 | 理由 |
|---|---|
| Wikiの正規URLの変更 | See also: Special language codes, Wiki-setup (rename) and phab:T172035 ウィキメディアのプロジェクトによっては、10年単位のかなりの期間にわたり正準記法の URL を使い続け、言語コードの誤用やその他、混乱を招くという問題がありました。 As of January 2022, the process of renaming wikis and changing their URLs remains a severe technical challenge. So far, only the following wikis have ever been successfully renamed:
Currently the known challenges are related to Wikidata, Special:SiteMatrix, ContentTranslation functions, and interwiki logs. |
システム管理者の独断による変更
As noted at Requesting wiki configuration changes, the ultimate authority on Wikimedia configuration lies with the system administrators, as only system administrators can edit it, and as such, are fully responsible for configuration.
As such, system administrators can not only reject requests, but also change configuration on their own. This section aims to explain and document why this might happen, but given the world can be hard to predict, it isn't (and can't be) complete by any means.
In this section, "changes made by the system administrators" are called "measures" for the purpose of simplicity.
Measures are mostly taken to protect the security of the Wikimedia infrastructure, but infrequently, can happen for other reasons as well.
他の理由は予測が難しいので、ここでは触れません。
Examples include (but are not limited to) exceptionally high levels of vandalism, other attempts to disrupt the Wikimedia movement and the like.
Measures can be both permanent and temporary, but temporary measures tend to be more frequent.
System administrators do their best to limit temporary changes as much as possible (in both scope and duration), while still keeping the measures effective.
Any measures may or may not be communicated to the community, as warranted by security implications.
Temporary measures can include (but are not limited to) decreasing the limit of accounts created from one IP address, requiring CAPTCHAs for all edits and the like.
Permanent measures can include (but are not limited to) taking away certain abilities from administrators in favour of dedicated groups or deciding that two-factor authentication is mandated for a user group.