User:Tailsultimatefan3891/Wiki changes to propose/Old/ja: Difference between revisions

From Test Wiki
Content deleted Content added
Created page with "日本語を話さない方、または言語を変更したい場合は、上記の言語から変更してください。"
 
(5 intermediate revisions by 2 users not shown)
Line 5: Line 5:
日本語を話さない方、または言語を変更したい場合は、上記の言語から変更してください。
日本語を話さない方、または言語を変更したい場合は、上記の言語から変更してください。


私は数日間、[[User:Tailsultimatefan3891/Wiki changes to propose|ユーザー:テイルス究極のファン3891/提案するウィキの変更]] としてドラフトとして作業してきました。いくつかの権限が不足しており、ウィキ に変更が必要になる可能性がありますが、コミュニティ ポータルから部分的にブロックされるため、個別に要求することはできませんでした。すべての提案は次のとおりです。ただし、すべての提案が承認されるわけではなく、複数の提案が一度に承認される可能性があります。また、人々がいくつかの選択を行えるように柔軟性も作りました。
<span lang="en" dir="ltr" class="mw-content-ltr">I have been working on it as a draft for a couple days as [[User:Tailsultimatefan3891/Wiki changes to propose]]. I have seen a couple of lacking permissions and we could need changes to the wiki, but I couldn't request them separately as I will get partially blocked from community portal. The all proposals are as follows, however, not every proposal will be passed, but multiple proposals may be passed at once. I have also made the flexibility for people to make some choices.</span>


#<span lang="en" dir="ltr" class="mw-content-ltr">Add Consul Permission: I have noticeably seen a couple of times where policies are bureaucrat-protected. However I can see and we could request to add the consul permission to prevent common bureaucrats from changing such policies especially major edits. As a result we can make a permission in between bureaucrat and steward but please this is not to be confused with the consul permission on Public Test Wiki on Miraheze. In addition, consuls could also add and remove interface administrator, abuse filter administrator, blocked from abuse filter, suppressor, CheckUser, non-steward CheckUser, non-steward suppressor, et al rights. We could also add a level of protection meaning "Allow only consuls" used for edit, move, protect, and delete. Abuse filter administrator rights are packed in the consul permission. Please note that consuls can add or revoke consul rights. Again, to be a consul, an election must be held at the community portal. A consul term can be served for 6 months from last activity, again, those rights can be granted within 1 hour of revocation, otherwise, a reconfirmation vote election will be held.</span>
#<span lang="en" dir="ltr" class="mw-content-ltr">Add Consul Permission: I have noticeably seen a couple of times where policies are bureaucrat-protected. However I can see and we could request to add the consul permission to prevent common bureaucrats from changing such policies especially major edits. As a result we can make a permission in between bureaucrat and steward but please this is not to be confused with the consul permission on Public Test Wiki on Miraheze. In addition, consuls could also add and remove interface administrator, abuse filter administrator, blocked from abuse filter, suppressor, CheckUser, non-steward CheckUser, non-steward suppressor, et al rights. We could also add a level of protection meaning "Allow only consuls" used for edit, move, protect, and delete. Abuse filter administrator rights are packed in the consul permission. Please note that consuls can add or revoke consul rights. Again, to be a consul, an election must be held at the community portal. A consul term can be served for 6 months from last activity, again, those rights can be granted within 1 hour of revocation, otherwise, a reconfirmation vote election will be held.</span>
Line 20: Line 20:
#<span lang="en" dir="ltr" class="mw-content-ltr">Add template administrator permissions: Template administrators are used for templates and modules that require a high-risk sensitivity and may cause (effective/immmediate) damage if improperly edited. Unlike template editors, they are not packed into the administrator privileges and cannot be granted to their own account. They can edit pages not usually approved to administrators. No regular administrator can grant or revoke it, however bureaucrats can grant or revoke it as long as they are using this right properly. This permission is usually not meant for testing.</span>
#<span lang="en" dir="ltr" class="mw-content-ltr">Add template administrator permissions: Template administrators are used for templates and modules that require a high-risk sensitivity and may cause (effective/immmediate) damage if improperly edited. Unlike template editors, they are not packed into the administrator privileges and cannot be granted to their own account. They can edit pages not usually approved to administrators. No regular administrator can grant or revoke it, however bureaucrats can grant or revoke it as long as they are using this right properly. This permission is usually not meant for testing.</span>
#<span lang="en" dir="ltr" class="mw-content-ltr">Add IP block exemption permissions: This permission is used for bypassing Tor blocks and open proxy and VPN blocks. It can be granted or revoked by administrators, bureaucrats and stewards (and obviously, system administrators). It is packed into the administrators rights and can be used for testing.</span>
#<span lang="en" dir="ltr" class="mw-content-ltr">Add IP block exemption permissions: This permission is used for bypassing Tor blocks and open proxy and VPN blocks. It can be granted or revoked by administrators, bureaucrats and stewards (and obviously, system administrators). It is packed into the administrators rights and can be used for testing.</span>
#<span class="mw-translate-fuzzy">したがって、PHP のコードシーケンスは次のようになります。</span>


したがって、PHP のコードシーケンスは次のようになります。
<span lang="en" dir="ltr" class="mw-content-ltr">So, the following sequences of code in PHP are as follows:</span>


<div lang="en" dir="ltr" class="mw-content-ltr">
<div lang="en" dir="ltr" class="mw-content-ltr">