Discussion: What criteria should determine inclusion into the warn menu? #533
Comments
This was referenced Mar 4, 2019
Amorymeltzer
added a commit
to Amorymeltzer/twinkle
that referenced
this issue
Apr 24, 2019
Setting it up this way means there is even more of a difference between the scaled levels (level2, level4im, etc.) and singlenotice/singlewarning/custom, but doing so should make it very straightforward to remove or add templates (pursuant to any discussion in wikimedia-gadgets#533). The only change to the enduser is that this will now generate a submenu category for every grouping, even if there are no templates in that group at that level. At the moment, this is only the `4im` level for the "Removal of deletion tags" category. I'm not sure this is a bad thing. One header was mistmatched ('other editors' versus 'other users'), resolves that.
Amorymeltzer
added a commit
to Amorymeltzer/twinkle
that referenced
this issue
May 10, 2019
Setting it up this way means there is even more of a difference between the scaled levels (level2, level4im, etc.) and singlenotice/singlewarning/custom, but doing so should make it very straightforward to remove or add templates (pursuant to any discussion in wikimedia-gadgets#533). The only change to the enduser is that this will now generate a submenu category for every grouping, even if there are no templates in that group at that level. At the moment, this is only the `4im` level for the "Removal of deletion tags" category. I'm not sure this is a bad thing. One header was mistmatched ('other editors' versus 'other users'), resolves that.
Amorymeltzer
added a commit
to Amorymeltzer/twinkle
that referenced
this issue
May 15, 2019
Setting it up this way means there is even more of a difference between the scaled levels (level2, level4im, etc.) and singlenotice/singlewarning/custom, but doing so should make it very straightforward to remove or add templates (pursuant to any discussion in wikimedia-gadgets#533). The only change to the enduser is that this will now generate a submenu category for every grouping, even if there are no templates in that group at that level. At the moment, this is only the `4im` level for the "Removal of deletion tags" category. I'm not sure this is a bad thing. One header was mistmatched ('other editors' versus 'other users'), resolves that.
Amorymeltzer
added a commit
that referenced
this issue
May 15, 2019
…in (#592) warn: Reorganize messages object, should make it more clear to maintain Setting it up this way means there is even more of a difference between the scaled levels (level2, level4im, etc.) and singlenotice/singlewarning/custom, but doing so should make it very straightforward to remove or add templates (pursuant to any discussion in #533). The only change to the enduser is that this will now generate a submenu category for every grouping, even if there are no templates in that group at that level. At the moment, this is only the `4im` level for the "Removal of deletion tags" category. I'm not sure this is a bad thing. One header was mistmatched ('other editors' versus 'other users'), resolves that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Additions to the
twinklewarnmenu are commonly suggested, and right now our inclusion criteria are a bit ad hoc, so it'd be good to nail those done, especially for #477. As @atlight nicely summarized, there are two major points we should consider as guiding concerns:A swollen list makes it difficult for anyone, in particular newish users, to find what they want (#517 may help). We're kind of begging the question here, given that most warnings are likely given by Twinkle and Huggle, but regardless we do not want to overwhelm or aggravate antivandalism efforts.
#412 is probably where the most consolidated discussion has taken place, but as a PR has gotten unwieldy and isn't a good starting place, so I'm opening this to supersede and centralize discussion of the merits. The last major pruning was done in #302 by @MusikAnimal.
The text was updated successfully, but these errors were encountered: