Line 37: | Line 37: | ||
I am Interested if editors think these steps would be an improvement, or if there are better suggestions. Thanks.—[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 06:31, 24 October 2015 (UTC) |
I am Interested if editors think these steps would be an improvement, or if there are better suggestions. Thanks.—[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 06:31, 24 October 2015 (UTC) |
||
:[[User:Bagumba|Bagumba]], if you want to this module in the infobox, you will need a way to keep the name of the color in sync with the color (e.g., color1 and color1hex). this is certainly possible by extending this module to include color names. a better option would be to just have {{tl|Infobox NCAA football school}} use this module directly, extracting the team name from the {{para|TeamName}} parameter. [[User:Frietjes|Frietjes]] ([[User talk:Frietjes|talk]]) 14:11, 24 October 2015 (UTC) |
Revision as of 14:11, 24 October 2015
This module does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Secondary colors
For purposes of legibility it seems a good a rule of thumb to if at all possible make the second color white, or, if that be untenable as a school color, and the first is a shade of Princeton orange or lighter, then black. Cake (talk) 09:09, 25 March 2015 (UTC)
Request for template protection
I was asked to consider adding template protection to this page, with the arguments summarized as follows:
- Some edit wars have occurred on this page
- A sockpuppet has previously edited this page.
- The colors of hundreds of schools could be compromised by this one page, impacting a lot of pages (exactly number not readily available as this page is generically included in templates also used by pro players)
Relevant points from Wikipedia:Protection policy are:
- WP:TEMP-P: Template protection "should only be used on templates whose risk factor would have otherwise warranted full protection."
- Full protection would not be warranted here for content disputes. Full protection would normally be temporary in this case, and not indefinite. Moreover, WP:FULL advises: "Isolated incidents of edit warring, and persistent edit warring by particular users, may be better addressed by blocking, so as not to prevent normal editing of the page by others."
- If socking were a concern, semi-protection would be used, not full.
- Full protection is not typically used to prevent vandalism. Per WP:PREEMPTIVE: "Pre-emptive full protection of articles is contrary to the open nature of Wikipedia ... Persistent vandalism, or the possibility of future vandalism for highly trafficked articles, rarely provides a basis for full-protection. Semi-protection is used for articles, such as Jesus, that have a pattern of heavy sustained vandalism."
- TEMP-P also allows for usage on high-risk templates or modules. Indications are that for this data page, the worst that is expected to happen is that the wrong colors might appear, and the text in the colored borders of affected infoboxes could be made unreadable by a rogue editor.[1] This is not at the risk level of making 1000s of pages entirely unreadable, or placing an undue load on servers.
My decision for the current request is for no template protection, based on policy cited. Incorrect colors seem to be the most likely risk of not providing template protection, but this seems akin to the risk inherent for any content on Wikipedia that might be temporarily incorrect until it is detected and addressed.
To mitigate edit wars, I would suggest improving the verifiability of the colors used. One option might be to annotate the page with comments—perhaps of urls supporting the choicef colors—in the Lua code. Comments are denoted by double dashes, e.g. --, such as in this sandbox edit. If an individual editor is still problematic despite continued dispute resolution attempts, a topic ban is also an option. Finally, temporary full protection remains an alternative if needed to encourage discussion.—Bagumba (talk) 02:27, 19 October 2015 (UTC)
Improve redundancy and verifiability
@Corkythehornetfan, MisterCake, Frietjes, ArmandoBecker, Joeykai, UCO2009bluejay, and Charlesaaronthompson: You've been directly pinged as the editors with > 10 edits of this page.[2] I'll also leave notification at WT:CBBALL and WP:CFB, projects that have infoboxes that use this module.
There seems to be occasional disputes over individual color entries in the table. To minimize these disagreements, I would suggest for long-term verifiabiity that inline comments be used when adding or modifying a line. This can be done in Lua by using double dashes, e.g. --, such as in this sandbox edit. For example, the comment can be the URL of an online reference, and/or text about how the colors were derived. In the past, this has sometimes been provided in an edit summary, but it's not manageable to trace through edit summaries for historical changes.
Additionally, the college colors on this page seem to be duplicated in other infoboxes. For example, the infobox of Ohio State Buckeyes football has the school colors displayed, except the values are not taken from this module. To centralize the colors and remove the overhead of multiple updates, I would suggest that {{CollegePrimaryHex}} and {{CollegeSecondaryHex}} be used to avoid colors not being consistent across pages.
I am Interested if editors think these steps would be an improvement, or if there are better suggestions. Thanks.—Bagumba (talk) 06:31, 24 October 2015 (UTC)
- Bagumba, if you want to this module in the infobox, you will need a way to keep the name of the color in sync with the color (e.g., color1 and color1hex). this is certainly possible by extending this module to include color names. a better option would be to just have {{Infobox NCAA football school}} use this module directly, extracting the team name from the
|TeamName=
parameter. Frietjes (talk) 14:11, 24 October 2015 (UTC)