Photo:1
Photo:2
Photo:3
Photo:4
Photo:1 Photo:2 Photo:3 Photo:4 |
| License | |
| 2>
MediaWiki is free and open source software and is distributed under the terms of the GNU General Public License version 2 or any later version while its documentation is released under the Creative Commons BY-SA 3.0 license and partly in the public domain.[12] Specifically, the manuals and other content at MediaWiki.org are Creative Commons-licensed, while the set of help pages intended to be freely copied into fresh wiki installations and/or distributed with MediaWiki software is public domain. This was done to eliminate legal issues arising from the help pages being imported into wikis with licenses that are incompatible with the Creative Commons license.[13] MediaWiki development has generally favored the use of open-source media formats.[14]
[edit] Tags:Wiki,License,Free,Wiki Software,Free And Open Source Software,Gnu General Public License,Creative Commons By-sa 3.0,Public Domain,Open-source, | |
| Development | |
| 2>
MediaWiki has an active volunteer community for development and maintenance. Users who have made meaningful contributions to the project by submitting patches are generally, upon request, granted access to commit revisions to the project's Apache Subversion repository.[15] There is also a small group of paid programmers who primarily develop projects for the Wikimedia foundation. Wikimedia participates in the Google Summer of Code by facilitating the assignment of mentors to students wishing to work on MediaWiki core and extension projects.[16] As of June 2010, there were 143 developers who had committed changes to the MediaWiki core or extensions within the past year.[17] Major MediaWiki releases are generated approximately every three to eight months by taking snapshots of the development trunk, which is kept continuously in a runnable state;[18] minor releases, or point releases, are issued as needed to correct bugs (especially security problems).
MediaWiki has a public bug tracker, bugzilla.wikimedia.org, which runs Bugzilla. The site is also used for feature and enhancements requests.
[edit] Tags:Wikimedia Foundation,Patches,Apache Subversion,Minor Releases,Bug,Bugzilla,Extensions, | |
| History | |
| 2>
When Wikipedia was first launched in January 2001, it ran on the existing wiki software UseModWiki, which was written in Perl and stored all wiki pages in text files. This software soon proved limiting, both in its functionality and its performance. In mid-2001, Magnus Manske, a developer and student at the University of Cologne, who was also a Wikipedia editor, began working on new software that would replace UseModWiki, specifically for use by Wikipedia. This software was written in PHP and stored all its information in a MySQL database. It launched on the English Wikipedia in January 2002, and was gradually deployed on all the Wikipedia language sites of that time. This software was referred to as "the PHP script" and as "phase II", with the name "phase I" retroactively given to the use of UseModWiki.
Increasing usage soon caused load problems again, and soon afterward, another rewrite of the software began, done by Lee Daniel Crocker, which was first known as "phase III". This new software was also written in PHP with a MySQL backend, and kept the basic interface of the phase II software, but was meant to be more scalable. It went live on Wikipedia in July 2002.
The Wikimedia Foundation was announced on June 20, 2003, and in July, Wikipedia contributor Daniel Mayer suggested the name "MediaWiki" for the software, as a play on "Wikimedia".[19] The name was gradually phased in beginning in August 2003. The name has frequently caused confusion due to its (intentional) similarity to the "Wikimedia" name (which itself is similar to "Wikipedia").[20]
The product logo was created by Erik Möller using a flower photograph taken by Florence Nibart-Devouard, and was originally submitted to an international logo contest for a new Wikipedia logo held in mid-2003.[21] The logo came in third place, and was chosen to represent MediaWiki instead of Wikipedia, with the second place logo used for the Wikimedia Foundation.[22] The double square brackets around the photo of a sunflower symbolize the syntax MediaWiki uses for creating hyperlinks to other wiki pages.
Later, Brion Vibber, the Chief Technical Officer of the Wikimedia Foundation,[23] took up the role of release manager and most active developer.[1][24]
Major milestones in MediaWiki's development have included the categorization system, added in 2004; parser functions, added in 2006; and flagged revisions, added in 2008.[25]
[edit] Tags:Written In,Php,Mb,Wikipedia,Database,Usemodwiki,Perl,University Of Cologne,Mysql,Erik Möller,Florence Nibart-devouard,Sunflower,Hyperlinks,Chief Technical Officer,Parser Functions,Flagged Revisions,Tea, | |
| Sites using MediaWiki | |
| 2>
See also: Category:MediaWiki websites
Wikia also uses MediaWiki Software.
MediaWiki's most famous use has been in Wikipedia and, to a lesser degree, Wikimedia's other projects. But MediaWiki has also been used to power tens of thousands of other wikis, both public and private.
A number of alternative wiki encyclopedias to Wikipedia run on MediaWiki, including Citizendium, Conservapedia,[26] Metapedia[27] and Scholarpedia.
Wikia, the world's most popular wiki farm, runs on MediaWiki. Among the notable wikis that Wikia hosts are LyricWiki, Memory Alpha, Uncyclopedia, WoWWiki and Wookieepedia.
Other popular public wikis that run on MediaWiki include wikiHow, AboutUs.org, Mahalo.com and WikiLeaks.
MediaWiki is also used internally by a large number of companies, including Novell and Intel.[28]
Notable usages of MediaWiki within governments include Intellipedia, used by the United States Intelligence Community, and Diplopedia, used by the United States Department of State. United Nations agencies such as the U.N. Development Programme and INSTRAW chose to implement their wikis using MediaWiki because "this software runs Wikipedia and is therefore guaranteed to be thoroughly tested, will continue to be developed well into the future, and future technicians on these wikis will be more likely to have exposure to MediaWiki than any other wiki software."[29]
[edit] Tags:Websites,Novell,Citizendium,Conservapedia,Metapedia,Scholarpedia,Wikia,Lyricwiki,Memory Alpha,Uncyclopedia,Wowwiki,Wikihow,Aboutus.org,Mahalo.com,Intel,Intellipedia,United States Intelligence Community,Diplopedia,United States Department Of State, | |
| Key features | |
| 2>
MediaWiki provides a rich core feature set and a mechanism to attach extensions to provide additional functionality. Due to the strong emphasis on multilingualism in the Wikimedia projects, internationalization and localization has received significant attention by developers. The user interface has been fully or partially translated into more than 300 languages,[30] and can be further customized by site administrators (the entire interface is editable through the wiki).
[edit] Tags: | |
| Installation and configuration | |
| 3>
Installation of MediaWiki requires that the user have administrative privileges on a server running both PHP and a compatible type of SQL database. Some users find that setting up a virtual host is helpful if the majority of one's site runs under a framework (such as Zope or Ruby on Rails) that is largely incompatible with MediaWiki.[31] Cloud hosting can enable a user to dispense with the task of building a new server by hand.[32]
An installation PHP script is accessed via a web browser to initialize the wiki's settings. It prompts the user for a minimal set of required parameters, leaving further changes, such as enabling uploads,[33] adding a site logo,[34] and installing extensions, to be made by modifying configuration settings[35] contained in a file called LocalSettings.php.[36] Some aspects of MediaWiki can be configured through special pages or by editing certain pages; for instance, abuse filters can be configured through a special page,[37] and certain gadgets can be added by creating javascript pages in the MediaWiki namespace.[38] The MediaWiki community publishes a comprehensive installation guide.[39]
[edit] Tags:Type, | |
| Markup | |
| 3>
One of the earliest differences between MediaWiki (and its predecessor, UseModWiki) and other wiki engines was the use of "free links" instead of CamelCase. When MediaWiki was created, it was typical for wikis to require text like "WorldWideWeb" to create a link to a page about the World Wide Web: links in MediaWiki, on the other hand, are created by surrounding words with double square brackets, and any spaces between them are left intact, e.g. [[World Wide Web]]. This change was logical for the purpose of creating an encyclopedia, where accuracy in titles is important.
MediaWiki uses an extensible[40] lightweight wiki markup designed to be easier to use and learn than HTML. Tools exist for converting content such as tables between MediaWiki markup and HTML.[41] Efforts have been made to create a MediaWiki markup spec, but a consensus seems to have been reached that Wikicode requires context-sensitive grammar rules.[42][43] The following side-by-side comparison illustrates the differences between wiki markup and HTML:
MediaWiki syntax
Equivalent HTML
Rendered output
"Take some more [[tea]]," the March Hare said to Alice, very earnestly.
"I've had nothing yet," Alice replied in an offended tone: "so I can't take more."
"You mean you can't take ''less''," said the Hatter: "it's '''very''' easy to take ''more'' than nothing."
<p>"Take some more <a href="Tea" title="Tea">tea</a>," the March Hare said to Alice, very earnestly.</p>
<p>"I've had nothing yet," Alice replied in an offended tone: "so I can't take more."</p>
<p>"You mean you can't take <i>less</i>," said the Hatter: "it's <b>very</b> easy to take <i>more</i> than nothing."</p>
"Take some more tea," the March Hare said to Alice, very earnestly.
"I've had nothing yet," Alice replied in an offended tone: "so I can't take more."
"You mean you can't take less," said the Hatter: "it's very easy to take more than nothing."
(Quotation above from Alice's Adventures in Wonderland by Lewis Carroll)
[edit] Tags: | |
| Editing interface | |
| 3>
Editing interface of MediaWiki 1.9, showing the edit toolbar and some examples of wiki syntax.
MediaWiki's page-editing tools have sometimes been described as somewhat challenging to learn.[44] A survey of students assigned to use a MediaWiki-based wiki found that when they were asked an open question about main problems with the wiki, 24% cited technical problems with formatting, e.g. "Couldn't figure out how to get an image in. Can't figure out how to show a link with words; it inserts a number."[45]
To make editing long pages easier, MediaWiki allows the editing of a subsection of a page (as identified by its header). A user can also indicate whether or not an edit is minor. Correcting spelling, grammar or punctuation are examples of minor edits, whereas adding paragraphs of new text is an example of a non-minor edit.
Sometimes while one user is editing, a second user saves an edit to the same part of the page. Then, when the first user attempts to save the page, an edit conflict occurs. The second user is then given an opportunity to merge his content into the page as it now exists following the first user's page save. An optional extension gives selected user groups priority when edit conflicts occur.[46]
MediaWiki has the user interface in different languages. A language for the wiki content itself can also be set, to be sent in the "Content-Language" HTTP header and "lang" HTML attribute.
In Mediawiki 1.17 and up the classic editing toolbar is no longer included.
[edit] Tags: | |
| Application Programming Interface | |
| 3>
MediaWiki has an extensible Application Programming Interface that provides direct, high-level access to the data contained in the MediaWiki databases. Client programs can use the API to login, get data, and post changes. The API supports thin web-based JavaScript clients and end-user applications (such as vandal-fighting tools). The API can be accessed by the backend of another web site.[47] An extensive Python bot library, Pywikipediabot,[48] and a popular semi-automated tool called AutoWikiBrowser, also interface with the API.[49] The API is accessed via URLs such as http://en.wikipedia.org/w/api.php?action=query&list=recentchanges. In this case, the query would be asking Wikipedia for information relating to the last 10 edits to the site. One of the perceived advantages of the API is its language independence; it listens for HTTP connections from clients and can send a response in a variety of formats, such as XML, serialized PHP, YAML, or JSON.[50] Client code has been developed to provide layers of abstraction to the API.[51]
[edit] Tags:Web-based, | |
| Rich content | |
| 3>
Images can be arranged in galleries, a feature that is used extensively for Wikimedia's media archive, Wikimedia Commons.
MediaWiki supports rich content generated through specialized syntax. For example, the software comes with support for rendering mathematical formulas using LaTeX and a special parser written in OCaml. Similar functionality for other content, ranging from graphical timelines over mathematical plotting and musical scores to Egyptian hieroglyphs, is available in the form of extensions and also aesthetic sense has improved considerably.
The software has become more powerful at dealing with a wide variety of uploaded media files. Its richest functionality is in the area of images, where image galleries and thumbnails can be generated with relative ease. There is also support for Exif metadata. The use of MediaWiki to operate the Wikimedia Commons, one of the largest free content media archives, has driven the need for further functionality in this area.
Because any WYSIWYG editor would have to know wikitext grammar, and no full grammar for wikitext exists, MediaWiki currently provides no native WYSIWYG support.[52] It does come with a customizable graphical toolbar for simplifying the process of learning the wiki syntax.[53] Various extensions exist for handling WYSIWYG editing to different degrees,[54] some using variations of the popular CKEditor. Wikia, a popular wiki farm, uses a WYSIWYG extension that, being designed to be a modal editor, allows the user to flip back and forth between WYSIWYG and WikiText and Preview modes in a single editing session.[citation needed] MediaWiki also has an interface to allow the transparent use of external editors for uploaded files and wiki pages.[55]
[edit] Tags:Available In,Free Content, | |
| Tracking edits | |
| 3>
Among the features of MediaWiki to assist in tracking edits is a Recent Changes feature that provides a list of recent edits to the wiki. This list contains basic information about those edits such as the editing user, the edit summary, the page edited, as well as any tags (e.g. "possible malware link")[56] added by customizable abuse filters and other extensions to aid in combating unhelpful edits.[57] On more active wikis, so many edits occur that it is hard to track Recent Changes manually. Anti-vandal software, including user-assisted tools[58] and fully automated bots,[59] are sometimes employed on such wikis to process Recent Changes items. Server load can be reduced by sending a continuous feed of Recent Changes to an IRC channel that these tools can monitor, eliminating their need to send requests for a refreshed Recent Changes feed to the API.[60]
Another important tool is watchlisting. Each logged-in user has a watchlist to which he can add whatever pages he or she wishes. When an edit is made to one of those pages, a summary of that edit appears on the watchlist the next time it is refreshed.[61] As with the recent changes page, recent edits that appear on the watchlist contain clickable links for easy review of the article history and specific changes made.
There is also capability to review all edits made by any particular user. In this way, if an edit is identified as problematic, it is possible to check the user's other edits for issues.
MediaWiki allows one to link to specific versions of articles. This has been useful to the scientific community, in that expert peer reviewers could analyse articles, improve them and provide links to the trusted version of that article.[62]
[edit] Tags: | |
| Navigation | |
| 3>
Navigation through the wiki is largely through internal wikilinks.
These implement page existence detection, in which a link is colored blue if the target page exists on the local wiki and red if it does not. When a user clicks on a red link, he is prompted to create an article with that title. Page existence detection makes it practical for users to create "wikified" articles — that is, articles containing links to other pertinent subjects — without those other articles being yet in existence.
The red/blue distinction alerts :
readers lacking an interest in creating new articles of broken links that it would be fruitless for them to click upon
editors interested in creating new articles of what topics their efforts might be usefully applied to.
Interwiki links function much the same way as namespaces. A set of interwiki prefixes can be configured to cause, for instance, a page title of wikiquote:Jimbo Wales to direct the user to the Jimbo Wales article on Wikiquote.[63] Unlike internal wikilinks, interwiki links lack page existence detection functionality, and accordingly there is no way to tell whether a blue interwiki link is broken or not.
[edit] Tags: | |
| Page tabs and associated pages | |
| 4>
MediaWiki page tabs, using the "Vector" skin. The red coloration of the "discussion" tab indicates that the article does not yet have a talk page. As with any other red wikilink, clicking on it prompts the user to create the page.
Page tabs are displayed at the top of pages. These tabs allow users to perform actions or view pages that are related to the current page. The available default actions include viewing, editing, and discussing the current page. The specific tabs displayed depend on whether or not the user is logged into the wiki and whether the user has sysop privileges on the wiki. For instance, the ability to move a page or add it to one's watchlist is usually restricted to logged-in users. The site administrator can add or remove tabs by using JavaScript or installing extensions.[64]
Each page has an associated history page from which the user can access every version of the page that has ever existed and generate diffs between two versions of his choice. Users' contributions are displayed not only here, but also via a "user contributions" option on a sidebar. Carl Challborn & Teresa Reimann note that "While this feature may be a slight deviation from the collaborative, ‘ego-less’ spirit of wiki purists, it can be very useful for educators who need to assess the contribution and participation of individual student users."[65]
[edit] Tags: | |
| 4>
"Talk page" redirects here, for talk pages on Wikipedia see Help:Using talk pages
MediaWiki provides many features beyond hyperlinks for structuring content. One of the earliest features is namespaces. One of Wikipedia's earliest problems had been the separation of encyclopedic content from pages pertaining to maintenance and communal discussion, as well as personal pages about encyclopedia editors. Namespaces are prefixes before a page title (such as "User:" or "Talk:") that serve as descriptors for the page's purpose and allow multiple pages with different functions to exist under the same title. For instance, a page titled "[[The Terminator]]", in the default namespace, could describe the 1984 movie starring Arnold Schwarzenegger, while a page titled "[[User:The Terminator]]" could be a profile describing a user who chooses this name as a pseudonym. More commonly, each page and each namespace has an associated "Talk:" page, which can be used to discuss its contents, such as "User talk:" or "Template talk:". The purpose of having discussion pages is to allow content to be separated from discussion surrounding the content.[66][67]
Namespaces can be viewed as folders that separate different basic types of information or functionality. Custom namespaces can be added by the site administrators. There are 16 namespaces by default for content, with 2 "pseudo-namespaces" used for dynamically generated "Special:" pages and links to media files. Each namespace on MediaWiki is numbered: content page namespaces have even numbers and their associated talk page namespaces have odd numbers.[68]
[edit] Tags: | |
| Category Tags | |
| 4>
Users can create new categories and add pages and files to those categories by appending one or more category tags to the content text. Adding these tags creates links at the bottom of the page that take the reader to the list of all pages in that category, making it easy to browse related articles.[69] The use of categorization to organize content has been described as a combination of :
Collaborative tagging systems like del.icio.us and
Hierarchical classifications like the Dewey Decimal Classification.[70]
[edit] Tags: | |
| Subpages | |
| 4>
In addition to namespaces, content can be ordered using subpages. This simple feature provides automatic breadcrumbs of the pattern [[Page title/Subpage title]] from the page after the slash (in this case, "Subpage title") to the page before the slash (in this case, "Page title").
[edit] Tags: | |
| Customization | |
| 3>
Users can configure custom JavaScript that is executed on every pageview. This has led to JavaScript tools that users can "install", the "navigation popup" tool shown here displays a small preview of an article when hovering over a link title.
If the feature is enabled, users can customize their stylesheets and configure client-side JavaScript to be executed with every pageview. On Wikipedia, this has led to a large number of additional tools and helpers developed through the wiki and shared among users. For instance, Lupin's navigation popups is a custom JavaScript tool that shows previews of articles when the user hovers over links, and also provides shortcuts for common maintenance tasks.[71] Another example is wikEd, a full-featured MediaWiki-integrated text editor that provides syntax highlighting and search and replace functions.[38]
A screenshot of a wiki using Mediawiki with a customized skin
The entire MediaWiki user interface can be edited through the wiki itself by users with the necessary permissions (typically so-called "administrators"). This is done through a special namespace with the prefix "MediaWiki:", where each page title identifies a particular user interface message. Using an extension,[72] it is also possible for a user to create personal scripts, and to choose whether certain sitewide scripts should apply to him by toggling the appropriate options in the user preferences page.
[edit] Tags: | |
| Templates | |
| 3>
The "MediaWiki:" namespace was also originally used for creating custom text blocks that could then be dynamically loaded into other pages using a special syntax. This content was later moved into its own namespace, "Template:".
Templates are text blocks that can be dynamically loaded inside another Tags: | |
z³ote monety |