Wiktionary:Votes

From Wiktionary, the free dictionary
(Redirected from Wiktionary:Votes/header)
Jump to navigation Jump to search

Wiktionary > Votes

Shortcuts:
WT:VOTE
WT:VOTES
WT:V

Votes formalize and document the consensus-building process and the decisions that the community makes. This page displays the full contents of recent, current and planned votes. Edit Wiktionary:Votes/Active to add new votes to the “active” list and remove old ones. Finished votes are added to Wiktionary:Votes/Timeline, an organized archive of previous votes and their results, sorted by the vote end date.

Policy and help pages, respectively: Wiktionary:Voting policy (including who is eligible to vote) and Help:Creating a vote.

See also Wiktionary:Votes/ for an automatically generated, less organized list of votes.

Before clicking the “Start a new vote!” button below, change “Title of vote” in the field just above the button to a short descriptive title. Once you have created your vote, add it to the list at Wiktionary:Votes/Active.



Note: add to this page and WT:A.
{{Wiktionary:Votes/sy-2024-06/User: for admin}}


Note: add to this page and WT:B.
{{Wiktionary:Votes/bc-2024-06/User: for bureaucrat}}


Note: add to this page and WT:C.
{{Wiktionary:Votes/cu-2024-06/User: for checkuser}}


Other

Admins, please periodically check for orphan votes at Wiktionary:Votes/.

Look for votes and voting templates, including templates for creation of new votes:

Main sections of this page: Current and new votes and Proposed votes. See also /Timeline.

Current and new votes

Planned, running, and recent votes [edit this list]
(see also: timeline, policy)
EndsTitleStatus/Votes
May 26Allowing etymology trees on entriespassed
Jun 30Make No personal attacks an official policy2 18 1
(=2)[Wiktionary:Table of votes](=62)

Allowing etymology trees on entries

