Difference between revisions of "Nookipedia:Proposals"

From Nookipedia, the Animal Crossing wiki
 
(80 intermediate revisions by 18 users not shown)
Line 4: Line 4:
 
*'''Proposals are ''only necessary'' for changes that would affect a large number of pages or users.''' Some examples: rules/policy changes, adding/removing namespaces, making major modifications to/replacing templates that affect 1000+ pages.
 
*'''Proposals are ''only necessary'' for changes that would affect a large number of pages or users.''' Some examples: rules/policy changes, adding/removing namespaces, making major modifications to/replacing templates that affect 1000+ pages.
  
*Proposals are for voting on fully worked out ideas. They should not have any yet-to-be-determined components: no 'option a, b, or c'. Proposals may be submitted without prior public comment or feedback, but should not receive major edits or changes once voting has started.
+
*Proposals are for voting on fully worked out ideas. They should be a binary yes/no choice and not have any yet-to-be-determined components: no 'option a, b, or c'. Proposals may be submitted without prior public comment or feedback, but should not receive major edits or changes once voting has started. If a proposal does not follow these rules or is otherwise deemed unfit, it may be vetoed at the discretion of a [[Nookipedia:Bureaucrats|Bureaucrat]].
  
 
*Proposals can only be submitted and voted upon by registered users. Comments or votes from unregistered users will be removed immediately. Furthermore, all votes or comments must have a signature attached ({{c|<nowiki>~~~~</nowiki>}}). Users are not allowed to vote on their own proposal, but may respond to comments.
 
*Proposals can only be submitted and voted upon by registered users. Comments or votes from unregistered users will be removed immediately. Furthermore, all votes or comments must have a signature attached ({{c|<nowiki>~~~~</nowiki>}}). Users are not allowed to vote on their own proposal, but may respond to comments.
  
*Proposals will be open for seven days. This voting deadline can be extended upon request, at the discretion of a [[Nookipedia:Bureaucrats|Bureaucrat]].
+
*Proposals will be open for seven days. This voting deadline can be extended upon request, at the discretion of a Bureaucrat.
  
*At the end of the voting period, if the proposal has at least a 2/3 majority (66%) it will be considered successful. A Bureaucrat will then officially close the proposal, and either enact it themselves, or coordinate with other staff members to make sure the proposal is completed.
+
*At the end of the voting period, if the proposal has at least a 2/3 majority (66%) support and five total votes it will be considered successful. A Bureaucrat will then officially close the proposal, and either enact it themselves, or coordinate with other staff members to make sure the proposal is completed.
  
*Once a proposal has been enacted, the [[Nookipedia:Staff|staff member]] responsible will make a note here and move the proposal to the [[Nookipedia:Proposals/Archive|Archives]].  
+
**If the proposal does not have five votes at the end of the voting period, the voting period will be extended for seven days.
 +
 
 +
*Once a proposal has been enacted, the [[Nookipedia:Staff|staff member]] responsible will make a note here and move the proposal to the [[Nookipedia:Proposals/Archive|Archives]].
  
 
==How to make a proposal==
 
==How to make a proposal==
Line 27: Line 29:
  
 
==Current proposals==
 
==Current proposals==
 +
===Changing the capitalization policy===
 
