{{subst:WikiProject template sharing/prototype}}

Welcome to the WikiProject template sharing WikiProject, a collaboration area and group of editors dedicated to improvement and dissemination of Wikipedia's large rich collection of productivity enhancing tools and utility templates to our fellow editors and sister projects.

The projects aim is simple:

1. Enhance productivity of wiki-editors whatever they call their home project by organizing and providing the same basic time saving template tools to do tasks.
2. Provide commonly available stable template tools maintained in similar or equivalent categories on the participating Wikpedia:Wikimedia Sister Projects.
3. Using templates developed on Meta-wiki and Wikipedia, the two sister's initially with "seed stocks of utility templates" for administrative, discussion, documentation, interwiki connection and analysis tools or utility templates and providing them to other sister sites where they might find use and save someone time is the prime thrust of this effort.

1. Mount an education effort explaining and demonstrating how macros are productivity multipliers and not magic boxes, as some lay people seem to think. Macro's have existed since at least the late sixties and much of today's software technology would be lost without such in its various computer languages.
   1. Meta:Help:Template almost makes that case in its first few lines, but does not discuss the human cost in time and lost and wasted opportunity costs of doing things in harder ways than need be. Demo: Is it easier to type: {{Wd|noun}} or [[Wikt:noun|noun]]?. Can one more easily look at Xfd decisions by having a simple link to Page, Links, Hist, etcetera, or must one be required to navigate to each page, then a second link then backspace, then the other, then eventually back to register a vote? Much more convenient and courteous of each others time to have all that one link away, so one has only to backspace one link to the business and discussion at hand when making an informed decision.
        
