View source for Wazeopedia View history

{{Construction|new=yes|draft=no|contacttype=forum|open=no|contact=http://www.waze.com/forum/viewtopic.php?t=146759}}
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}
<!--
 #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
 ####    This page has been curated   ####
 ####    to be included in the new    ####
 ####     Wazeopedia - GLOBAL Wiki.   ####
 ####    Please do not make any       ####
 ####    edits on this page without   ####
 ####    PRIOR CONSENSUS in the Wiki  ####
 ####    Updates and Discussions      ####
 ####    forum thread for this page.  ####
 ####    If a specific forum thread   ####
 ####    for this page doesn't exist  ####
 ####    please start one.            ####
 ####        www.waze.com/forum/      ####
 ####        viewforum.php?f=276      ####
 #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->

'''Wazeopedia''' is the new name for the Waze community wiki, and also the project name for converting the existing wiki into the new framework. First [http://www.waze.com/forum/viewtopic.php?f=276&t=123270 announced in Jan, 2015], the project is being spearheaded by {{username|wonderlerm}} a member of Waze staff. Wazeopedia will contain a unique individual wiki instance for each local community, as well as another instance to host global content. Content will be able to shared across the wikis, maintaining the collaboration while allowing the reader an insulated experience.


== Framework ==

The Wazeopedia will be separated into a group of sister wikis. These individual wikis will function on their own, yet also be able to share resources with each other.

The individual wikis inside Wazeopedia will be structured as follows:
* A [[#Global wiki|'''Global wiki''']] containing content that is valid everywhere, and not subject to local variation. This includes interface guides, global rules, and best practices, etc.
** A '''Commons wiki''' will host a repository of images and other resources which may be easily used by any of the other wikis. This will prevent a lot of duplication of the same resources for each wiki.
* A separate [[#Local wiki|'''Local wiki''']] for each country / local community which wishes to have its own wiki, representing their unique guidance.

[[File:Wazeopedia_structure.PNG|650px|thumb|center]]

== Global wiki ==

{{Mbox|type=critical|text={{Red|'''DO NOT EDIT''' ANY GLOBAL PAGE WITHOUT '''PRIOR GLOBAL CONSENSUS'''.}} Please make sure you follow the [[#Protocol for editing global pages|protocol for editing global pages]], as well as the [[Waze_etiquette#Wiki_changes|Waze wiki editing etiquette]]}}

[[File:Wazeopedia.png|right]]The Wazeopedia Global wiki will be built of carefully selected content that is useful for all the local Waze editing communities around the world. Each local community is free to include global content into its own pages. This can be done in the original English, or by creating a modified, translated, or interpreted derivative.

Since the Global wiki pages may be reused by any community, it is imperative that they maintain a Global perspective, and reflect global consensus. Therefore any edits to a Global wiki page must follow the [[#Protocol for editing global pages|protocol for editing global pages]], as well as the [[Waze_etiquette#Wiki_changes|Waze wiki editing etiquette]].

All content in the Wazopedia Global wiki will be verified and maintained for accuracy by a combined group of Wiki Masters and Champs, with assistance from staff. The Champs will also ensure the content is relevant to the global community and not biased to only certain local communities.


=== Nominated pages for global wiki ===

{{As of|2015|6}} the Wazeopedia Global wiki site is not yet available. However, the 
[http<!--The 'S' is purposefully included in httpS for this URL since it targets a secure page you must be logged in to view-->s://www.waze.com/forum/memberlist.php?mode=group&g=145 Wiki Masters team] which has been tasked with building the new Wazeopedia has examined the pages in the existing Waze wiki, and nominated a comprehensive list of pages which were already global in nature to be included in the Wazeopedia Global wiki.

Each page which has been nominated for the Global wiki will have the {{tl|GlobalMark}} template placed at the top to clearly identify it to the reader as a Global nominee.

While a great deal of effort has been extended to build an accurate inventory of existing wiki pages which have global relevance, mistakes are inevitable. The people parsing the pages to determine if they are globally relevant, are usually not the authors of the page, and may not even be familiar with discussions about the page. It is entirely possibly for a page which was only ever intended for a local community audience to be nominated for the global wiki, or for a page intended for a global audience to have been missed and not be nominated. 

To provide feedback and discuss a page which either; you think should have been nominated for the Global wiki, or a page which has been nominated for the Global wiki process that applies to existing pages, pease visit [//www.waze.com/forum/viewtopic.php?t=146145 this forum thread]. You can ask questions there, and alert the global wiki team to any concerns you have.


==== Inventory list of global nominees ==== 

The complete list of current pages nominated for global Wazeopedia can be viewed either on the list for [[: Category:Wazeopedia Global Page]], or in this [http://docs.google.com/spreadsheets/d/1bwS_VWdZj116-urzl7bJl7woU4SEUOzmvpPLbF5XuGA Google Sheet].

=== Page style and location ===


==== Choosing a namespace ====

{{NeedInfo|&nbsp;
*draft/revise in user
*variable or not intended for search results in template
*main is only for finalized, which can be consumed individually, and would make sense in search
*Wazeopedia for wiki admin}}


==== Nuggets ====

Pages in the Global wiki are designed to be reused in whole or in part by the local wikis. Some local communities may wish to use only portions of a page, and fill in the rest with local guidance, or interpretation. Some portions of a page may not be relevant to certain local communities. To enable other pages, and Local wikis to easily transclude, or translate only selected portions of a page, Global wiki pages are broken down into smaller individual pieces. We refer to these smaller pieces of knowledge as '''nuggets'''.


When viewing the global page a user will see a seamless flow of content, with all the Nuggets displayed together. When building a local wiki page, the local community may choose to utilize some of the global content. In such a case the local editor could string together some of the global Nuggets with some locally generated content, and display it as one cohesive page.

This method also allows the same small piece to be displayed on multiple pages, while only truly existing in one source location. This makes maintaining the content accuracy easier, since when it changes, it only has to be updated in one place.


Using Nuggets for the content will also help efforts for those who are translating the content into other languages for the local wikis. When the global page is updated, the Local Wiki Masters won't have to study the entire page to update the translation. They will only need to update the translation of that individual nugget. Additionally with the introduction of new tools to track when a translation is outdated, the system will be able to automatically indicate to a reader which section of page (based on which nugget) is now out of date.


===== Process for creating nuggets =====

Each nugget should be a distinct small piece of knowledge content. It should be a whole thought, able to be read alone. It doesn't need to explain an entire topic but should be one full distinct aspect of the topic. A Nugget might be the contents of one section of a wiki page as a good rule of thumb. You may even split one section into a few Nuggets depending on the content.


Each Nugget should be saved as a separate subpage to the parent page it will be primarily displayed on. Each Nugget subpage should be named with a descriptive but short title. For example a nugget going to be used on this page (<code>{{FULLPAGENAME}}</code>) should be save as <code>{{FULLPAGENAME}}/<Nugget title1></code>.


To then transclude (display) this nugget in the main parent page you would use the code <code>{{Tl|/<Nugget title1>|nl}}</code>. You don't need to specify the parent page in the code since you're transcluding a subpage of the page you're on.

''If you want to transclude (display) a Nugget from a different page, you will have to use the full page name, and if the page is in the main namespace it must be preceded by a colon (:). For example this page  transcludes the wiki etiquette Nugget from the [[Waze etiquette]] page using the code {{tlx|:Waze etiquette#Wiki changes}}.''

===== Cautions and pitfalls of using nuggets =====

Nuggets are designed to be transcluded (displayed) on other pages primarily, they must therefore be coded with transclusion in mind to ensure they display as desired when viewed directly '''and from other pages using them'''.


Because Nuggets are being transcluded, they follow the same rules as templates do, and have some of the same cautions.
* A pipe character (&#124;) is used in template wiki markup code to define a new parameter in the template. When transcluded these can interfere with the parsing and cause unexpected output.
** The solution is to either use the character code <code>&amp;#124;</code> to output a visual pipe character which does not affect the code. If you need the actual pipe character to be output (for example as part of a table syntax or a parser function), then you must use the {{tl|!}} [[Template:!|template]].
* Similarly an equals sign ({{=}}) is used as an operator in templates, and parser functions. You may use the {{tl|{{=}}}} [[template:{{=}}|template]] to display and {{=}} which is not an operator. This is commonly needed in deep URL links. ''For more complex usages please see the [[template:{{=}}|template documentation]].''

=== Converting from the existing wiki ===

The ''Wiki Masters'' are currently editing all of the [[#Nominated pages for global wiki|pages nominated for the Global wiki]] to meet the standards of the Wazeopedia Global wiki. This is a slow process, as there is a great deal of content to work on.

The majority of these pages which have been nominated for the Wazeopedia Global wiki were heavily biased to the United States, and some other English-speaking local communities. This is because most of the English content wiki was primarily edited by American editors. As part of the preparation for, and the conversion process to move these pages to the Wazeopedia Global wiki, they will have to "globalized". To "globalize" a page the Wiki Masters working with the Global Champs will remove any information specific to the local communities, and replace it with globally relevant information instead.

These local communities will have to decide if they want to either maintain the current page as is, or adopt the new global version for their local community as well.

If they want to maintain the original page, the Wiki Master team will offer to work in tandem with the local editors to make a copy for them before any "globalization" is performed. The local editors may choose to make the copy and separate it from the global page on their own.


=== Protocol for editing global pages ===

Any edit to the wiki should follow the rules of Waze wiki editing etiquette, edits to the Global wiki must also follow this protocol.
{{Collapsible section top}}
:''Click expand to read the [[Waze etiquette#Wiki changes|Waze wiki editing etiquette]]''
{{Collapsible section content}}
{{:Waze etiquette/Wiki changes}}
{{Collapsible section bottom}}

==== Purpose ====

The purpose of the protocol is to protect the global wiki from premature changes, or changes which do not represent a Global consensus. Because these pages may be transcluded into numerous other local wikis, and because there may be local translations of the pages which are monitoring these pages for any updates, it is very important that any changes to these pages are perfected before they are published.


==== The protocol summarized ====

* Any edit which changes the meaning of the existing content - ''even if the change is just a clarification compliant with the original intent of the authors'' - must first be presented in the forum.
** Simple edits which do not change the content meaning at all (e.g. punctuation, simple typos, removing the 's' from http'''s''' URLs) do not need to be posted to the forum. These should be explained in the edit summary.
* Every edit must be based on a previous consensus posted in the public [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion] forum.
** Edits based on a private consensus ''(because the information used to reach the decision is proprietary, or the decision is made by Champs to protect the maps / wiki)'', should still first be publicly announced in the wiki updates forum, to allow the public to provide feedback. This feedback can provide an alternate perspective, or inform the private audience of special situations they had not considered. The private audience ''(Champs, Wiki Masters)'' may '''choose to consider''' this feedback, and use it to refine or adapt their consensus. {{U|Ultimately it is the decision of the Champs whether to modify their decision based on the feedback, or to move forward and publish their edit.}}
* After a consensus is reached (in private or public), and a resulting edit is being made, there should be an announcement in the public forum. The forum post should summarize the consensus which was reached, and describe the edit being made. This also lets others know that a guideline, interface fact, or statement, etc., is being changed.
** Simple edits which are made to clarify a pages meaning so it more clearly reflects a previously achieved consensus, should still be announced with the rationale in the forum as well. However since there is already consensus for their meaning, they don't need to wait to build consensus again. They can make the change as soon as they announce it.
* Edits which alter formatting, deal with and affect templates, might  break tranclusions, or links, or otherwise affect the technical integrity of a page should be tested in a user page first, and generally should include oversight from "technical Wiki Masters".

==== Protocol flowchart ====

[[File:Global_Wiki_Change_Control_-_process_flow.png|thumb|200px|center|Click to see in full size]]

==== Enforcement ====

There is a team of ''Wiki Moderators'' who will patrol the Global wiki pages and ensure that any changes which are made have followed this protocol. In the new Wazopedia changes will not be visible to regular users until after the moderators approve them. In the current wiki until the upgrade to Wazeopedia is completed the moderators will monitor [[#Nominated pages for global wiki|pages nominated for the Global wiki]], and may have to revert changes which don't follow this protocol, until they conform to this protocol.

If an edit is made which does not follow this protocol, the moderators will hold the edit until it is agreed upon using this protocol. The moderators will begin a discussion in the proper forum to facilitate this process if the editor failed to so first.

== Local wiki ==
{{NeedInfo|explain purpose of local wiki, content management authority and responsibility, WM tools, global will redirect to local at every opportunity}}