Voting on: allowing editors to add etymology trees to entries using the {{etymon}} template. Here is an example etymology tree for English father:

    Etymology tree

    Proto-Indo-European *peh₂-

    ?

    Proto-Indo-European *-tḗr

    ?

    Proto-Indo-European *ph₂tḗr


    Proto-Germanic *fadēr


    Proto-West Germanic *fader


    Old English fæder


    Middle English fader


    English father

    This output above was generated by the wikitext {{etymon|en|id=male parent|title=father|inh|enm>fader>father|tree=1}}. The syntax is quite easy to learn and documented extensively on the template page.

    This has the benefits of making etymology more interesting and accessible to casual readers, as well as increasing the consistency of our content—by design, it is impossible for etymology trees on different entries to contradict one another.

    Specifically, the terms of the vote are:

    • Each language community may decide for itself when and where etymology trees should be added to an entry. This may well be "never".
    • Etymology trees must not be placed anywhere aside from within an Etymology section.
    • If {{etymon}} is used without setting |tree=1, the template produces no output (aside from an anchor to itself). However, these "silent" templates are still important as they can pass on information to other entries. Therefore, they may be used site-wide whenever necessary.
    • The {{etymon}} template has a parameter |text= which can generate some text describing the etymology. This feature is currently experimental and should not be used in mainspace.

    This vote does not:

    • Affect the way our etymologies are currently presented. Etymology trees are in addition to, not a replacement for, textual etymologies.
    • Allow or encourage editors to mass-add etymology trees across the site. As stated above, each language community will decide if or when they are appropriate.
    • Seek to deprecate or change the usage of any existing template.

    Schedule:

    Discussion:

    Support

    1. Support as proposer. Ioaxxere (talk) 02:54, 27 April 2024 (UTC)[reply]
    2. Support. -saph 🍏 14:26, 27 April 2024 (UTC)[reply]
    3. Support Binarystep (talk) 14:44, 27 April 2024 (UTC)[reply]
    4. Support Protegmatic (talk) 16:18, 27 April 2024 (UTC)[reply]
      Support 178.120.64.68 17:24, 27 April 2024 (UTC)[reply]
      IPs are not eligible to vote — SURJECTION / T / C / L / 17:25, 27 April 2024 (UTC)[reply]
      Eh, why not? I'm active here (definitely more than 50 edits, you can see my IP range below) and the only one who uses the IP range 178.120// (at least here on Wiktionary). It's much better if you think about it. As an IP address I can't sockpuppet even if I wanted to. I only get one vote. 178.120.0.0/18 17:33, 27 April 2024 (UTC)
      It's universally understood that IPs are not allowed to vote in official votes. Wikipedia spells it out more clearly (plus their additional requirements, but it's the same here. "Account" means an actual account. If anything, we'd limit it to the IP you were using when you voted, which still does not meet the requirements. I'd highly recommend making an account if you'd like to fully participate in processes like these. AG202 (talk) 22:24, 28 April 2024 (UTC)[reply]
      Oh that's a bummer. I made many, many, contributions with this IP range, for years. I'd thought that would let me participate in votes. I basically see it as my account without a password lol. 178.120.13.161 01:20, 29 April 2024 (UTC)[reply]
    5. Support. Whoop whoop pull up Bitching Betty ⚧️ Averted crashes 20:15, 27 April 2024 (UTC)[reply]
    6. Support - I do think the maintenance issues raised in the Beer Parlor are a real concern, but I think it's definitely worth trying; this is something I've wanted for etymologies for a long time. Combine this with {{dercat}} and {{root}} you can cut down on the unnecessary text within an entry while still providing a full picture. I also think it's "shininess" isn't just a gimmick, I think it really could attract a larger readerbase, including real scholars. Vininn126 (talk) 07:21, 28 April 2024 (UTC)[reply]
    7. Support for the trees! more seriously, this is a great improvement for users as it more clearly shows the relations between lemmas instead of a prose list in my opinion. of course, the latter will never go away but more options are better than none. Juwan (talk) 12:06, 28 April 2024 (UTC)[reply]
    8. Support Allahverdi Verdizade (talk) 15:23, 28 April 2024 (UTC)[reply]
    9. Support. It's useful. Kungming2 (talk) 19:56, 28 April 2024 (UTC)[reply]
    10. Support - I think this will be popular with casual users. Theknightwho (talk) 00:47, 29 April 2024 (UTC)[reply]
    11. Support I'm excited by this initiative. This, that and the other (talk) 04:51, 29 April 2024 (UTC)[reply]
    12. Support Looks like it's ready to go. —Soap— 06:39, 29 April 2024 (UTC)[reply]
    13. Weak support I don't really like the look of it for now, but it seems overall a great addition. Tim Utikal 6:59, 29 April 2024 (UTC)
    14. Support Rakso43243 (talk) 08:03, 29 April 2024 (UTC)[reply]
    15. Support Tashi (talk) 09:47, 29 April 2024 (UTC)[reply]
    16. Support I really like this idea, especially for our casual readers! Visualisation likes this really helps to convey information much easier. LunaEatsTuna (talk) 02:26, 30 April 2024 (UTC)[reply]
    17. Support — Vorziblix (talk · contribs) 19:48, 30 April 2024 (UTC)[reply]
    18. Support Ideally, etymologies would be linked to each other and consistent across all pages. This is a step in the right direction. Megathonic (talk) 19:04, 1 May 2024 (UTC)[reply]
    19. Support Easier to use, it'd be a great addition Rolando 1208 (talk) 07:26, 2 May 2024 (UTC)[reply]
    20. Support --ChemPro (talk) 20:01, 4 May 2024 (UTC)[reply]
    21. Support I don’t need to use the trees actively and they increase Wiktionary’s citation impact on the web, also attracting more manpower; perhaps add more gimmicky branding or watermarks in the background? In the end we will discontinue it anyway for the reasons Victar opposes it, unless new people follow my reasoning. Fay Freak (talk) 00:22, 6 May 2024 (UTC)[reply]
    22. Support I hope to see more infrastructure for this sort of thing in the future. Anarhistička Maca (talk) 03:28, 7 May 2024 (UTC)[reply]
    23. Support — justin(r)leung { (t...) | c=› } 17:18, 8 May 2024 (UTC)[reply]
    24. Support --FocalPoint (talk) 22:42, 11 May 2024 (UTC)[reply]
    25. Support in principle. This is the kind of progressive idea that transcendence of printed formats enables and makes Wiktionary such a great resource, although with Benwing2 I wish this vote hadn't been so rushed (the idea was first brought up in the beer parlour 14 March) and more time had been allowed for discussion about testing, implementation, and other issues. —Caoimhin ceallach (talk) 11:46, 13 May 2024 (UTC)[reply]
    26. Support, any automation would be good and even if this is ugly at the start, could lead to something better Ysrael214 (talk) 18:26, 18 May 2024 (UTC)[reply]
    27. Support. Imetsia (talk (more)) 22:25, 18 May 2024 (UTC)[reply]
    28. Support - has some rough edges, but I am curious and fairly optimistic about where this will lead. — Mnemosientje (t · c) 08:25, 21 May 2024 (UTC)[reply]
      Support Иованъ (talk) 19:09, 21 May 2024 (UTC)[reply]
      Not eligible to vote, per rule 2 of Voting eligibility — SURJECTION / T / C / L / 19:37, 21 May 2024 (UTC)[reply]
    29. Support - nice representation. Jonashtand (talk) 09:47, 22 May 2024 (UTC)[reply]
    30. Support — Etymology trees are wasted on words like th'English father (or, at least, trees as exemplified above are, anyway), since linear descent (with single forking at the root level) is expressed perfectly well by standard text etymologies. Where I see the real benefits of etymology trees is in complex derivations and in the presentation of cognates, for relevant discussions of which see Wiktionary:Beer parlour/2024/April#Automatic cognate generation and Wiktionary:Beer parlour/2024/May#Descendant tree design. I hope that, someday soon, I shall be able to add elucidatory etymology trees to the German Reichsrat and to its cognates. 0DF (talk) 22:21, 26 May 2024 (UTC)[reply]

    Oppose

    1. Strong oppose Word0151 (talk) 14:34, 27 April 2024 (UTC)[reply]
      ...rationale? Whoop whoop pull up Bitching Betty ⚧️ Averted crashes 20:15, 27 April 2024 (UTC)[reply]
    2. Oppose If there is any chance that I would have to look at it. DCDuring (talk) 23:44, 27 April 2024 (UTC)[reply]
    3. Oppose — Fenakhay (حيطي · مساهماتي) 18:54, 28 April 2024 (UTC)[reply]
    4. Strong oppose Any benefit it might afford isn't worth the massive redundancy of work it creates maintaining consistency on entries, especially at the reconstructive level, and should have been made to work with the {{der}} templates, not in isolation from them. This template will breed mistakes and misinformation. --{{victar|talk}} 03:25, 30 April 2024 (UTC)[reply]
      Merging the two templates is absolutely possible, and is something I would support once the design has stabilised. I don’t see it as a reason to oppose, because it would be impractical to merge them from the start. Theknightwho (talk) 10:19, 30 April 2024 (UTC)[reply]
      I do agree maintenance could be an issue - we already have problems with getting headword templates on all lemmas for crying out loud! I think that it would be very easily possible to add inh/der and root function to this at some point however. Vininn126 (talk) 11:05, 30 April 2024 (UTC)[reply]
      And I can't even consider supporting this template until it includes this integration, which would more than likely require it being rebuilt from the ground up. This vote was made prematurely, and needs more development before it can be rolled out. There was no need for this vote yet. --{{victar|talk}} 06:19, 2 May 2024 (UTC)[reply]
      It wouldn't involve rebuilding from the ground up all. Theknightwho (talk) 03:52, 7 May 2024 (UTC)[reply]
    5. Oppose — I don't like the appearance, which strikes me as a poor use of space (though I allow that that is an personal, aesthetic preference. Also, kudos for making it collapsible). I also don't relish the thought of having to add – and reach consensus for the content of – matched templates on all predecessor/descendant terms, especially where some of these relationships might be controversial. Cnilep (talk) 23:25, 1 May 2024 (UTC)[reply]
    6. Weak oppose I can't really articulate this confidently but it looks...plasticky? It seems like a useless gimmick. If someone really needs it, there's already etytree.toolforge.org, don't clutter this site up with infographics.--Simplificationalizer (talk) 13:16, 3 May 2024 (UTC)[reply]
      @Simplificationalizer: I didn't know about that site, but it's clearly far from perfect. The trees for lead (metal) and ice are a complete mess. In both cases the program is evidently confused by homographs. Ioaxxere (talk) 14:16, 3 May 2024 (UTC)[reply]
      This website's last update seems to be one year old. There are edits from August 2023 that don't appear in the trees. Trooper57 (talk) 16:17, 6 May 2024 (UTC)[reply]
    7. Oppose Disturbing. 恨国党非蠢即坏 (talk) 15:16, 11 May 2024 (UTC)[reply]
    8. Oppose until someone demonstrates how an interesting etymology entry (let's say 3 disputed theories, of varying strengths of evidence, with links to researchers or citations for each) will look in tree form. From what I have seen, current proposal is suitable only for the completely trivial and well-settled cases like father. Tetromino (talk) 14:23, 14 May 2024 (UTC)[reply]
      As it says above "Etymology trees are in addition to, not a replacement for, textual etymologies" and "each language community will decide if or when they are appropriate." I don't think a case such as you sketch would be a good candidate for an etymology tree any more than a family tree can give you insight into your geneology if fundamental facts about your ancestry are unknown. —Caoimhin ceallach (talk) 09:42, 15 May 2024 (UTC)[reply]
      I have to echo this. Your complains here don't seem unaddressed by the vote's criteria. Vininn126 (talk) 12:55, 15 May 2024 (UTC)[reply]
      I am afraid that the usage of the tree in a critical mass of articles will lead well-meaning editors into also adding it where it is not appropriate. Tetromino (talk) 19:28, 15 May 2024 (UTC)[reply]
      1) It has the ability to show uncertain connections 2) Like many other templates, one need not apply it literally on every entry within a language, as the proposal allows. Vininn126 (talk) 08:01, 16 May 2024 (UTC)[reply]
      The same complaint applies to literally any etymology template, too. Theknightwho (talk) 14:32, 16 May 2024 (UTC)[reply]
    9. Oppose largely per Victar. If this vote passes, there is too great a risk that people will actually use the template. —Mahāgaja · talk 09:08, 16 May 2024 (UTC)[reply]

    Abstain

    1. Abstain I like the look of it, but it is very screen-dependent. I hope this will be handled in a "reactive" way, by which I mean not just "big or small phone", but also understanding desktop PC users. Good luck. Equinox ◑ 00:37, 13 May 2024 (UTC)[reply]
    2. Abstain Similar reasons as Caoimhin ceallach. I appreciate the changes that have been made, and think that it'd be a helpful feature, but I still feel like there needed to be more time to work out the details. I'm a bit concerned as to how this would look as a whole, especially on pages with several languages. Imagine a page like mi with over 100 trees. Or the fact that this really only works well for Indo-European languages or similarly reconstructed families, and not for languages without established reconstructions or written ancestors. I'm worried that they'll start being out of place and neglected more than they already are, if this change becomes commonplace. However, this isn't enough for me to oppose the idea, but at the same time, I can't support it as is. AG202 (talk) 12:57, 13 May 2024 (UTC)[reply]
      Why does the fact it works mostly with one group (for now) mean it can't be applied to that one group? Vininn126 (talk) 12:56, 15 May 2024 (UTC)[reply]
      Note that I am abstaining, hence I'm not opposing the template being used. I just can't fully support it at this time. AG202 (talk) 15:21, 16 May 2024 (UTC)[reply]

    Decision

    Passes 30–9–2. This, that and the other (talk) 01:27, 27 May 2024 (UTC)[reply]

    Make No personal attacks an official policy

    Voting on: Should Wiktionary:No personal attacks be labeled a policy? It's currently labeled a draft.

    Schedule:

    Discussion:

    Support

    1. Support An essential policy that ought to have been in place long ago. WordyAndNerdy (talk) 21:20, 1 June 2024 (UTC)[reply]
    2. Support Obviously Purplebackpack89 12:55, 2 June 2024 (UTC)[reply]

    Oppose

    1. Oppose I wrote extensive reasoning at the Beer Parlour. I can also afford one of various abridged reasons that alternatively suffice a nay. One is that the vote proposer knows not what a personal attack is. Right after the creation of this vote he escalated towards accusations of harassment and bullying. Maybe he should get treatment for paranoia. Is this a personal attack? I don’t know; this is why I don’t participate in making such bills. The wokery creates a toxic environment for less socially adept people and in consequence of this campaign our two Top 2 editors announced their retire, as Mglovesfun (talk • contribs) did ten years before, due to the same user. Thank you for your concern – Mag. iur. Fay Freak (talk) 12:33, 1 June 2024 (UTC)[reply]
      WF didn't leave and Equinox didn't say why they were leaving. You're making assumptions. And if they did indeed leave because someone complained that they were being nasty to them then who is being thin-skinned here? —Caoimhin ceallach (talk) 00:31, 2 June 2024 (UTC)[reply]
      Humans are regularly insincere about the reasons for what they do, or specifically what they dedicate their life-years to, they are just conglomerates of cognitive biases, making assumptions about themselves, or what determines their personal lives, based on their identities, which even deprives them of maladaption insight; I don’t say “illness insight” inasmuch as even without clinical psychosocial impairment the mind turns the trick of defying reality, because there actually isn’t reason behind this life and we still have to move on somehow. If good things happened it was one’s dexterity in navigating godly laws and if bad things happen it was demonic characters, self-serving bias and fundamental attribution error. Like we know it since Hume under various formulations and degrees of detail.
      You also make the assumption that WF merely trolled, though announcing it repeatedly so the jape is barely operational, and didn’t actually prefer to leave rather than being unable of it due to behavioural addiction; the subtypes of internet use disorder are understudied, at least for social network use disorder and problematic social networking site use, which is similar to the occupation of online-lexicon editing, under the radar in population studies due to its rarety, there are prevalences higher than even any personality disorder. At least, when affording awareness, we can make a kind of Faustian bargain, to combat the Pavlovian reaction of writing out, up to the point of dysfunctionality, hating oneself and others, a new social categorization upon one’s encountering some exciting term.
      Taking advantage of the organizational responsibility diffusion and pseudonymity, we create systems of avoiding to take things personally, rather than forbidding to get personal, which owing to the subjective nature of human understanding is a maxim that cannot be consistently complied. Fay Freak (talk) 05:37, 2 June 2024 (UTC)[reply]
      The above user's pronouncements concerning "wokery" ought to be viewed in light of their history of inserting Daily Stormer quotes into entries. WordyAndNerdy (talk) 03:12, 2 June 2024 (UTC)[reply]
      Ever reflected about political socialization? Since roaming the unregulated internet at youth, I am titillated by political vocabulary, while at the same time I’ve done more against the radicalization from this content than you, who added fuel to the flame by building reactance. This is because, and I make an assumption again, you feel much more strongly about terms and contexts separating groups of people than even Nazis do, who ween conspiracies against their race all the time. Someone evidenced it by banning herself to avoid adding the latest idpol vocabulary tracked on userspace lists, but this was you only according to my memory, which I can’t confirm by currently extant userspace pages and block logs, and I don’t want to reinvoke traumatic memory in you here. Generally though, schoolteachers give, and have to give, their pupils politically biased content to read, of various veneer and degrees of delusion, why? Because the world looks like that, they have only a limited power to create alternative realities; there is such a thing as political education or political literacy, required for readers of texts so general as a newspaper or dictionary. Unfortunately you don’t need to make a great detour to encounter a MAGA, not to speak of their difference to Nazis new and historical. If due to some personal experiences you have flashbacks from identifying them, the recipe is exposure therapy. Fay Freak (talk) 05:37, 2 June 2024 (UTC)[reply]
      @Fay Freak First off, Caoimhin ceallach is correct, blaming me for editors retiring is inaccurate. Also, if editors leave when they're not allowed to harass other editors...that's a GOOD thing.
      Furthermore, why have you gone on this long screed making assumptions about WordyAndNerdy? In opposition to a policy about personal attacks, you've made them. Purplebackpack89 13:04, 2 June 2024 (UTC)[reply]
    2. Nay, for fear of the potential misuse of the proposed draconian law which can lead to a curtailment of free speech. There is no clear definition as to what constitutes a personal attack; in the aforetime I myself got bemired in controversy thanks to my innovative usages of English which little polpotesque wights misconstrued as a scathful attack. Inqilābī 17:30, 1 June 2024 (UTC)[reply]
    3. Oppose per Fay Freak. It seems like the purpose of this vote is to escalate the current Beer Parlour drama rather than to actually get people to treat each other more nicely. Ioaxxere (talk) 18:23, 1 June 2024 (UTC)[reply]
    4. Oppose per all the above. Some people just take everything personally. We shouldn't live in constant fear of criticizing bad editors, just because they might construe our criticism as personal. I don't agree with calling people idiots (for example), but I also don't think it should be a bannable offense, especially if it's directed at someone who is in fact being an idiot. Andrew Sheedy (talk) 22:30, 1 June 2024 (UTC)[reply]
    5. Oppose, seconding all the above. This policy is too susceptible to abuse and would quickly be weaponized. Some users would exploit the policy by labeling even mild criticism as “personal attacks,” creating a chilling effect where individuals are afraid to express their views. The varying thresholds for what different users consider “offensive” only makes the matter worse, because it would inevitably lead to inconsistent and prejudiced enforcement. It could be used to silence dissenting voices or unfairly target editors under the pretense of preventing personal attacks. Imetsia (talk (more)) 23:05, 1 June 2024 (UTC)[reply]
    6. Oppose Ancient and neglected fork of w:Wikipedia:No personal attacks that has not been evaluated or formed by the community, + distrust of the nominator (c.f. Chuck Entz's statement, as well as Ioaxxere's evaluation above). —Fish bowl (talk) 04:13, 2 June 2024 (UTC)[reply]
      Distrust of the nominator isn't a good reason for voting oppose... Purplebackpack89 12:57, 2 June 2024 (UTC)[reply]
    7. Oppose per Fish bowl. So little effort has gone into this proposal that the nominator couldn't even be bothered to display the proposed policy on this page, unlike every other policy vote I've ever seen. Theknightwho (talk) 04:46, 2 June 2024 (UTC)[reply]
      To clarify my view: I do think we need a policy on this, but it needs to have had some actual thought put into it by current members of the community first. Theknightwho (talk) 10:31, 2 June 2024 (UTC)[reply]
    8. Oppose The initiator of this vote seems to be suffering from a massive persecution complex. If this becomes a policy, it'll obviously be abused by people like the OP, interpreting as personal attacks comments in which no personal attack whatsoever is to be found. -- 𝘗𝘶𝘭𝘪𝘮𝘢𝘪𝘺𝘪(𝘵𝘢𝘭𝘬) 08:29, 2 June 2024 (UTC)[reply]
    9. Oppose per all of the above. PUC – 08:42, 2 June 2024 (UTC)[reply]
    10. Oppose. Nothing I could say hasn't been said above. Vininn126 (talk) 10:22, 2 June 2024 (UTC)[reply]
    11. Oppose – The proposer had a specific agenda in mind when proposing this, plus the actual policy they hastily nominated to make official had not been edited since 2012 (!), hence I have to oppose. For the record, I would definitely support an actual well-written proposal for a policy against using personal attacks; I have seen a lot of inexperienced editors get scared off due to the language/tone used by more experienced editors during interactions which is detrimental to the project. IMO we must try to be patient (not overtly!) with newcomers because they could grow up to be dedicated editors, which would thus be a net positive for the project. At least compared to my experience on Wikipedia, Wiktionary is low-key the Wild West sometimes. LunaEatsTuna (talk) 10:37, 2 June 2024 (UTC)[reply]
      I would strongly urge you to reconsider your vote, @LunaEatsTuna. If you want the policy, then take your opinions about me out of it and support it. Purplebackpack89 13:10, 2 June 2024 (UTC)[reply]
      They clearly outlined their issues with the current page being outdated. Vininn126 (talk) 13:13, 2 June 2024 (UTC)[reply]
      Then, by that logic, you should also retract your vote because you DIDN'T clearly outline your reasons... Purplebackpack89 13:18, 2 June 2024 (UTC)[reply]
      Lol, agreeing with those above is clear. Don't twist things. Vininn126 (talk) 13:42, 2 June 2024 (UTC)[reply]
    12. Oppose — Fenakhay (حيطي · مساهماتي) 12:49, 2 June 2024 (UTC)[reply]
    13. Oppose --Vahag (talk) 14:32, 2 June 2024 (UTC)[reply]
    14. Oppose Thadh (talk) 18:53, 2 June 2024 (UTC)[reply]
    15. Oppose The page is not good enough to be policy. The principle, "no personal attacks", has a lot to recommend it, provided enforcement is not too quick on the draw after rare violations and provided accusation of personal attacks is not taken to be sufficient evidence of a personal attack (though it should be taken seriously). I dread a legalistic system. DCDuring (talk) 19:15, 2 June 2024 (UTC)[reply]
    16. Oppose Allahverdi Verdizade (talk) 21:41, 2 June 2024 (UTC)[reply]
    17. Oppose What others above me have said. Megathonic (talk) 01:15, 3 June 2024 (UTC)[reply]
    18. Oppose Case in point: Fumiko Take has a long history of making personal attacks. She was blocked several times for such problematic behaviour (proving policy is unnecessary) and now jumps around IPs to make blocking her impossible (proving policy is toothless). MuDavid 栘𩿠 (talk) 02:06, 3 June 2024 (UTC)[reply]

    Abstain

    1. As several oppose voters have suggested, I suspect (hope) that once the community has time to discuss what kind of policy against personal attacks we should have, what would be reasonable for the policy/guideline to say and how we could mitigate/handle gaming of it (where trolls bait someone into saying something that can be construed as an attack and seek to get them banned, a tried and true tactic on Wikipedia), we can come up with something which will at least be a Guideline, if not suitable for making an 𝕺fficial 𝕻olicy. Since that time wasn't allotted before starting this vote, one editor just rushed a woefully long-unupdated text straight to a vote in what plainly looked like an effort to score points in a dispute with another editor (and only thanks to the quick action of a third editor were some of the most egregiously out-of-date parts of the text noticed and removed before voting started), it quite understandably looks like this particular ill-thought-out vote on this particular outdated version of the text will fail. Since the optics of a vote which is nominally about saying 'personal attacks are bad' failing are ¿grimly amusing?, I want to go ahead and note that if anyone responds to the vote failing by going out and making personal attacks in response (and in general, if anyone is making numerous or egregious personal attacks), they're still liable to be reprimanded or blocked; basic standards exist, lol (I've seen other admins block users for egregiously bad personal attacks, without giving any indication they knew we had a long-unupdated page about the topic, but just based on general standards, as I also have done without realizing we had a page about it). - -sche (discuss) 15:25, 2 June 2024 (UTC)[reply]
    2. Abstain: There should've been more thought and effort put into this, allowing more input from the community. We do need a policy for alleviating conflicts, but not like this. AG202 (talk) 20:40, 2 June 2024 (UTC)[reply]

    Comments

    Should we copy what the current proposal says here? I feel like it would be helpful to show the policy to voters, to help them make up their minds. CitationsFreak (talk) 23:15, 25 May 2024 (UTC)[reply]

    Could just mirror it using a template. There's already a link Purplebackpack89 00:02, 26 May 2024 (UTC)[reply]
    • As Vininn126 pointed out, that is indeed what I did: "For the record, I would definitely support an actual well-written proposal" – the current policy had not been edited since 2012 until the illustrious This, that and the other made an edit mid-discussion in an attempt to improve it. If we are to adopt a policy, it must be a good one that would cover the most important aspects/definitions for 'harassment' so that it cannot be abused (via loopholes or ambiguities) by any editor.. I based my decision solely on my reading of that page, for which I get the impression that it is definitely not good and IMO leaves a lot to be desired. i.e. you essentially proposed an outdated suggestion for a policy written 12-years ago. As I said twice before, we do indeed need such a policy but it must be well-written; and this is a sentiment that seems to be shared by a lot of other voters here, regardless of their opinion on you as an editor. LunaEatsTuna (talk) 16:49, 2 June 2024 (UTC)[reply]
    Then please read my statement again. —Fish bowl (talk) 22:29, 2 June 2024 (UTC)[reply]

    Decision

    Proposed votes

    The following are proposals for new votes, excluding nominations, in cases where the proposer of the vote prefers that the vote is written collaboratively, or where the vote appears to require substantial revision. If you have not created a passing vote yet, it is recommended that you use this section and actively solicit feedback by linking to your proposal in discussion; your vote may have a better chance of passing if it is first reviewed.

    Votes may linger here indefinitely. If changes in policy make a proposal irrelevant, the voting page will be requested for deletion. On the other hand, you do not have to be the creator to initiate one of the votes below. Place any votes with a live start date in the section above at least a few days before that start date arrives.

    Forthcoming votes:

    Wiktionary:Votes/2020-09/Review of Gheg Albanian circumflexes
    Wiktionary:Votes/2022-01/Excluding trivial present participal adjectives
    Wiktionary:Votes/2023-12/Represent the GenAm NURSE and STRUT vowels as schwa
    Wiktionary:Votes/pl-2022-06/Streamlining the approval process of online sources
    Wiktionary:Votes/pl-2022-07/Stubifying alternative forms
    Wiktionary:Votes/pl-2022-11/Should unidiomatic phrases be included if there is consensus for likely utility to readers?

    Votes intended to be written collaboratively or substantially revised:

    Retrieved from "https://en.wiktionary.org/w/index.php?title=Wiktionary:Votes&oldid=77775649"