ウィキメディアの非公開ウィキを作成

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Setting up an internal Wikimedia wiki and the translation is 36% complete.
Other languages:
Deutsch • ‎English • ‎Esperanto • ‎Lëtzebuergesch • ‎Türkçe • ‎dansk • ‎español • ‎français • ‎magyar • ‎polski • ‎português • ‎português do Brasil • ‎čeština • ‎русский • ‎മലയാളം • ‎中文 • ‎日本語 • ‎한국어
依頼と提案 ウィキメディアの内部ウィキを作成
このページではウィキメディアの活動、委員会、提携団体で使う内部ウィキの作成を解説します。特定の言語のウィキメディアのプロジェクトで新設するにはRequests for new languages (言語の追加の申請) を、またプロジェクトのウィキの新設の提案はProposals for new projects (プロジェクト新設の提案) をそれぞれご参照ください。

ウィキメディアのコアなプロジェクト群のウィキならびにプロジェクト立ち上げ等に用いるウィキがあります。ウィキメディア財団が設けているさまざまな内部ウィキ公開非公開fishbowl wikisに分かれており、ウィキメディア提携団体計画段階のプロジェクト委員会プロジェクト ウィキのサポートにも使われています。

このページには、内部ウィキを作ろうと考えたときに出発点となるように、参照できる作り方と管理の方法の前例をあげます。

基本

  1. Get consensus - is this wiki really needed? What will it be used for? Has the relevant community, arbcom, or WMF body, that is responsible for the wiki, agreed to its creation?
  2. Request a wiki be set up. The route for this is via a request through Phabricator.
    1. File a task in Wikimedia's task tracker;
    2. Be sure that the task includes a URL to the local on-wiki consensus, preferably using a permanent link (click the "Permanent link" link in the toolbox, which should make the URL end in &oldid=...); the page at this URL should also link to the task;
    3. What abbreviation / subdomain (URL) will it have? Discuss with Phabricator participants if needed.
      • The abbreviation should only be one level and must be a subdomain of an existing Wikimedia site, in almost all cases it should be .wikimedia.org. Hosting a new domain would require a new SSL certificate purchase and setup. Instead, it is recommended that you redirect any new web domains to the subdomain of an existing Wikimedia Foundation operated domain.
        • Examples: ex.wikimedia.org - ex-yz.wikimedia.org - exyz.wikimedia.org - ex.mediawiki.org
        • Not: ex.yz.wikimedia.org - exyzwikimedia.org
  3. If the wiki needs special configuration when it is set up, then request that at the same time. Examples:
    • Who can read it?
    • Who can edit it?
    • Is account creation by approval only, or by anybody clicking on "create an account"?
    • Is email notification to be switched on? (usually yes)
    • Should certain extensions like Translate be switched on?
    • Are any special namespaces required? (For example, OTRS Wiki might have a namespace for "Response:" and "Response_talk:")
    • Are any custom settings for upload needed - for example is upload disabled, or unusual file types allowed?
    • (See also: Help:Configuration)
  4. Be sure to follow the request on Phabricator and help answer any questions that may come up during the discussion.

Your wiki will have at least one bureaucrat account, that can be used to create sysops and other bureaucrats. You will want to test that the basics of your wiki - log in; verify you have bureaucrat rights; verify the correct privacy setting and visibility exists; verify that upload works; verify that editing works. These all require setup at the server end, and once working will continue to work. (Initially some specialist formatting may not - see below.) You will also want to create accounts, and sysop/bureaucrat these as necessary.

Congratulations - once your request is reviewed in Phabricator, discussed, and approved - you will have your wiki!

Wiki config

A new wiki is like a new house - walls, floors, doors, windows, nothing else. There are an infinite number of ways to set one up internally. Rather than reinventing the wheel, this page describes a setup that's been used before and works well. It contains markup you can cut/paste to create basic pages if needed. Feel free to customize it!

Note: Included in the attached information are instructions how to import the standard .js and .css configurations, to allow tables, and other customized wiki formatting you may be used to. Hence these are not repeated here. A number of variant pages for one very common use - internal arbcoms - are also described. Ignore these if they don't apply to you. The examples are geared to small, focussed wikis (arbcom, working groups, chapters, and the like). Last, if your wiki is not in English, you will need to translate any text you use.

Pages setup

See Sample pages for copy-and-paste markup.

The same page also contains markup for useful documentation pages covering import of js and css, sidebar and main page handling, and so on.

Specialist formatting (CSS, JS)

The import of table classes and formats, and common JS (script) to work with these, will need importing. The above page contains wiki-markup for a documentation page that explains how to do this.

Main Page privacy

The official Main Page can be seen by anyone, as can any transcluded information templates. You also cannot delete revisions from it. Accordingly if your wiki is private, you should make your main page a "public" page for passers-by that points those with accounts on the wiki to a secondary main page (i.e. Portal)

関連項目