Difference between revisions of "Team Fortress Wiki:Community topics notability assessment project"
m (Tark moved page User:Mikado282/Community topics notability assessment project to Team Fortress Wiki:Community topics notability assessment project over a redirect without leaving a redirect) |
m |
||
Line 1: | Line 1: | ||
− | {{ | + | {{TFWiki navbar}} |
− | {{hatnote| | + | {{hatnote|See [[Team Fortress Wiki:Community topics notability guidelines]].}} |
− | |||
− | == Project | + | Under the '''Community topics notability assessment project''', all preexisting custom content are systematically assessed for notability in accordance with the [[Team Fortress Wiki:Community topics notability guidelines]] (Policy). |
+ | |||
+ | == Project objectives == | ||
{| class="wikitable grid" | {| class="wikitable grid" | ||
− | ! class="header" style="background: # | + | ! class="header" style="background: #F3A957;" colspan="2" | Project Objectives |
|- | |- | ||
− | | style="border:1px solid #333;" |Assess notability | + | | style="border:1px solid #333;" | Assess the notability of and decide whether to retain or remove all current community topic pages. |
− | | style="border:1px solid #333;" |{{c| | + | | style="border:1px solid #333;" | {{c|Ongoing}} |
|- | |- | ||
− | | style="border:1px solid #333;" |Complete | + | | style="border:1px solid #333;" | Complete the tagging and documentation of retained community topic pages. |
− | | style="border:1px solid #333;" |{{c| | + | | style="border:1px solid #333;" | {{c|Ongoing}} |
|- | |- | ||
− | | style="border:1px solid #333;" | | + | | style="border:1px solid #333;" | Remove non-notable community topics from the Main Space and adjust Main Space categories as needed, possibly requiring modifications to common templates. |
− | | style="border:1px solid #333;" |{{c| | + | | style="border:1px solid #333;" | {{c|Ongoing}} |
|- | |- | ||
|} | |} | ||
− | + | == Notice board == | |
− | == Notice | ||
{| class="wikitable grid" | {| class="wikitable grid" | ||
− | ! class="header" style="background: # | + | ! class="header" style="background: #F3A957;" colspan="1" | Notice board |
|- | |- | ||
| style="border:1px solid #333;" | As quickly as practical, tag the Community topics pages we broadly agree to keep as "keep" (notable) and delete the ones we broadly agree to delete. With this done:<br/> | | style="border:1px solid #333;" | As quickly as practical, tag the Community topics pages we broadly agree to keep as "keep" (notable) and delete the ones we broadly agree to delete. With this done:<br/> | ||
− | 1) Editors can fix | + | 1) Editors can fix style and quality issues in the retained pages without concerns about "wasted effort". ''The question of notability should no longer delay application of style and qualify.''<br/> |
− | 2) The presence of | + | 2) The presence of highly non-notable pages will no longer serve as an excuse to add more.<br/> |
− | 3) The project | + | 3) The project can then focus on cases where opinions regarding notability require some resolution. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|} | |} | ||
Line 58: | Line 32: | ||
== Assessments == | == Assessments == | ||
{| class="wikitable grid" | {| class="wikitable grid" | ||
− | ! class="header" style="background: # | + | ! class="header" style="background: #F3A957;" colspan="2" | List of assessment records |
|- | |- | ||
| style="border:1px solid #333;" | [[Team Fortress Wiki:Community topics notability assessment project/Community event assessments|Community event assessments]] | | style="border:1px solid #333;" | [[Team Fortress Wiki:Community topics notability assessment project/Community event assessments|Community event assessments]] | ||
− | | style="border:1px solid #333;" | {{c| | + | | style="border:1px solid #333;" | {{c|Ongoing.}} |
|- | |- | ||
| style="border:1px solid #333;" | [[Team Fortress Wiki:Community topics notability assessment project/Custom map assessments|Custom map assessments]] | | style="border:1px solid #333;" | [[Team Fortress Wiki:Community topics notability assessment project/Custom map assessments|Custom map assessments]] | ||
− | | style="border:1px solid #333;" | {{c| | + | | style="border:1px solid #333;" | {{c|Not done}} |
+ | |- | ||
+ | | style="border:1px solid #333;" | [[Team Fortress Wiki:Community topics notability assessment project/Custom content assessments|Custom content assessments]] (mods, gamemodes, "misc." custom content) | ||
+ | | style="border:1px solid #333;" | {{c|Not done}} | ||
|- | |- | ||
|} | |} | ||
== Tags == | == Tags == | ||
− | {{hatnote| | + | {{hatnote|For more information on tags and the assessment process, see [[Team_Fortress_Wiki:Community_topics_notability_guidelines#Tags_and_assessment_process|Tags and assessment process]].}} |
=== Non-Notability (Delete) tag instructions === | === Non-Notability (Delete) tag instructions === | ||
Line 77: | Line 54: | ||
* Remember, deleting ''any'' page for ''any'' reason page ''is a process''; Tag the page, discuss the tag, close the discussion. The result is not required to be deletion. Consensus should determine results, keep, delete, move, improve, etc. | * Remember, deleting ''any'' page for ''any'' reason page ''is a process''; Tag the page, discuss the tag, close the discussion. The result is not required to be deletion. Consensus should determine results, keep, delete, move, improve, etc. | ||
* If you feel the topic does not meet the Notability requirements for inclusion in this wiki, then locate or create the Notability section in the topic's Talk page and state the case, and Delete-tag the page for potential non-notability. | * If you feel the topic does not meet the Notability requirements for inclusion in this wiki, then locate or create the Notability section in the topic's Talk page and state the case, and Delete-tag the page for potential non-notability. | ||
− | * Deletion for non-notability should have that reason stated; e.g., "This Community topic page is nominated for deletion for [[ | + | * Deletion for non-notability should have that reason stated; e.g., "This Community topic page is nominated for deletion for [[Team_Fortress_Wiki:Community_topics_notability_guidelines|lack of notability]]. Please, discuss under the Notability topic for the page." |
== Past discussions == | == Past discussions == | ||
− | The | + | The primary issue revolves around the policy for inclusion/exclusion of Custom maps: |
* 2011-2018: [[Talk:Custom maps]] | * 2011-2018: [[Talk:Custom maps]] | ||
* 2020 late-Summer: [[Team Fortress Wiki talk:Policies/Community content notability guidelines|Talk:Community content notability guidelines]] | * 2020 late-Summer: [[Team Fortress Wiki talk:Policies/Community content notability guidelines|Talk:Community content notability guidelines]] | ||
Line 87: | Line 64: | ||
== Resources == | == Resources == | ||
− | * [[User:Mikado282/Player-Map statistics|Player-Map statistics]] | + | * [[User:Mikado282/Player-Map statistics|Mikado's Player-Map statistics]] |
:: A catalog of resources for measuring popularity of Community maps | :: A catalog of resources for measuring popularity of Community maps | ||
+ | |||
+ | * [[User:Mikado282/Sandbox/Custom map study 2020|Mikado's Custom map study 2020]] | ||
+ | :: An inventory of all maps in the Custom category ''at that time''. There was a surprising amount of low-notability maps in place since around 2011. | ||
* [[Team Fortress Wiki talk:Policies/Community content notability guidelines#Glossary: Official versus Unreleased content, et al|Glossary: Official versus Unreleased content, et al]] | * [[Team Fortress Wiki talk:Policies/Community content notability guidelines#Glossary: Official versus Unreleased content, et al|Glossary: Official versus Unreleased content, et al]] | ||
Line 95: | Line 75: | ||
:: Measurably precise to the Valve community server list; but, it has been suggested that there is a large amount of community servers (hosting community content) that cannot be measured by the Valve community server list. This is to say, rather than overstating the influence of Community content on Community servers, teamwork.tf actually may ''understate'' activity on Community servers. | :: Measurably precise to the Valve community server list; but, it has been suggested that there is a large amount of community servers (hosting community content) that cannot be measured by the Valve community server list. This is to say, rather than overstating the influence of Community content on Community servers, teamwork.tf actually may ''understate'' activity on Community servers. | ||
− | + | == Category tree == | |
− | |||
− | |||
− | == Category | ||
* [[:Category:Community topics]] | * [[:Category:Community topics]] | ||
** [[:Category:Community topics pending assessment]] | ** [[:Category:Community topics pending assessment]] | ||
Line 110: | Line 87: | ||
** [[:Category:Mapping content packs]] | ** [[:Category:Mapping content packs]] | ||
** [[:Category:Mods]] | ** [[:Category:Mods]] | ||
− | |||
− |
Revision as of 22:50, 2 October 2023
|
Under the Community topics notability assessment project, all preexisting custom content are systematically assessed for notability in accordance with the Team Fortress Wiki:Community topics notability guidelines (Policy).
Contents
Project objectives
Project Objectives | |
---|---|
Assess the notability of and decide whether to retain or remove all current community topic pages. | ![]() |
Complete the tagging and documentation of retained community topic pages. | ![]() |
Remove non-notable community topics from the Main Space and adjust Main Space categories as needed, possibly requiring modifications to common templates. | ![]() |
Notice board
Notice board |
---|
As quickly as practical, tag the Community topics pages we broadly agree to keep as "keep" (notable) and delete the ones we broadly agree to delete. With this done: 1) Editors can fix style and quality issues in the retained pages without concerns about "wasted effort". The question of notability should no longer delay application of style and qualify. |
Assessments
List of assessment records | |
---|---|
Community event assessments | ![]() |
Custom map assessments | ![]() |
Custom content assessments (mods, gamemodes, "misc." custom content) | ![]() |
Tags
Non-Notability (Delete) tag instructions
Process for applying notability Delete tags to Community topics:
- Remember, deleting any page for any reason page is a process; Tag the page, discuss the tag, close the discussion. The result is not required to be deletion. Consensus should determine results, keep, delete, move, improve, etc.
- If you feel the topic does not meet the Notability requirements for inclusion in this wiki, then locate or create the Notability section in the topic's Talk page and state the case, and Delete-tag the page for potential non-notability.
- Deletion for non-notability should have that reason stated; e.g., "This Community topic page is nominated for deletion for lack of notability. Please, discuss under the Notability topic for the page."
Past discussions
The primary issue revolves around the policy for inclusion/exclusion of Custom maps:
- 2011-2018: Talk:Custom maps
- 2020 late-Summer: Talk:Community content notability guidelines
- 2019 late-Summer: Talk:Regarding pages on custom maps, competitions, MVM missions, and such
- 2020-2021: Team Fortress Wiki talk:Policies/Community content notability guidelines
Resources
- A catalog of resources for measuring popularity of Community maps
- An inventory of all maps in the Custom category at that time. There was a surprising amount of low-notability maps in place since around 2011.
- Measurably precise to the Valve community server list; but, it has been suggested that there is a large amount of community servers (hosting community content) that cannot be measured by the Valve community server list. This is to say, rather than overstating the influence of Community content on Community servers, teamwork.tf actually may understate activity on Community servers.