Difference between revisions of "Team Fortress Wiki talk:Community topics notability guidelines"

From Team Fortress Wiki
Jump to: navigation, search
m
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{discussion close}}
 
== My thoughts, as per request ==
 
== My thoughts, as per request ==
 
These are my thoughts about the current guidelines, I've gone over the sections I've had something to say about. The others I have had no issues with.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 16:39, 25 August 2021 (UTC)
 
These are my thoughts about the current guidelines, I've gone over the sections I've had something to say about. The others I have had no issues with.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 16:39, 25 August 2021 (UTC)
Line 97: Line 98:
  
 
Had some clarifications with Tark to clear up on misunderstandings and discuss more on the proposed guidelines. If custom MvM content can indeed stay in the wiki, then I have no problem with the current version of the proposed guidelines, and there would not be any need to perform the move after all.[[User:Bot Rot|Bot Rot]] ([[User talk:Bot Rot|talk]]) 04:41, 9 September 2023 (UTC)
 
Had some clarifications with Tark to clear up on misunderstandings and discuss more on the proposed guidelines. If custom MvM content can indeed stay in the wiki, then I have no problem with the current version of the proposed guidelines, and there would not be any need to perform the move after all.[[User:Bot Rot|Bot Rot]] ([[User talk:Bot Rot|talk]]) 04:41, 9 September 2023 (UTC)
 +
 +
== Legacy content ==
 +
 +
The memory dims. I might have written this note. If I did, my intention was maybe one of two things:
 +
# Legacy content is any content existing on the Team Fortress Wiki before assessment; an easy concept but maybe too broad -- I don't think the intention was to give any sort of degree of amnesty to any page that got in before we built the wall.  OTOH, maybe it meant that the Policy of no deletion without [specific] discussion should still be applied.
 +
# Legacy content is any content that has been on the Team Fortress Wiki for a Long Time. If I wrote this note, I might have been thinking particularly about the custom map pages made before 2011, mostly transferred from the [[User:Nos|Nos]] [[Team Fortress Wiki|Unofficial Wiki]] in July 2010. It can be seen that the Great Editors of the Past were aware of these custom map pages ''and maintained them''. Why? We may never know. Maybe they were hugely popular or innovative (cf. [[Convoy]]), but that was not written.  (If you could prove that you had managed to survive in pre-Revolutionary Paris for a full year without getting caught, you were granted residency.)
 +
I leave it to the rest of you all to decide.  Maybe this could be removed, maybe it should be promoted to a section.
 +
 +
[[User:Mikado282|<span style="font-family: Arial"><font color="db9c1f">''' M I K A D O 282 '''</font></span><span style="font-family: Arial "><font color="00ff00"> <small>⊙</small>⊙⊙⊙⊙<small>⊙ ⊙⊙  ⊙⊙</small></font></span>]] </small> <!-- --
 +
--> <small> ([[User:Mikado282/Contact Mikado282|Contact Mikado282 (SM)]]) | ([[Special:Contributions/Mikado282|'''''contribs''''']]) ([[User:Mikado282/Help Wanted!|'''''Help Wanted!''''']]) </small> 14:20, 10 September 2023 (UTC)
 +
 +
: I believe it was my inclusion, actuall! Since our goal with these guidelines is to address the sheer amount of content currently being developed by the community, it doesn't really make much sense to go on a deleting spree for content that has been here for over a decade, even if they don't really fit the new guidelines (Hi, [[Mechanical Engineer Update]]!). This is the first time (?) we've tried to make clear rules for the inclusion of such content, so I'd like to at least acknowledge and honor pages that were created many, many years ago and let them remain accessible.
 +
: The note about "legacy content must follow the style guide" is a leeway for us to avoid hosting barebones articles that already don't fit the guidelines. While incompleteness is not a reason for deletion, these pages have been here forever, don't meet the new guidelines, and honestly, probably won't ever be finished. — [[User:Tark|<span style="font-weight:bold;color: #5BC236">Tark</span>]] 14:55, 10 September 2023 (UTC)
 +
 +