{{proposal
 
{{proposal
| title = Change item capitalization policy to match in-game capitalization
+
| title = Changing the capitalization policy
| description = I am proposing that we change our policy and item capitalization to use the in-game capitalization—which is generally all lowercase except for proper nouns—for all item names. This proposal has been divided into sections for ease of reading:
+
| description = How about we change the capitalization policy so that every letter in the title has to be capitalized except words like "the" and "and"? The English grammar is like that, and Nookipedia should probably follow it. I know this will effect ''<u>so</u>'' many pages, but again, I think it is necessary. [[File:ACL.png|20px]] [[User:Acnh Player|<span style="font-family:Coustard;color:#448EE4">'''Acnh Player'''</span>]] [[User talk:Acnh Player|<span style="font-family:Coustard;color:#1C662A">'''(talk)'''</span>]] [[File:ACL.png|20px]] 14:35, April 14, 2024 (EDT)
  
;History of our item capitalization policy
+
| comments =
Right now, our [[Nookipedia:Manual of Style#Capitalization|policy for the capitalization of item names]] defined on our general [[Nookipedia:Policy|policy page]] and in our [[Nookipedia:Manual of Style|Manual of Style]] is to use title case, regardless of the in-game capitalization, as enacted by a [[Nookipedia:Polls#Ninth poll (August 13, 2014 - August 18, 2014)|2014 poll]]. The reasoning behind the decision to make a policy regarding item names was brought forth by the staff largely due to the wiki at the time having inconsistent standards between pages (some pages used in-game capitalization, some used title case), but it was left to a poll because there was no consensus on which system to use. Since the policy's enactment, two discussions ([[Nookipedia_talk:Policy#Not_exactly_agreeing_with_capitalization_policy|one in 2015]] and [[Nookipedia_talk:The_Roost/2020#Regarding_the_capitalization_of_item_names|one in 2020]]) were started in opposition of the policy and how it was decided. In both discussions, the consensus was that a poll was not a great way to gather the opinions of readers and editors, though neither discussion led to any changes in the policy.
+
*Personally, I feel the capitalization policy is perfectly fine as it is and actually refers to in-game capitalization. I can understand the meaning of your message, but the wording is a bit clumsy- is that how you phrase it? [[User:Raven Star|Raven Star]] ([[User talk:Raven Star|talk]]) 14:42, April 14, 2024 (EDT)
 +
*The rules for capitalizing each word in a title generally only apply to published works or works of art. For anything else (including wiki articles), the titles are subject to whatever style guide the website/organization has in place. In our case, that is the [[Nookipedia:Manual of Style#Capitalization|Manual of Style]], which dictates that article and section names should be in sentence case, and I see no reason to change that. '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 18:47, April 14, 2024 (EDT)
 +
**U R WRONG [[File:ACL.png|20px]] [[User:Acnh Player|<span style="font-family:Coustard;color:#448EE4">'''Acnh Player'''</span>]] [[User talk:Acnh Player|<span style="font-family:Coustard;color:#1C662A">'''(talk)'''</span>]] [[File:ACL.png|20px]] 18:53, April 14, 2024 (EDT)
 +
***No u r wrong [[User:Lexy|Lexy]] ([[User talk:Lexy|talk]]) 14:24, April 15, 2024 (EDT)
 +
****Hm u didn't even vote. [[File:ACL.png|20px]] [[User:Acnh Player|<span style="font-family:Coustard;color:#448EE4">'''Acnh Player'''</span>]] [[User talk:Acnh Player|<span style="font-family:Coustard;color:#1C662A">'''(talk)'''</span>]] [[File:ACL.png|20px]] 19:07, April 15, 2024 (EDT)
 +
| votes =
 +
*{{Oppose}} As per my above comment. [[User:Raven Star|Raven Star]] ([[User talk:Raven Star|talk]]) 14:42, April 14, 2024 (EDT)
 +
*{{Oppose}} '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 18:47, April 14, 2024 (EDT)
 +
*{{Oppose}} -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 01:36, April 15, 2024 (EDT)
 +
*{{Oppose}} [[User:Drago|<span style="font-family:Coustard;color:green">Drago</span>]] [[User talk:Drago|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Drago PC Villager Icon.png|20px]] 10:41, April 15, 2024 (EDT)
 +
* {{Oppose}} We already decided to follow in-game capitalization for in-game terms. As AlexBot2004 says, wiki articles are not titled like they are published works. If anything it would lead to more confusion and inconsistency. [[User:Chubby Bub|Chubby Bub]] ([[User talk:Chubby Bub|talk]]) 23:01, April 15, 2024 (EDT)
 +
| year = 2024
 +
| month = 4
 +
| day = 21
 +
| hour = 14
 +
| minute = 35
 +
| percent = <!--Staff use only.-->
 +
| result = <!--Staff use only.-->
 +
| staffsig = <!--Staff use only.-->
 +
}}
  
;Why we should change the policy
+
===Policies regarding staff promotions/demotions===
I am proposing to use in-game capitalization for one main reason: it would be the most official way to present these names. We use official terms as they are in the games for all other subjects, so why should items be any different? I feel that capitalization is just as much a part of a subject's official name as anything else.
+
{{proposal
 +
| title = Policies regarding staff promotions/demotions
 +
| description = This proposal contains several changes to the staff application/promotion process as well as new policies regarding staff demotions.
  
The capitalization of item names is not just aesthetic; it has practical effects. There are plenty of items that ''do'' use proper nouns in-game, and with our system of making everything a proper noun, the actual proper nouns in the original names are lost. Another issue with our current policy is shown with the "Snowman vanity" (uppercase "S") in the North American version of {{CF|short|nolink}}, which was changed to "snowman vanity" (lowercase "s") in the European version. With our current system, there is no way to convey to the reader that the name was changed without either breaking our policy or having an awkward note.
+
;Application/Promotion
 +
If accepted, the following policies will be integrated into the [[Nookipedia:Staff/Apply|staff application page]].
 +
*Staff applications will require a minimum of 5 votes before the result can be determined. If the voting period ends before 5 votes are cast, the voting period will be extended for 7 days.
 +
----
 +
*Non-staff must start out as a Patroller. Our current policy merely suggests that non-staff start out as a Patroller, but this policy will require it. The only exceptions are users who were previously Administrators or Bureaucrats and either resigned or were demoted due to inactivity; these users can apply directly for their previous position.
 +
----
 +
*Patrollers must wait 2 months before they can apply for Administrator, and Administrators must wait 2 months before they can apply for Bureaucrat.
 +
----
 +
*A user who successfully applies for staff must add a verified email address to their account before they can be promoted. If one is not added within 30 days of a successful staff application, the application will be rendered null and the user will not become staff.
 +
*On a similar note, Administrators who successfully apply for a Bureaucrat position must enable [[Help:Two-factor authentication|two-factor authentication]] on their account before they can be promoted. If it is not enabled within 30 days of a successful application, the application will be rendered null and the user will not be promoted.
 +
;Demotion
 +
There are currently no official rules on staff demotion. If accepted, the following policies will be documented on a new policy page.
 +
*If a staff member has not edited the wiki in over a year, they will be removed from their position.
 +
**If the user resumes activity on the wiki, they may return to their previous position within a year of their demotion. After a year, the user must go through the staff application process again.
 +
**Only wiki edits make a user 'active' in this regard. Activity in the Discord server or anywhere else off-wiki does not count.
 +
:''Note: If this proposal passes, any staff members who have already not edited in over a year will have a 30-day grace period after it goes into effect to resume activity before they will be demoted.''
 +
----
 +
*Any staff member may voluntarily step down from their staff position or move down to a lower position (e.g. Bureaucrat to Administrator)
 +
**If the user wishes, they may return to their previous position within a year of their resignation. After a year, the user must go through the staff application process again.
 +
----
 +
*If an existing staff member removes their email address from their account, they will have 30 days to re-add it or add a different email, after which they will be removed from the staff.
 +
*If an existing Bureaucrat removes two-factor authentication from their account, they will have 30 days to re-enable it, after which they will be demoted to Administrator.
 +
----
 +
*If a staff member does not utilize their abilities as staff, improperly utilizes them, or is otherwise seen as unfit to be staff, they may be expelled from the staff by a vote. Only Bureaucrats or Directors may call for a vote to expel another staff member. The vote will be held on the wiki and have the same rules as a staff application: support from 65% of voting staff members and a minimum of 5 total votes.
 +
**If an expulsion vote is called in bad faith, it may be vetoed by a Director.
 +
**An expelled user may apply for staff again as a Patroller (regardless of their previous position) after 6 months.
 +
----
 +
*If a staff member clearly abuses their staff powers, vandalizes the site, or does any other action that would result in a block, they will be blocked from editing and removed from their staff position immediately.
 +
----
 +
There's a lot here, but my hope is to remove some of the vagueness in our existing policies, as well as create new policies to account for all possible scenarios. Thank you for your time and consideration. '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 20:55, April 14, 2024 (EDT)
  
One point that was brought up in the 2015 discussion is that it would be hard to enact such a policy of using in-game capitalization since there was no accurate master item list for all games. Another point brought up in the 2020 discussion is that having item names in title case has stylistic value because makes it clear to the reader that these are actual in-game items and not generic terms. To respond to these two counter-arguments:
+
| comments =
#Today we have spreadsheets for every game in the series that use datamined names, so those would be our sources if this policy were to be enacted.
+
*Obviously not. Although I agree with the "minimum" vote, and non staff users can apply for anything, even bureaucrat. Plus, it should be a 80% agreement for demoting staff, because sometimes people are wrongly accused. '''''Plus, if there is no vote for demoting a staff that <u>clearly</u> abused tools, who in the world decides that it is a <u>clearly</u>? There should still be a vote when demoting staff who <u>clearly</u> abused tools.''''' Plus, staff that was removed and indefinitely barred from becoming staff again will just be mad and create a sockpuppet account. Plus, what if a director does something bad? Then a bureaucrat can propose a removal, but then the director removes it on sight. For example, lets say SuperHamster vandalizes every single page. But then, AlexBot2004 calls a proposal to remove him. And then SuperHamster can just remove that application because he is a director and can do that, as you mentioned above in your super-long boring description. [[File:ACL.png|20px]] [[User:Acnh Player|<span style="font-family:Coustard;color:#448EE4">'''Acnh Player'''</span>]] [[User talk:Acnh Player|<span style="font-family:Coustard;color:#1C662A">'''(talk)'''</span>]] [[File:ACL.png|20px]] 21:39, April 14, 2024 (EDT)
#The most common way items are mentioned in articles is through tables or other similar templates which isolate the name from any other text, making it clear to the reader that these aren't generic terms. Also, items should always be linked to their respective item pages, which would make it clear even in the prose that a term is not generic.
+
** I don't get this argument. So you're saying that if a admin abuses their rights in a clear malicious intent, we should wait by voting on their demotion instead of taking action immediately? Also, why assume the user's going to sockpuppet if they get banned? Staff rights is a responsibility, if anything goes wrong, we have to take action and take accountability for what goes on in the backstage. I'm confused. -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 01:36, April 15, 2024 (EDT)
 +
* Solid set of rules. I do have two recommended changes:
 +
** Regarding only a Bureaucrat being able to call for a vote to expel, I suggest it be Bureaucrats + Directors.
 +
** "A user removed from the staff in this manner will be indefinitely barred from becoming staff again" -> I think we can remove this line. While it's very likely a staff member removed for abuse would never be staff again, I don't like absolutes like this. It's theoretically possible for someone to come back years later, be productive, and be re-accepted as staff.
 +
* Other than that, the proposal looks great and I'm happy to support. '''~[[User:SuperHamster|''<span style="color:#07517C;">Super</span>''<span style="color:#6FA23B;">Hamster</span>]]''' <small>[[User talk:SuperHamster|Talk]] [[Special:Contribs/SuperHamster|Contribs]]</small> 02:40, April 15, 2024 (EDT)
 +
**I've gone ahead and made both of those changes. For the first point, I initially worded the expulsion vote sentence that way since Directors are inherently Bureaucrats, but it is good to clarify. For the second, now that I think about it more, I agree that it is better to not have absolutes regarding being barred from staff. '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 02:50, April 15, 2024 (EDT)
 +
***Thank you! '''~[[User:SuperHamster|''<span style="color:#07517C;">Super</span>''<span style="color:#6FA23B;">Hamster</span>]]''' <small>[[User talk:SuperHamster|Talk]] [[Special:Contribs/SuperHamster|Contribs]]</small> 03:25, April 15, 2024 (EDT)
 +
*Sure I changed my vote. {{Unsigned|Acnh Player}}
 +
* Another hypothetical situation where we might want to reallow someone who acts disruptively is if their account was demonstrably hacked or accessed by someone else. [[User:Chubby Bub|Chubby Bub]] ([[User talk:Chubby Bub|talk]]) 22:56, April 15, 2024 (EDT)
 +
| votes =
 +
* {{Support}} I changed my vote lol. [[File:ACL.png|20px]] [[User:Acnh Player|<span style="font-family:Coustard;color:#448EE4">'''Acnh Player'''</span>]] [[User talk:Acnh Player|<span style="font-family:Coustard;color:#1C662A">'''(talk)'''</span>]] [[File:ACL.png|20px]] 19:05, April 15, 2024 (EDT)
 +
* {{Support}} These changes are definitely well needed especially given the lack of activity by most of our staff, and the fact that info on admin abuse is definitely well warranted. -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 01:36, April 15, 2024 (EDT)
 +
* {{Support}} '''~[[User:SuperHamster|''<span style="color:#07517C;">Super</span>''<span style="color:#6FA23B;">Hamster</span>]]''' <small>[[User talk:SuperHamster|Talk]] [[Special:Contribs/SuperHamster|Contribs]]</small> 03:25, April 15, 2024 (EDT)
 +
* {{Support}} Yeah, I guess I'm mostly on board. The only sticking point I have is that two months in between positions is ''mildly'' arbitrary and I think focusing on experience prior to the position makes a little more sense, but I guess I can see the point in why it is done this way too. [[User:Trig Jegman|Trig Jegman]] - 10:22, April 15, 2024 (EDT)
 +
* {{Support}} [[User:Drago|<span style="font-family:Coustard;color:green">Drago</span>]] [[User talk:Drago|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Drago PC Villager Icon.png|20px]] 10:41, April 15, 2024 (EDT)
 +
* {{Support}} Thanks, --[[User:SunsetBay|<span style="font-family:Coustard;color:#D7A5E0">SunsetBay</span>]] ([[User talk:SunsetBay|<span style="font-family:Coustard;color:#F3B4EF">Talk</span>]]) [[File: Bob NL Villager Icon.png|25px]] 13:22, April 15, 2024 (EDT)
 +
* {{Support}} I had a few questions/concerns, mainly about absolutes, but they've now been addressed. [[User:Chubby Bub|Chubby Bub]] ([[User talk:Chubby Bub|talk]]) 22:56, April 15, 2024 (EDT)
 +
| year = 2024
 +
| month = 4
 +
| day = 21
 +
| hour = 20
 +
| minute = 55
 +
| percent = <!--Staff use only.-->
 +
| result = <!--Staff use only.-->
 +
| staffsig = <!--Staff use only.-->
 +
}}
  
As a wiki that covers content from the {{SER|nolink}} objectively and strives to be as accurate as possible, I believe there isn't a place on Nookipedia for a policy that makes us write item names contrary to how they appear in the games, especially for stylistic reasons.
+
===Adding more rights to patrollers===
 
+
{{proposal
;Other item-related terms
+
| title = Adding more rights to patrollers
There are also several non-item—but still item-related—terms that are not defined in our MoS, but still follow our item name policy on the wiki; namely HHA genres/themes and variant/pattern names. Any terms like these should be changed to in-game case just like the items themselves, for the same reasons stated above.
+
| description = I think patrollers should be able to block users and edit protected pages. {{Unsigned|Acnh Player}}
 
+
| comments = *I'm not sure if this should be voted on as a proposal, and it might be better for staff to decide. But I'll give my opinion anyway: this change would make Patrollers too similar to Administrators and the second promotion wouldn't feel like a big step up. There also isn't enough vandalism currently to justify needing more users with blocking rights. I do think we should re-assess the role of Patrollers on this wiki (this is nothing against the users who currently hold the position, simply that I think the position itself is flawed), but I'm not sure simply adding more rights is the best way to do that. [[User:Drago|<span style="font-family:Coustard;color:green">Drago</span>]] [[User talk:Drago|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Drago PC Villager Icon.png|20px]] 11:47, April 17, 2024 (EDT)
That being said, I am not proposing any changes to our furniture collection (series/set/theme) terminology in this proposal. Their full names aren't clearly defined via in-game strings like the other terms; the first part (e.g. "blue", "lovely", "modern") is defined, but the "series"/"set"/"theme" part, as far as I can tell, is just an internal property and is never appended to the name in-game. I think these warrant their own proposal to determine what we call them going forward, but at the moment, they can stay at their current names.
+
| votes = *{{Oppose}} --[[User:Drago|<span style="font-family:Coustard;color:green">Drago</span>]] [[User talk:Drago|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Drago PC Villager Icon.png|20px]] 11:47, April 17, 2024 (EDT)
 
+
* {{Oppose}} per Drago '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 00:38, April 18, 2024 (EDT)
I also want to make it clear that this policy would not affect item image filenames; the standard for all filenames is title case and I see no need to change that.
+
| year = 2024
 
+
| month = 4
;How we would implement this policy
+
| day = 22
This is the format I am proposing we use going forward:
+
| hour = 18
*In the prose of an article: write item names exactly as they are in-game, except for (obviously) capitalizing the first letter if it is at the beginning of a sentence.
+
| minute = 51
*In tables and templates like {{t|House Info}}: capitalize the first letter; these will be essentially treated as sentences.
 
*In item page infoboxes:
 
:*In the "name" parameter of the template, capitalize the first letter; these will be essentially treated as sentences. This will be what is displayed in the infobox and what is queried in Cargo for item tables.
 
:*In the "en-name" parameter of the template, write item names exactly as they are in-game. This will be stored to Cargo and can be queried if needed.
 
 
 
With thousands of item pages and even more mentions of items across the wiki, it will take a while for everything to be fully updated, but it will certainly be possible. Item pages would be automatically moved and their prose would be updated via text replacements, as would standardized templates such as the villager housing templates. Updating the item pages would in turn automatically update every Cargo item table; for non-Cargo tables, those will be replaced in due course with Cargo tables as item pages for all the games are created. The only thing that I don't think can be updated automatically would be mentions of items in the prose of mainspace articles; however, these take up such a small amount of the mentions of items across the wiki relative to the others I've listed that it could be done manually.
 
 
 
This was a long proposal, but for a change as large as this I feel I needed to go into as much detail as possible. Thank you for your time and consideration. '''~'''&nbsp;[[User:AlexBot2004|<span style="font-family:Coustard;color:#1C662A">'''AlexBot2004'''</span>]]&nbsp;([[User talk:AlexBot2004|<span style="font-family:Coustard;color:black">Talk</span>]]) 00:00, November 19, 2022 (EST)
 
 
 
| comments = I'm kinda conflicted with this notion. On one hand, I think this is accurate, and I'm certain of using the in-game names as best as possible, I understand why this is necessary for us, and if anything it'll probably be better off to use the actual in-game names.
 
 
 
On the other hand, I'm not very confident that things will remain functional as it is. I'd have to go through some of the worst cargo tables and change <code>name</code> to  <code>en_name</code>, and with how slow some of these pages are, I feel like the worst cargo tables will just break again. If we want to assure we actually abide by the in-game names, I think we need to look into how the item names are being used at a technical point, and see if it'll be able to run without issues. -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 00:42, November 19, 2022 (EST)
 
| votes =
 
| year = 2022
 
| month = 11
 
| day = 26
 
| hour = 00
 
| minute = 00
 
 
| percent = <!--Staff use only.-->
 
| percent = <!--Staff use only.-->
 
| result = <!--Staff use only.-->
 
| result = <!--Staff use only.-->
Line 78: Line 138:
 
}}
 
}}
  
{{Nookipedia}}
+
{{Navbox Nookipedia}}

Latest revision as of 00:39, April 18, 2024

Nookipedia Proposals allow the community to vote on sitewide changes that would affect a large number of pages or users. This process is not a replacement for community-wide input (see:The Roost) or talk page discussion. Rather, it takes the final product of those discussions (in the form of a proposal) and puts them to a vote.

Rules[edit]

  • Proposals are only necessary for changes that would affect a large number of pages or users. Some examples: rules/policy changes, adding/removing namespaces, making major modifications to/replacing templates that affect 1000+ pages.
  • Proposals are for voting on fully worked out ideas. They should be a binary yes/no choice and not have any yet-to-be-determined components: no 'option a, b, or c'. Proposals may be submitted without prior public comment or feedback, but should not receive major edits or changes once voting has started. If a proposal does not follow these rules or is otherwise deemed unfit, it may be vetoed at the discretion of a Bureaucrat.
  • Proposals can only be submitted and voted upon by registered users. Comments or votes from unregistered users will be removed immediately. Furthermore, all votes or comments must have a signature attached (~~~~). Users are not allowed to vote on their own proposal, but may respond to comments.
  • Proposals will be open for seven days. This voting deadline can be extended upon request, at the discretion of a Bureaucrat.
  • At the end of the voting period, if the proposal has at least a 2/3 majority (66%) support and five total votes it will be considered successful. A Bureaucrat will then officially close the proposal, and either enact it themselves, or coordinate with other staff members to make sure the proposal is completed.
    • If the proposal does not have five votes at the end of the voting period, the voting period will be extended for seven days.
  • Once a proposal has been enacted, the staff member responsible will make a note here and move the proposal to the Archives.

How to make a proposal[edit]

All proposals must be made using the template provided below, posted under the "Current Proposals" heading:

{{proposal
| title       = A short, one-sentence description of the proposal.
| description = Additional proposal details/explanation.
| comments    = User commentary on proposal.
| votes       = User votes on proposal: {{Support}} or {{Oppose}} + signature (~~~~).
}}

Current proposals[edit]

Changing the capitalization policy[edit]

Proposal: Changing the capitalization policy
How about we change the capitalization policy so that every letter in the title has to be capitalized except words like "the" and "and"? The English grammar is like that, and Nookipedia should probably follow it. I know this will effect so many pages, but again, I think it is necessary. ACL.png Acnh Player (talk) ACL.png 14:35, April 14, 2024 (EDT)
Comments:
  • Personally, I feel the capitalization policy is perfectly fine as it is and actually refers to in-game capitalization. I can understand the meaning of your message, but the wording is a bit clumsy- is that how you phrase it? Raven Star (talk) 14:42, April 14, 2024 (EDT)
  • The rules for capitalizing each word in a title generally only apply to published works or works of art. For anything else (including wiki articles), the titles are subject to whatever style guide the website/organization has in place. In our case, that is the Manual of Style, which dictates that article and section names should be in sentence case, and I see no reason to change that. ~ AlexBot2004 (Talk) 18:47, April 14, 2024 (EDT)
Votes:
  • Oppose Oppose As per my above comment. Raven Star (talk) 14:42, April 14, 2024 (EDT)
  • Oppose Oppose ~ AlexBot2004 (Talk) 18:47, April 14, 2024 (EDT)
  • Oppose Oppose -- PanchamBro (talkcontributions) 01:36, April 15, 2024 (EDT)
  • Oppose Oppose Drago (talk) Drago PC Villager Icon.png 10:41, April 15, 2024 (EDT)
  • Oppose Oppose We already decided to follow in-game capitalization for in-game terms. As AlexBot2004 says, wiki articles are not titled like they are published works. If anything it would lead to more confusion and inconsistency. Chubby Bub (talk) 23:01, April 15, 2024 (EDT)
Result: (??%) To be determined.

There are 3 days, 9 hours, 29 minutes and 38 seconds until voting closes. (refresh)

Policies regarding staff promotions/demotions[edit]

Proposal: Policies regarding staff promotions/demotions
This proposal contains several changes to the staff application/promotion process as well as new policies regarding staff demotions.
Application/Promotion

If accepted, the following policies will be integrated into the staff application page.

  • Staff applications will require a minimum of 5 votes before the result can be determined. If the voting period ends before 5 votes are cast, the voting period will be extended for 7 days.

  • Non-staff must start out as a Patroller. Our current policy merely suggests that non-staff start out as a Patroller, but this policy will require it. The only exceptions are users who were previously Administrators or Bureaucrats and either resigned or were demoted due to inactivity; these users can apply directly for their previous position.

  • Patrollers must wait 2 months before they can apply for Administrator, and Administrators must wait 2 months before they can apply for Bureaucrat.

  • A user who successfully applies for staff must add a verified email address to their account before they can be promoted. If one is not added within 30 days of a successful staff application, the application will be rendered null and the user will not become staff.
  • On a similar note, Administrators who successfully apply for a Bureaucrat position must enable two-factor authentication on their account before they can be promoted. If it is not enabled within 30 days of a successful application, the application will be rendered null and the user will not be promoted.
Demotion

There are currently no official rules on staff demotion. If accepted, the following policies will be documented on a new policy page.

  • If a staff member has not edited the wiki in over a year, they will be removed from their position.
    • If the user resumes activity on the wiki, they may return to their previous position within a year of their demotion. After a year, the user must go through the staff application process again.
    • Only wiki edits make a user 'active' in this regard. Activity in the Discord server or anywhere else off-wiki does not count.
Note: If this proposal passes, any staff members who have already not edited in over a year will have a 30-day grace period after it goes into effect to resume activity before they will be demoted.

  • Any staff member may voluntarily step down from their staff position or move down to a lower position (e.g. Bureaucrat to Administrator)
    • If the user wishes, they may return to their previous position within a year of their resignation. After a year, the user must go through the staff application process again.

  • If an existing staff member removes their email address from their account, they will have 30 days to re-add it or add a different email, after which they will be removed from the staff.
  • If an existing Bureaucrat removes two-factor authentication from their account, they will have 30 days to re-enable it, after which they will be demoted to Administrator.

  • If a staff member does not utilize their abilities as staff, improperly utilizes them, or is otherwise seen as unfit to be staff, they may be expelled from the staff by a vote. Only Bureaucrats or Directors may call for a vote to expel another staff member. The vote will be held on the wiki and have the same rules as a staff application: support from 65% of voting staff members and a minimum of 5 total votes.
    • If an expulsion vote is called in bad faith, it may be vetoed by a Director.
    • An expelled user may apply for staff again as a Patroller (regardless of their previous position) after 6 months.

  • If a staff member clearly abuses their staff powers, vandalizes the site, or does any other action that would result in a block, they will be blocked from editing and removed from their staff position immediately.

There's a lot here, but my hope is to remove some of the vagueness in our existing policies, as well as create new policies to account for all possible scenarios. Thank you for your time and consideration. ~ AlexBot2004 (Talk) 20:55, April 14, 2024 (EDT)

Comments:
  • Obviously not. Although I agree with the "minimum" vote, and non staff users can apply for anything, even bureaucrat. Plus, it should be a 80% agreement for demoting staff, because sometimes people are wrongly accused. Plus, if there is no vote for demoting a staff that clearly abused tools, who in the world decides that it is a clearly? There should still be a vote when demoting staff who clearly abused tools. Plus, staff that was removed and indefinitely barred from becoming staff again will just be mad and create a sockpuppet account. Plus, what if a director does something bad? Then a bureaucrat can propose a removal, but then the director removes it on sight. For example, lets say SuperHamster vandalizes every single page. But then, AlexBot2004 calls a proposal to remove him. And then SuperHamster can just remove that application because he is a director and can do that, as you mentioned above in your super-long boring description. ACL.png Acnh Player (talk) ACL.png 21:39, April 14, 2024 (EDT)
    • I don't get this argument. So you're saying that if a admin abuses their rights in a clear malicious intent, we should wait by voting on their demotion instead of taking action immediately? Also, why assume the user's going to sockpuppet if they get banned? Staff rights is a responsibility, if anything goes wrong, we have to take action and take accountability for what goes on in the backstage. I'm confused. -- PanchamBro (talkcontributions) 01:36, April 15, 2024 (EDT)
  • Solid set of rules. I do have two recommended changes:
    • Regarding only a Bureaucrat being able to call for a vote to expel, I suggest it be Bureaucrats + Directors.
    • "A user removed from the staff in this manner will be indefinitely barred from becoming staff again" -> I think we can remove this line. While it's very likely a staff member removed for abuse would never be staff again, I don't like absolutes like this. It's theoretically possible for someone to come back years later, be productive, and be re-accepted as staff.
  • Other than that, the proposal looks great and I'm happy to support. ~SuperHamster Talk Contribs 02:40, April 15, 2024 (EDT)
    • I've gone ahead and made both of those changes. For the first point, I initially worded the expulsion vote sentence that way since Directors are inherently Bureaucrats, but it is good to clarify. For the second, now that I think about it more, I agree that it is better to not have absolutes regarding being barred from staff. ~ AlexBot2004 (Talk) 02:50, April 15, 2024 (EDT)
  • Sure I changed my vote. - unsigned comment from Acnh Player (talkcontribs)
  • Another hypothetical situation where we might want to reallow someone who acts disruptively is if their account was demonstrably hacked or accessed by someone else. Chubby Bub (talk) 22:56, April 15, 2024 (EDT)
Votes:
  • Support Support I changed my vote lol. ACL.png Acnh Player (talk) ACL.png 19:05, April 15, 2024 (EDT)
  • Support Support These changes are definitely well needed especially given the lack of activity by most of our staff, and the fact that info on admin abuse is definitely well warranted. -- PanchamBro (talkcontributions) 01:36, April 15, 2024 (EDT)
  • Support Support ~SuperHamster Talk Contribs 03:25, April 15, 2024 (EDT)
  • Support Support Yeah, I guess I'm mostly on board. The only sticking point I have is that two months in between positions is mildly arbitrary and I think focusing on experience prior to the position makes a little more sense, but I guess I can see the point in why it is done this way too. Trig Jegman - 10:22, April 15, 2024 (EDT)
  • Support Support Drago (talk) Drago PC Villager Icon.png 10:41, April 15, 2024 (EDT)
  • Support Support Thanks, --SunsetBay (Talk) Bob NL Villager Icon.png 13:22, April 15, 2024 (EDT)
  • Support Support I had a few questions/concerns, mainly about absolutes, but they've now been addressed. Chubby Bub (talk) 22:56, April 15, 2024 (EDT)
Result: (??%) To be determined.

There are 3 days, 15 hours, 49 minutes and 38 seconds until voting closes. (refresh)

Adding more rights to patrollers[edit]

Proposal: Adding more rights to patrollers
I think patrollers should be able to block users and edit protected pages. - unsigned comment from Acnh Player (talkcontribs)
Comments:
  • I'm not sure if this should be voted on as a proposal, and it might be better for staff to decide. But I'll give my opinion anyway: this change would make Patrollers too similar to Administrators and the second promotion wouldn't feel like a big step up. There also isn't enough vandalism currently to justify needing more users with blocking rights. I do think we should re-assess the role of Patrollers on this wiki (this is nothing against the users who currently hold the position, simply that I think the position itself is flawed), but I'm not sure simply adding more rights is the best way to do that. Drago (talk) Drago PC Villager Icon.png 11:47, April 17, 2024 (EDT)
Votes:
Result: (??%) To be determined.

There are 4 days, 13 hours, 45 minutes and 38 seconds until voting closes. (refresh)