2. Survey, re-categorize as needed, and hammer good documentation together for each tool or utility template using the Meta/Wikipedia doc page pattern technique to minimize server loading and provide a clear set of usage and instruction aimed at the novice and lay person.
   1. This means de-fang Computer Jargon and assumptions that the viewer knows anything at all about templates.
   2. This means provide a clear purpose statement of what the template is used for, how it is used, the named and numbered parameters it will take or tolerate, and a few good examples.
   3. In general, templates should be grouped by general function, and where possible write usage 'see also lists' so that an interwiki capable template is used to provide the link. (Note all sisters will want any or many tools templates, however, when they do import one, the usage should not show redlinks to others in a see also list. This means the various interwiki versions based on Ltsany and Tlx, or Tlw/Tlm should be written in versus Lts, and Tl.
   4. The initial primary mission, is therefore, good documentation, followed by making such portable documentation.
        
3. Copy template tools to sister projects, with a firm understanding that each sister has its own unique and sometimes quirky culture. In general, an announcement on the local Village pump using {{Template list}} that documentation has been updated and prepared for the tools templates list of that week should draw some interested parties.
   1. Just dropping a new template onto a sister is contra-indicated. Preferably, this project can attract some editors interested in saving their personal time to import the tools into their home wiki's, and use them as well as talk about them.
   2. Writing good documentation is again key to having a template used. If people can envision how it will help their daily grind, they'll use it.
   3. Be prepared to overcome certain types of objections. Some sites have obsolescent tagging like 'esoteric' and worry about Parserfunctions, both of which are likely about to disappear as part of the survey and recategorization undertaken on wikipedia during early February 2007.
4. Aid interlingual porting of templates as much as possible. The big tool for that will be {{ltsany}} with its ability to select both sister projects by type and by language.
5. Last but not least, this project will strive to put together a utility template handbook.
   1. An early approach is to excerpt the /doc page to about 12-15 lines into another subpage. The handbook sucks in those small pages to assemble the handbook in alphabetical order.
   2. An alternative approach would be to 'box display' template help similar to those displayed via Wikipedia:Wikipedia template and its sub-pages.
   3. A similar modular approach may lead to a handbook with several pages of templates by group and type.

Template:Interwikitmp-grp

Scope

• ?

1. As much as possible templates on all sisters, and categories used on all sister projects should be kept the same, in particular for templates and their '/doc' documentation pages.
   1. Any rationale for deviating from that standard should be discussed only after seeking advice. Many 'hinky' issues with templates may in fact be script issues with a sister projects Mediawiki:Common.css page. (One tell tale touchstone-- square boxes or weird symbols.)
   2. A careful survey of various category naming practices across the sisters projects was made, and the set of sub-categories used or defined was done with great care and an eye on commonly recurring names.
        
   3. The prototype testing effort conducted in late August and early September of 2006 identified both naming collisions, and common categorizations and established several methods of working needed categorizations into templates or into a sister projects category system inobtrusively so as to interfere locally as little as possible.
        
   4. 'Name Case Variations' was the method chosen to handle most naming collisions with a template on a sister project that has a different behavior. That is the common name was generally converted to all uppercase ('cat' by default is 'Cat' save for on Wiktionary, Name case equivalent is 'CAT' — giving visiting editors a commonly named and behaving tool. This causes some redundant templates, but it is a small handful.
        In most cases, the redundancy is made in name only--the name case equivalent is created as a redirect template, not a full coded stand-alone page, and this is the preferred method.
        This method has proven satisfactory for most system templates except for on Wiktionary, where both uppercase anything and redirects of any sort are aggressively discouraged.
        
2. An 'enhanced intensity' informal survey of templates was begun by several editors as February arrived in 2007, part of this project will be to lend aid to this effort, upgrade documentation on the sourcing sister project, and discuss on WT:TSP whether such templates should be recommended to sister projects as potentially useful tools.
     
3. Any template that has been around Meta or Wikipedia for a long while is likely suffering from the former practice of "hiding" usage information on template talk pages and the fact that this was not infrequently written at an inappropriately high technical level, quite frequently above the heads of a lay editor without template knowledge.
     
   1. Convert usage of candidate templates into Wikipedia:Template doc page pattern compliant documentation pages, unless it is a tool which is rarely used.
      These should successively be:
   2. ...edited to a level comprehensible to a newcomer editor without much computing knowledge,
   3. ...formatted and configured to limit editing so that a copy on any sister project's pages will display identically.
   4. In particular, some sisters do not have an abbreviation such as 'w:', 'b:', 'q:' and the like, most notably the commons. Longform names do not work within a sister project's pages in most cases. For these, macro templates must be used, which tests the magic word {{SITENAME}} and using an if-then-else test branching to a local version (no prefix) or common form (off sister).
        
4. When a category (generally one which includes a sitename 'Wikipedia templates', 'Wikiquote templates' is utilized within a template, or one of the common categories interwiki connected using this project, appropriate #ifeq:-then-else tests of SITENAME should be used to step around the category. In some cases, a switch maybe a better choice.
     
5. Templates should not be dropped willy-nilly on a sister project, no matter how good. The different sister projects have their own unique society and cultures. (some garbled sentences follow) In general, the template should be fully prepared interwiki message compatibility and proper auto-categorization within the categories maintained by this project. A notification of suggested importation, or for such sister's as choose to implement a 30 day trial and speedy-delete criteria, a delivery then such a post should be made on the communities general discussion page (Many use Village Pump, some few have different names making it hard to not check their Help pages to know where to go.)
     
6. This project hopes to recruit and maintain three to six ombudsmen to monitor key talk discussions and advocate the WikiProject's position on each sister, patrolling in turn and turn about or on some regular schedule. These parties, steeped in the guidelines of both projects, hopefully will include some admin level volunteers from the given sister acting in an advisory capacity and smoothing any disjoint practices.

Mission

(Quick and dirty) proto-project description currently available.

Seems sensible to add

There was a significant change to WP:DPP this weekend, relative to templates tagged with {{interwikitmp-grp}}, as I'm fairly sure editing the latter on the last two occasions locked the data-base for a time... a geometric propagation effect of so many tools templates in wide use being tagged and exported to our under manned sister projects.
  For those unfamiliar, this is the best online description of the proto-project currently available. Now that it's moving out of experimentation into minimal implementation, I'll be innaugerating [(just now) stubbed in] a project page (interim, this is properly a Meta project)... and this is and would be an assist in freeing up time for that. The specialist normally editing many sisters are both undermanned and have not our wide deep pool of template coders, and viewing some of their VP posts (How can I do this... stuff) is eye-opening, as are the responses.
  If some have a moment to assist in adding the 'doc page pattern' technique to such tools templates, especially the protected templates, this will be a big help in inoculating (preventing) the system from such server loads. The {{interwiki doc page pattern}} subst'd gives a boilerplate on the /doc page, so only a little cutting and pasting is needed to achieve a permanent fix.
  Two caveats:

1. The syntax <noinclude>{{/doc}}</noinclude> does not work on most other sister projects, so please use the longer equivalent <noinclude>{{{{PAGENAME}}/doc}}</noinclude> or the verbatimboilerplate if aiding this small [List cat: Interwiki utility templates] tasking bubble.
2. The next stage evolution uses parameters and will delete the interwikitmp-grpNN suffixed pages, so if you convert those to {{interwikitmp-grp}}, per suffixed 'NN' tag now inplace, will be a big assist. And I can get on with making the write-up for the trial project into a concrete project from Meta. I'm a little time tight right now and all help much appreciated. Thanks, regards FrankB 17:29, 4 February 2007 (UTC)[reply]

Please feel free to add yourself here, and to indicate any areas of particular interest.

    Name (talk · contribs) (everything to know about WikiProject template sharing)

1. Fabartus (talk · contribs)
2. Ezhiki (talk · contribs) (will help when I can)
3. imz (talk · contribs)
4. Willscrlt (talk · contribs) (limited availability; already do this sort of stuff on meta, commons, en.books, de.wiki, es.wiki, fr.wiki, it.wiki, pt.wiki, etc.)
5.  Buaidh  — I've created over 2700 templates.

Please feel free to list your new WikiProject template sharing-related template suggestions for export here (newer porposals at the top, please). Any new templates that have an interesting or unusual fact in them should be suggested for the Did you know? box on the Main Page.

• …your new goodies suggestion here…
• {{User sister projects}} is currently only on Wikipedia, but would be good to have everywhere. —Sam Wilson (Australia) (talk) 22:27, 29 May 2008 (UTC)[reply]
• Various cat see also type templates: catlst, Cat see also W2, Cat see also W2
• W:Template:Template list -- when finalized, template will allow cross-wiki checking of templates for updating and exporting by use of 'SITE' parameter to change project contexts.

Collaboration of the week

Assessment

1. Template:Interwikitmp-grp ( talk links history)
2. Template:Interwikitmp-grp/doc ( talk links history)
3. Template:Interwikitmp-grpNN usage ( talk links history)

• The exact number of kernel templates is in the process of being determined by the prototype interaction and needs on the various sister projects, as usage material is upgraded and interwikified (made portable so will display exactly the same on all sister projects). This is in part complicated by templates of short name lengths being used on different sister projects for differing uses. Unfortunately, many of these are the most commonly used tool templates, like {{tl}}.
    Example: {{cat}} has at least three major variants— two that list the category as a link, with and without the word 'category' as part of the link, and a third where it is actually used to categorize a page. A template {{w}} is used on many sisters as a macro template to make the link [[W:pagename | pipe-tricked name]] . 'W' however does very different things on several sister's, as does the two letter '{{Wc}}', a natural mnemonic for Wikimedia Commons|Wikimedia Commons. Hence work around macros 'W2' and 'W2c' were found to be unencumbered, and are used extensively in category pages linked between sister projects and documentation of templates expected to be shared respectively.

• Category:WikiProject template sharing -- List/tracking category for elements of the system, including other categories used, borrowed and shared.
• Category:Interwiki utility templates
• Category:Redirects from alternative spellings -- implemented on sisters for redirects of NameCase Equivalents.
• W:Category:Interwiki template sharing categories -- Work around common node category to tie into sister projects category schema, with as little disruption as possible to their way of doing administrative business. Connects to all projects used by the common categorization of templates by type.
• W:Category:Interwiki templates on all sisterprojects -- tracking category of the minimal templates needed to make interwiki portable annotation and usage notes.
     4. Category: Interwiki templates on all sisterprojects  ??? Found in IWTG3 on commons.

0. Category:WikiProject Interwiki equalization -- sourced in {{I5}} -- (?) implementation pending more study.

Use parameter "|V=#|" to add the category to a template in '/doc' page

1. Category:Internal link templates 2. Category:Interwiki link templates 3. Category:Miscellaneous templates or using parameter "|cat=bare category name
   sub-categories Category:Typing-aid templates or Category:Wikipedia uncategorized templates. 4. '|V=4' combines 1+3 above: Miscellaneous and makes internal links. Example: {{cat see also}} 5. Category:graphics and table effects templates 6.

7. category: Wikipedia special effects templates {{I0}Options:
A) --> rename? ---> Special effects templates
B) or (tentative keep and such -- allows each sister their own 'SITENAME' category, (seems silly)
C) or {{category redirect}} and shift gradual?.
Some {{interwikitmp-grp}} tagged templates apply before sorting is even well begun: {{NestTextColors}}, {{TextColors}} aka redirected 'Co', {{tt}}, etc. A better survey of templates and upgrading of template usage, while incorporating such into a Template Utility list/guide page will make this clear in time.

8. Category:WikiProject Interwiki equalization -- (I've a better name somewhere squirreled away) this is a related project, a semi-parent, to link commons categories to English language sister projects using a simple set of templates.
A) Related hope is make a small system software change to dynamically insert interwiki's in place by the language of the user's browser. Brion Vibber needs queried again, or goto mediawiki?
B) Template: Interwikicat-grp, which needs major overhaul, and a set of individual XXXXXcat templates in place, especially connect Wikipedia pages to the commons categories. (Progress and effects seen in below two categories.)

See for experimental scope see:

1. Category:Wikipedia categories matching with Wikimedia Commons categories and
2. Category:Wikipedia categories equalized with Wikimedia Commons categories

Project categories --->

9. Category:Utility templates used in categories and

Category:Templates used in categories -- The later is parent, the former lists general purpose templates used on category page documentation.

9. Category:Interwikitmp-grp ineligible -- List templates with functional differences where a naming collision occurs on another sister project.

10. MSIE font fix templates

Sister projects may have a local page

Since staffing is from en.wikipedia for English projects, the below are direct links to source/master pages there.

1. {{interwikitmp-grp}} tagging utility, Master copy: W:template:interwikitmp-grp
        Questions, concerns, talk, requests W:Wikipedia:WikiProject template sharing
     
2. {{interwikitmp-grp/doc }} auto-categorization tagging guideline
     
3. interwikitmp-grpNN usage }} notes utility
     
4. http://en.wikipedia.org/wiki/Wikipedia:Template_doc_page_pattern
     
5. http://en.wikipedia.org/wiki/Wikipedia:Template_doc_page_pattern/doc
     

• Sister projects
• Child of Wikipedia:WikiProject Templates (WP:WPT) and probably a similar project on Meta