:: Policy is not style, exactly. If you find it is not in proper style, the job is to fix it. If you find it is not compliant with policy, the job is to tag it for deletion discussion, or alter it so that it complies, if possible.
 +
:: Yes, it is policy that style be followed, but it is a fixing thing, not a deletion thing.
 +
:: IMO.
 +
:: If someone >wanted< to fix the style of a legacy page, should they feel any constraint from doing so?
 +
:: [[User:Mikado282|<span style="font-family: Arial"><font color="db9c1f">''' M I K A D O 282 '''</font></span><span style="font-family: Arial "><font color="00ff00"> <small>⊙</small>⊙⊙⊙⊙<small>⊙ ⊙⊙  ⊙⊙</small></font></span>]] </small> <!-- --
 +
--> <small> ([[User:Mikado282/Contact Mikado282|Contact Mikado282 (SM)]]) | ([[Special:Contributions/Mikado282|'''''contribs''''']]) ([[User:Mikado282/Help Wanted!|'''''Help Wanted!''''']]) </small> 15:12, 10 September 2023 (UTC)
 +
 +
:::Agreed with Tark here, a lot of old content has been here so long there's not much point in deleting it. {{tl|Cleanup}} could be added if it needs to be cleaned up, but if it's too barebones I think a deletion is fine (but if someone wants to take a shot at improving it I think they should get the chance even post-delete).<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 15:39, 10 September 2023 (UTC)
 +
 +
== Final criticism (hopefully) ==
 +
 +
The only change I'd like to see is to have MvM missions featured in ''at least'' 2 events (preferably from different organisers). Otherwise, every event will have all the missions that they have in each tour eligible, which is an overwhelming amount.<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 22:50, 12 September 2023 (UTC)
 +
 +
: I don't see this happening, ever. Community campaigns usually run contests (which we don't cover) to decide which missions will be featured in the event itself, and, as I understand, each one is a completely new batch of missions.
 +
: Having different groups run the same mission is also quite difficult. There aren't that many groups for this to happen, and naturally, groups have different goals.
 +
: This requirement would essentially be a barrier, as the requirement itself seems quite unrealistic. Not that it can't happen, but that it likely won't. — [[User:Tark|<span style="font-weight:bold;color: #5BC236">Tark</span>]] 23:53, 12 September 2023 (UTC)
 +
 +
::Understandable, the whole thing about having every mission page be ready before moving over to main space should also partially prevent what I mentioned anyway, so it's not a huge loss.<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 11:10, 13 September 2023 (UTC)
 +
 +
::: Weighing in on this, I also agree that the requirement wouldn't happen at all, because missions are almost never re-ran, especially not by both of the two existing groups.
 +
::: But just to clarify, there aren't so much ''contests'' to determine which missions get used anymore, so much as a more-standardized pass/fail judging queue system, where missions are uploaded to a test server by an individual, and then judged by a selected panel. Public open contests were really only a thing in the earliest days of community MVM submissions. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 09:10, 15 September 2023 (UTC)
 +
 +
::::That's pretty much exactly why I wanted it to happen, for a custom mission to be truly notable I feel like it shouldn't just be featured in a single event.<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 09:58, 15 September 2023 (UTC)
 +
 +
::::: Then at the end of the day, none of them will ever be. I've played during every single one of these events, and the only time missions were re-ran (outside of archive servers in the downtime, obviously) was when they explicitly re-ran all of Titanium Tank as a whole operation. The key draw of these events is that they '''are''' entirely new missions each time, like all of Valve's official operations were.
 +
 +
::::: Though it seems as though your key issue is just about an influx of articles, which doesn't really make sense to me. The missions would be part of an event that's already deemed to be notable, as per the guidelines most everybody already agrees to, and some operations do already have full mission tables. Are you not in favor of documenting any of them? Community mission articles have been going on for quite some time, and I don't remember you being too terribly concerned at the time, outside of April Fools missions.  — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 13:20, 15 September 2023 (UTC)
 +
{{discussion close|footer}}

Latest revision as of 22:37, 2 October 2023