Wiktionary:Votes

(Redirected from Wiktionary:V)

Wiktionary > Votes

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-04/User: for admin}}


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


Note: add to this page and WT:C.
{{Wiktionary:Votes/cu-2024-04/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
Apr 29User:TTObot for bot status 8  0  0
May 26Allowing etymology trees on entriesstarts: Apr 27
(=2)[Wiktionary:Table of votes](=8)

User:TTObot for bot status

Nomination: I hereby request the Bot flag for User:TTObot, an account which is used to update the todo list subpages of WT:Todo/Lists.

Schedule:

Discussion:

Support

  1.   Support, of course, but I don't think a vote should be required. Ioaxxere (talk) 23:59, 14 April 2024 (UTC)[reply]
  2.   Support. Benwing2 (talk) 00:09, 15 April 2024 (UTC)[reply]
  3.   Support Vininn126 (talk) 07:21, 15 April 2024 (UTC)[reply]
  4.   Support JeffDoozan (talk) 23:32, 15 April 2024 (UTC)[reply]
  5.   Support Went through the contribs and yep, looks great! This vote may as well be a formality aha. LunaEatsTuna (talk) 00:03, 20 April 2024 (UTC)[reply]
  6.   Support easy decision P. Sovjunk (talk) 09:59, 20 April 2024 (UTC)[reply]
  7.   Support 0DF (talk) 01:59, 22 April 2024 (UTC)[reply]
  8.   Support Binarystep (talk) 09:41, 23 April 2024 (UTC)[reply]

Oppose

Abstain

Decision


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:

    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.

    If anyone has any suggestions, questions, or concerns about the wording, please bring it up on the talk page!

    Schedule:

    Discussion:

    Support

    Oppose

    Abstain

    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:

    Votes intended to be written collaboratively or substantially revised: