Difference between revisions of "Nookipedia:Proposals"

From Nookipedia, the Animal Crossing wiki
(→‎Current proposals: CC 3.0 to 4.0 proposal passed)
 
(20 intermediate revisions by 12 users not shown)
Line 29: Line 29:
 
==Current proposals==
 
==Current proposals==
 
{{#ifexpr:{{PAGESINCATEGORY:Active proposals}}=0|There are no active proposals. For a record of past proposals, visit the [[Nookipedia:Proposals/Archive|Archive]].}} <!-- Place proposals below this line. -->
 
{{#ifexpr:{{PAGESINCATEGORY:Active proposals}}=0|There are no active proposals. For a record of past proposals, visit the [[Nookipedia:Proposals/Archive|Archive]].}} <!-- Place proposals below this line. -->
 +
 
{{proposal
 
{{proposal
−
| title      = Modifications and additions to Nookipedia Policy regarding user page content and community interaction
+
| title      = Migrate Nookipedia from CC BY-SA 3.0 to 4.0
−
| description = This proposal is in part a rework of a few ideas I proposed at [[Nookipedia talk:Policy]] in January of 2022, but also includes a few additional policies which aim to a) clarify some gray areas surrounding user talk pages and b) establish policy regarding backseat moderation.
+
| description = Nookipedia is, like many other wikis, licensed under [https://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA 3.0]. This proposal is to migrate Nookipedia to using [https://creativecommons.org/licenses/by-sa/4.0/ version 4.0] of the same license. 4.0 has been available since 2013, and includes some good improvements and common sense changes -- see [https://creativecommons.org/version4/ this article] for full details. Improvements include explicitly allowing attribution by linking to a history page (practical for wikis); a 30-day window to correct license violations; and better internationalization.
  
−
Additions to existing policy (in bold):
+
Wikipedia moved to 4.0 last year (see [https://creativecommons.org/2023/06/29/wikipedia-moves-to-cc-4-0-licenses/ this blog post]), and a growing number of our fellow NIWA wikis have migrated (or plan to) this year (Inkipedia, Pikipedia, etc.).
  
−
<blockquote>
+
Regarding implementation: Creative Commons licenses are forward-compatible, which means that if you adapt a CC 3.0 work, you can license it under 4.0. For Nookipedia, this means that all existing content can and always will be considered to be a 3.0 work, but as new edits are made and articles become derivatives of themselves, they will be considered a 4.0 work.
−
''User page content''<br>
 
−
4. Other than for necessary basic maintenance edits '''and reverting vandalism''', editing '''or reverting changes to''' another user's user page is not allowed, even when censoring or correcting spelling or grammar. Concerns about user page content should be directed to Nookipedia Administrators or Bureaucrats.
 
−
<br><br>
 
−
''Community interaction''<br>
 
−
5. Do not remove other users' messages '''or revert edits to their talk page''', except in clear cases of vandalism, personal attacks, being off-topic, or maintenance (removing duplicate messages, moving to correct talk page, etc.).
 
−
*'''As an exception, welcome messages and mass invites (e.g. "Invitation to Summer of Edits...") posted to one's own user talk page may be removed by the talk page owner.'''
 
−
'''6. Talk page messages older than 1 month may be moved by the talk page owner to an archive page, so long as a link to the archive is clearly provided on the user's talk page. Official warnings or messages from staff members concerning a user's edits or behavior may be archived after 6 months.'''
 
−
<br><br>
 
−
'''7. Do not interpret Nookipedia policy or enforce policy violations on behalf of staff members.'''
 
−
*'''With the exception of blatant spam or vandalism, which can be reverted by any user, all other potential policy violations should be posted to the Staff noticeboard or to the official Discord server (ping @staff) so that a staff member can take appropriate action.'''
 
−
*'''Editors should not speak with a tone of authority in comments or edit summaries in regard to potential policy violations. Doing so is considered backseat moderating and may result in a warning.'''</blockquote>
 
−
:::[[File:Sunmarshsignature.png|link=User:Sunmarsh]] '''<small><span style="font-variant:small-caps">([[User_talk:Sunmarsh|<span style="color:#7B7B7B">talk</span>]])</span></small>''' 23:59, July 21, 2024 (EDT)
 
−
| comments    =
 
−
* I think changes to 4 and 5 are fine. Addition 6 concerns me slightly as I think it somewhat encourages a more constant stream of archival which is not useful. It seems pointedly addressing a single user case over the span of recent years and I don't think it's helpful for any party. I would just have the site suggest to archive after "significant time has passed" and after some significant size, whether thats bytes or headers. I'm also pretty iffy about point 7, because it effectively removes the ability for editors to enforce already defined policies. The line in particular causing concern is <code>Editors should not speak with a tone of authority in comments or edit summaries in regard to potential policy violations.</code> (although most of it is in the same realm). For an example, if a user is overtly violating the [[Nookipedia:Upload policy]] through the first bulled point <code>When uploading the file, be sure to give it a meaningful name which describes its content.</code>, I'm not permitted to inform that user via talk page or edit summary that they are not following the policy (even though it is clearly defined via page)—or at least, that's how this policy change is conveyed. I think it's an overreach to stop users from micromanaging which more often then not needs to be a more direct intervention than a blanket fix. Because of my support for only half of the proposed changes, and distaste for the other half, I find it impossible to vote on this proposal at all and simply leave my commentary behind for reference. [[User:Trig Jegman|Trig Jegman]] - 00:55, July 22, 2024 (EDT)
 
−
::I appreciate your feedback, although I am a bit confused by what you mean by "It seems pointedly addressing a single user case over the span of recent years and I don't think it's helpful for any party." Could you be a bit more specific about the user case you're referring to and how this policy would be unhelpful? This policy was meant to address the grey area established by the existing point #5: "Do not remove other users' messages...". As it stands, archives of user talk pages are not explicitly permitted by the existing policy. This addition simply provides a framework for when it's acceptable to move talk page messages and warnings. The original time frame that I proposed internally to staff members when I was seeking feedback on this proposal was 1 year. This time period makes sense to me, as generally user talk pages do not receive a high level of activity, however this didn't take into account factors like site or user activity; a user who is very active or involved in the community, or who is active during periods of high site activity (like around the time of a new game release), would benefit from a shorter archive threshold as it would make their talk page more manageable/easier to navigate. While I appreciate the flexibility that language like "significant time has passed" allows for, I feel like it's not particularly helpful as it makes the policy unenforceable; what may be "significant" for one user may not be for another. Lastly, I just wanted to clarify here that an additional reason for this policy addition is that we've recently had issues surrounding user talk pages (including removal of user messages and warnings) by disruptive users, and so this policy change is also aimed at making it very clear the acceptable and unacceptable ways to go about this.
 
  
−
::As for point #7, these were my same concerns with this policy addition, and I would be interested in your suggestions on how to achieve the right balance here. The goal of this policy is not to require users to defer to staff to address comparatively minor issues like upload policy violations. Its goal is to make clear that users who are not staff should not be taking actions to remedy their own perceived policy violations, or mimicking staff behavior. As with #6 it was also created in an attempt to address recent disruptive behavior where the user in question was trying to act like a staff member by moderating edits and users. There is a difference between bringing something to another user's attention versus telling someone they are wrong or reverting edits based off perceived policy violations, which in this case were incorrect. In short, it's one thing to be correctly enforcing the policy, and another to be enforcing it wrong because you don't know it or don't understand it, and so this policy addition tries to make it clear that those who are not in a position to properly enforce the policy should not be doing so. Again, if you have any suggestions on how to improve the language so that it strikes the right balance I'd appreciate your suggestions. [[File:Sunmarshsignature.png|link=User:Sunmarsh]] '''<small><span style="font-variant:small-caps">([[User_talk:Sunmarsh|<span style="color:#7B7B7B">talk</span>]])</span></small>''' 02:54, July 22, 2024 (EDT)
+
Regarding impact: This change has very little impact to the day-to-day experience of our editors and readers. Most impact would be seen by text re-use between Nookipedia and others. While Creative Commons versions are forward compatible, they are not backwards compatible. This means that 3.0 works can be used in a 4.0 work, but 4.0 works can't be used in a 3.0 work. By moving to 4.0, we will be better aligned with other wikis on 4.0, and can adapt both 3.0 and 4.0 text. Inversely, any wikis on 3.0 looking to re-use Nookipedia's 4.0 text won't be able to, but can also migrate to 4.0 if they wish.
−
* Hi, I really like this. It sounds good. {{Support}}. I just have one question. What do you mean by an ‘authoritative tone’? I think that there should be a list of identifying things specifying what is authoritative and what is not. Just because I don’t really get what it means, and other people might not too. 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]] 14:32, July 25, 2024 (EDT)
 
−
** I'm not sunmarsh, but I think I can answer this. In this case, "authoritative tone" means acting in a way that could make an uninformed user believe you are a staff member. There's no way to neatly define exactly what behavior constitutes that in a way that covers all possible cases while also not having false positives, so it's best to leave the interpretation of it up to the staff members on a case-by-case basis. This reason is also part of why point #7 is so important; policy is sometimes vague and up to interpretation, and in cases like that, non-staff should not be the ones to interpret it. '''~&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:26, July 28, 2024 (EDT)
 
−
***That makes sense, thanks! 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]] 06:37, July 29, 2024 (EDT)
 
−
*Unfortunately I'm going to have to oppose this proposal in its current form. I agree with most of the changes, but point #7 suggests that editors won't be able to remove anything from articles that violates a policy, and I think editors should have more freedom to remove things from articles that don't belong. On most open-editing wikis like ours, content can be added, removed and edited by anyone and I don't want to interfere with that. I also think that leaving a friendly message on a user talk page to point out that their edits may be inappropriate is acceptable too, as long as they're not being authoritative, but I do think comments that threaten disciplinary action (e.g. "Further changes like these may result in an official warning or block") should be left to the staff. Since a proposal can't receive major changes after voting starts, I'm opposing for now. [[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:42, July 28, 2024 (EDT)
 
−
*I'm in support of this proposal in its current form. If changes need to be done to address what has been stated by others above, that's okay. But I have always been opposed to users trying to skirt around warnings, changes to userspaces thaat are not their own, and trying to pose as staff. The latter can be especially confusing for new editors as they wouldn't know who is and isn't on the team, so they in good faith trust their judgement. Anything to prevent this is good in my book, but I'm open to see what changes take place if this proposal was to be revised and brought back later on. <nowiki>~</nowiki>[[User:PoizonMushro0m|<span style="color:#32CD32">'''Poizon'''</span>]][[User talk:PoizonMushro0m|<span style="color:#228B22">'''Mushro0m'''</span>]][[File:PoizonMush Sig.png|link=Special:Contributions/PoizonMushro0m|15px]] 16:44, July 28, 2024 (EDT)
 
−
 
 
−
*{{Oppose}} I don't really like how staff members can't really censor on User pages and User talk pages, I feel like staff members should due to younger audiences. Also, Users should be able to revert inappropriate behavior right away, just so almost nobody sees it. I feel like backseat moderating is bad so well done, but some stuff feels a bit wrong. [[User:SpaceBean|<span style="font-family:Coustard;color:pink">SpaceBean</span>]] [[User talk:SpaceBean|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Rosie PC Villager Icon.png|20px]] 10:42, July 28, 2024 (EDT)[[User:SpaceBean|SpaceBean]] ([[User talk:SpaceBean|talk]])
 
  
 +
'''~[[User:SuperHamster|''<span style="color:#07517C;">Super</span>''<span style="color:#6FA23B;">Hamster</span>]]''' <small>[[User talk:SuperHamster|Talk]] [[Special:Contribs/SuperHamster|Contribs]]</small> 17:48, October 19, 2024 (EDT)
 +
| year        = 2024
 +
| month      = 10
 +
| day        = 26
 +
| hour        = 17
 +
| minute      = 49
 +
| comments    =
 
| votes      =  
 
| votes      =  
−
*{{Support}} '''~&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:26, July 28, 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> 17:48, October 19, 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:42, July 28, 2024 (EDT)
+
* {{Support}} -- [[User:PanchamBro|PanchamBro]] ([[User talk:PanchamBro|talk]] • [[Special:Contributions/PanchamBro|contributions]]) 21:28, October 19, 2024 (EDT)
−
*{{Support}} <nowiki>~</nowiki>[[User:PoizonMushro0m|<span style="color:#32CD32">'''Poizon'''</span>]][[User talk:PoizonMushro0m|<span style="color:#228B22">'''Mushro0m'''</span>]][[File:PoizonMush Sig.png|link=Special:Contributions/PoizonMushro0m|15px]] 16:44, July 28, 2024 (EDT)
+
*{{Support}} '''~&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>]]) 04:03, October 20, 2024 (EDT)
−
*{{Support}} {{User:Lampshade59276/sig}} 17:01, July 28, 2024 (EDT)
+
*{{Support}} <nowiki>~</nowiki>[[User:PoizonMushro0m|<span style="color:#32CD32">'''Poizon'''</span>]][[User talk:PoizonMushro0m|<span style="color:#228B22">'''Mushro0m'''</span>]][[File:PoizonMush Sig.png|link=Special:Contributions/PoizonMushro0m|15px]] 04:20, October 20, 2024 (EDT)
−
*{{Oppose}} [[User:SpaceBean|<span style="font-family:Coustard;color:pink">SpaceBean</span>]] [[User talk:SpaceBean|<span style="font-family:Coustard;color:purple">(talk)</span>]]    [[File:Rosie PC Villager Icon.png|20px]] 10:42, July 28, 2024 (EDT)[[User:SpaceBean|SpaceBean]] ([[User talk:SpaceBean|talk]])
+
*{{Support}} as well. [[User:Chubby Bub|Chubby Bub]] ([[User talk:Chubby Bub|talk]]) 07:33, October 20, 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]] 06:37, July 29, 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]] 11:24, October 20, 2024 (EDT)
 +
* {{Support}} ~ [[User:Vivian|<span style="font-family:Coustard;color:#6299c1">Vivian</span>]] [[User talk:Vivian|<span style="font-family:Coustard;color:#3a5fb1">(talk)</span>]]    [[File:Vivian Sig Pic.png|20px|link=Special:Contributions/Vivian]] 14:42, October 21, 2024 (EDT)
 +
* {{Support}} -- [[User:ToastyMarshmallow|ToastyMarshmallow]] ([[User talk:ToastyMarshmallow|talk]]) 15:00, October 23, 2024 (EDT)
 +
* {{Support}} {{User:Crosstent/sig}} 11:05, October 24, 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]] 12:38, October 26, 2024 (EDT)
 +
| percent = 100
 +
| result = Passed. Will be implemented by SuperHamster and Jake. '''~[[User:SuperHamster|''<span style="color:#07517C;">Super</span>''<span style="color:#6FA23B;">Hamster</span>]]''' <small>[[User talk:SuperHamster|Talk]] [[Special:Contribs/SuperHamster|Contribs]]</small> 01:29, November 13, 2024 (EST)
 +
}}
  
−
| year        = 2024
 
−
| month      = 7
 
−
| day        = 28
 
−
| hour        = 23
 
−
| minute      = 59
 
−
}}
 
 
{{Navbox Nookipedia}}
 
{{Navbox Nookipedia}}

Latest revision as of 01:29, November 13, 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]

There are no active proposals. For a record of past proposals, visit the Archive.


Proposal: Migrate Nookipedia from CC BY-SA 3.0 to 4.0
Nookipedia is, like many other wikis, licensed under CC BY-SA 3.0. This proposal is to migrate Nookipedia to using version 4.0 of the same license. 4.0 has been available since 2013, and includes some good improvements and common sense changes -- see this article for full details. Improvements include explicitly allowing attribution by linking to a history page (practical for wikis); a 30-day window to correct license violations; and better internationalization.

Wikipedia moved to 4.0 last year (see this blog post), and a growing number of our fellow NIWA wikis have migrated (or plan to) this year (Inkipedia, Pikipedia, etc.).

Regarding implementation: Creative Commons licenses are forward-compatible, which means that if you adapt a CC 3.0 work, you can license it under 4.0. For Nookipedia, this means that all existing content can and always will be considered to be a 3.0 work, but as new edits are made and articles become derivatives of themselves, they will be considered a 4.0 work.

Regarding impact: This change has very little impact to the day-to-day experience of our editors and readers. Most impact would be seen by text re-use between Nookipedia and others. While Creative Commons versions are forward compatible, they are not backwards compatible. This means that 3.0 works can be used in a 4.0 work, but 4.0 works can't be used in a 3.0 work. By moving to 4.0, we will be better aligned with other wikis on 4.0, and can adapt both 3.0 and 4.0 text. Inversely, any wikis on 3.0 looking to re-use Nookipedia's 4.0 text won't be able to, but can also migrate to 4.0 if they wish.

~SuperHamster Talk Contribs 17:48, October 19, 2024 (EDT)

Comments:
Votes:
Result: (100%) Passed. Will be implemented by SuperHamster and Jake. ~SuperHamster Talk Contribs 01:29, November 13, 2024 (EST).

Voting on this proposal has ended. (refresh)

Nookipedia
Main Nookipedia.png
Discussions
Tech & Gadgets
Policy
Help pages
User Levels
Projects
Category
Retrieved from "https://nookipedia.com/w/index.php?title=Nookipedia:Proposals&oldid=1178468"