Template talk:WikiProject Tropical cyclones

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Tropical cyclones (Rated Template-class)
WikiProject iconThis template is within the scope of WikiProject Tropical cyclones, which collaborates on tropical cyclones and related subjects on Wikipedia. To participate, help improve this article or visit the project page for details.
 Template  This template does not require a rating on the project's quality scale.
 

Old pre-wikiproject guidelines[edit]

This is all moved to Wikipedia:WikiProject Tropical cyclones, but I haven't deleted it from here. Jdorje 21:51, 8 January 2006 (UTC)

Structure[edit]

Templates provide consistent layouts for presenting information about tropical cyclones (referred to as hurricanes or typhoons for simplicity) and storm seasons.

  • {{Infobox hurricane}} provides a template for creating an informative table for any hurricane article.
  • {{HurricaneWarning}} provides a top-of-page warning (disclaimer) useful for active hurricanes.
  • {{HurricaneActive}} provides a table to show the current status of an active hurricane (still under development).
  • {{Infobox Hurricane Season}} is a similar template for hurricane season articles.
  • {{hurricane}} may be included at the top of talk pages of hurricane-related articles to let potential editors know about these resources.

Guidelines[edit]

Standards[edit]

Most discussion on standards is currently spread throughout Talk:List of notable tropical cyclones and Talk:2005 Atlantic hurricane season.

Areas that need standardization include

...and more. Most of these have been discussed in the above discussion pages, and a consensus has probably been reached. But because these guidelines are not well publicized, authors keep making the same mistakes.

Things to do[edit]

Spam!!![edit]

This template appears to be spamming Category:Wikipedia editorial validation with hundreds of hurricane talk pages (which have nothing to do with editorial validation. However, after some hacking, I cannot figure out the cause of this bug. Someone, please fix this. linas 08:06, 19 February 2006 (UTC)

I don't know. Note that simply fixing the template will not have an immediate result: pages are not recatorized until they are editied. I can't see what could be causing this though. — jdorje (talk) 13:56, 19 February 2006 (UTC)

Seems to be fixed. NOt sure why. — jdorje (talk) 23:15, 27 March 2006 (UTC)

MetaBanner[edit]

Sitting in the sandbox is a proposed implementation of this banner using {{WPBannerMeta}} the centralised wikiproject banner template which projects are gradually moving over to. The appearance of the tempate won't change a great deal. From this:

{{Hurricane|class=template|importance=NA}}

to this:

{{Hurricane/sandbox|class=template|category=no}}

All the functionality of the current template will be preserved. In addition it should make maintaining the banner and adding new functionality much easier. Any thoughts or concerns about doing this? Martin 16:23, 4 January 2009 (UTC)

Since we usually deploy changes to banners before they are done with WPBannerMeta (and which then are spread to other projects or even to the meta banner), I'd be opposed to switching to the central template. Additionally, the template becomes larger and more visually obtrusive in talk pages. Titoxd(?!? - cool stuff) 17:58, 4 January 2009 (UTC)
The size can be reduced by changing the image size and/or removing the portal link, if that is important. What sort of changes do you mean? I think you'd be surprised - changes can be implemented at BannerMeta within hours if consensus supports them. I'm not sure I follow your main argument: you surely recognise the inefficiency of projects spending time to reinvent the wheel and maintain their own banners when a lot of the work can be done just once? This gives editors more time to write articles (or if they like template programming, to come and help us maintain the central banner!) Martin 18:14, 4 January 2009 (UTC)
I'm not sure I would call it inefficiency. Case in point: BannerMeta did not implement forced B-Class rubrics until MILHIST and WPTC created a standardized method of doing it simply. The template is modified only a few times annually, so all the work that had to be done has been done, negating the benefits of BannerMeta. Titoxd(?!? - cool stuff) 01:54, 5 January 2009 (UTC)
Well you are still using the messagebox classes that have been deprecated for five months. And it doesn't support category optouts. And has large amounts of code duplication. And it doesn't respect DEFAULTSORT sortkeys (admittedly something that is broken in WPBM too, but do you want to bet on which banner is fixed first when bug 16552http://bugzilla.wikimedia.org/show_bug.cgi?id=16552 is done?). And the treatment of categories in general is erratic, with some inclusions having overriding sortkeys and some not.
I'm not trying to demean the work that you or anyone else has put into this template. I'm actually rather impressed to see the new nesting code in place; very few other banners have done that. And I had to work much harder to find flaws in this code than I have in other instances (eg). No one's coding is perfect, I know mine isn't - witness the number of my edits that have the summary "oops" :D. But Msgj is right: with metatemplates work can be done just once, and the wheel needn't be reinvented - instead of inventing the wheel a thousand times, we can invent an aeroplane :D. You're quite right that every major advance in WikiProject banners has been pioneered by individual projects. WPBannerMeta maintains support for such creativity, even encourages it. But why shouldn't other projects be able to instantly and effortlessly take advantage of your enhancements? I guess you're concerned about 'losing control' of your project banner. That's a matter of perspective, I don't see it that way. Rather, I see it as asking you to share your experience and skills with the other WikiProjects, including those not gifted with competent template coders. Happymelon 00:03, 19 January 2009 (UTC)
The question is that undeployed, untested changes should not be deployed to live code that is used by multiple WikiProjects. I have zero interest in deciphering the incredibly-complex parser function soup that is the Meta Banner, and we adopt custom features regardless of whether other projects decide to do so or not, so I see no benefit in this template using the Meta Banner. Titoxd(?!? - cool stuff) 01:08, 21 January 2009 (UTC)

Tagging as meteorology articles[edit]

I've added some text so that anything tagged with this will get categorized as a meteorology article as well. The WP:Meteorology article table wasn't including tropical cyclone articles like it should've been, but this SHOULD hopefully fix it. Inks.LWC (talk) 06:05, 18 July 2011 (UTC)

I reverted this. The Meteorology WikiProject treats all of our articles with N/A importance, and the way the change was implemented, it automatically set WPMET's importance setting to be equal to WPTC's importance assessment. I'll try to get this fixed soon. Titoxd(?!? - cool stuff) 08:34, 18 July 2011 (UTC)

B-class checklist[edit]

Graph of classes

Is the B-class checklist needed in the template? It is something that users very rarely use at all, and users that do tag articles as 'B' class using |class=B forget to fill out the required checklist information, and thus it is considered a C-class article, even though it was tagged as 'B.' As a result of the checklist, B-class article numbers dropped drastically in mid-July of 2008 (see image at right). It's also the reason we have more A-class articles than B-class. If we remove the checklist, we can easily see which articles are close to becoming a potential GAN. TheAustinMan(Talk·Works) 18:39, 8 December 2012 (UTC)

In theory, we should only be sending articles to GAN that pass the B-Class checklist, since the B-Class checklist is just a very weak form of the GA criteria. Titoxd(?!? - cool stuff) 19:47, 10 December 2012 (UTC)

List class[edit]

I noticed that (apparently), this template does not have a list class even though it has a featured list class. Could someone please add a List class option to this template that I can use for timelines? Thanks. Dustin (talk) 17:18, 16 May 2015 (UTC)